IBM Lotus Web Content Management: Tracings and common exceptions  

Enable tracing

Web Content Management uses the WebSphere Application Server trace facilities to create trace information. If you need detailed trace output of Web Content Management to debug a problem, follow these steps:

b. To permanently enable tracing, do the following:
a. Start WebSphere Application Server.
b. Open the Administrative Console.
c. Navigate to Troubleshooting > Logs and Traces > WebSphere_Portal > Diagnostic Trace.
d. Make sure that the check box "Enable Trace" is selected.
e. Enter one of the following in the TraceSpecification field:

com.ibm.workplace.wcm.*
com.aptrix.*
com.presence.*

For example, to trace all events, enter the following:

com.ibm.workplace.wcm.*=all:com.aptrix.*=all:com.presence.*=all

f. Save the changes and restart WebSphere Portal.

2. To enable tracing for just the current WebSphere Portal session, do the following:

a. Go to Administration > WebSphere Portal > Portal Analysis > Enable Tracing.
b. Enter one of the following in the “Append these trace settings” field:

com.ibm.workplace.wcm.*
com.aptrix.*
com.presence.*

For example, to trace all events, enter the following:

com.ibm.workplace.wcm.*=all:com.aptrix.*=all:com.presence.*=all

NOTE: The location of trace file can be found at WP_HOME/log: trace.log

Trace strings for different situations

Specifying which packages to trace depends on the area of interest. Enabling these packages at trace level finer is equivalent to enabling trace level 3 logging in previous versions of Web Content Management. Other options are INFO, FINE, FINER, FINEST, ALL.

Authoring UI:

com.ibm.workplace.wcm.app.ui.*
com.aptrix.*
com.presence.connect.*

Workflow subsystem tracing:

com.ibm.workplace.wcm.services.workflow.*
com.aptrix.pluto.workflow.*

Authoring and presentation template subsystem tracing:

com.aptrix.pluto.presentation.*

Syndication subsystem tracing:

com.aptrix.syndication.*
com.aptrix.deployment.*

WCM Caching:

com.presence.connect.cache.*
com.aptrix.cacher.*
com.ibm.workplace.wcm.services.content.*

WCM Search (Search portlet):

com.ibm.lotus.search.*
com.ibm.hrl.*
com.ibm.siapi.search.*
com.ibm.workplace.searchmenu.*

Resource subsystem tracing:

com.aptrix.pluto.resource.*

Personalization (PZN) integration subsystem tracing:

com.ibm.workplace.wcm.services.pzn.*
com.ibm.workplace.wcm.data.pzn.*

Personalization in WebSphere Portal (rules, campaigns, application objects):

com.ibm.websphere.personalization.*
com.ibm.websphere.query.*

Personalization and Security:

com.ibm.websphere.personalization.*

Personalization and Web Content Management:

com.ibm.websphere.personalization.*
com.ibm.websphere.query.*
com.ibm.workplace.wcm.pzn.*
com.ibm.workplace.wcm.services.pzn.*

Personalization and Java Content Repository (JCR):

com.ibm.websphere.personalization.*
com.ibm.websphere.query.*
com.ibm.icm.jcr.*

Personalization Authoring Performance:

com.ibm.websphere.personalization.*
com.ibm.wps.caf.*


Personalization Runtime Performance:

com.ibm.websphere.personalization.*

Personalization Publishing:

com . i bm.websphere.personalization.*

Personalization Authoring Environment (Navigator, Editor, and List portlets):

com.ibm.websphere.personalization.*
com.ibm.wps.caf.*

Security subsystem tracing:

com.presence.connect.wmmcomms.*
com.presence.connect.session.*
com.presence.connect.vault.*
com.aptrix.pluto.security.*

Portal Document Manager (PDM) General:

com.ibm.wcf.*
com.ibm.wps.dm.*
com.ibm.icm.jcr.ts.*
com.ibm.icm.jcr.query.*
com.ibm.icm.ci.query.*
com.ibm.wcf.runtime.portlet.standard.WpsRenderContext.*

JCR Tracings

Simple tracing

Use when you do not know which controllable-type/control is failing. The settings are as follows:

com.ibm.icm.*
- Captures the inner workings of JCR

com.ibm.workplace.wcm.services.content.*
- Captures a low-level WCM-JCR tracing for every item

com.ibm.workplace.wcm.domain.transformers.control.*
- Captures a higher-level WCM-JCR tracing for every control of every item

com.ibm.workplace.wcm.domain.transformers.controllable.*
- Captures an even-higher-level WCM-JCR tracing for every item (controllable) type

JCR Advance Tracing

Use when you know which controllable-type and/or control is failing. The settings are as follows:

com.ibm.workplace.wcm.services.content.*
- Turns on low-level WCM-JCR tracing for every item

com.ibm.workplace.wcm.domain.transformers.control.XXXXX
- Turns on higher-level WCM-JCR tracing for the specified control of every item, where XXXXX is one of the following:

• HistoryControlTransformer
  
• IdentityControlTransformer
  
• ProfileControlTransformer
  
• SecurityControlTransformer
  
• WorkflowControlTransformer
  

• AbstractControllableTransformer
  
• AlternateDesignCmpntTransformer
  
• AlternateLinkCmpntTransformer
  
• ArrayCmpntTransformer
  
• AttributeReferenceCmpntTransformer
  
• BasePathCmpntTransformer
  
• BaseReferenceCmpntTransformer
  
• CategoryTransformer
  
• CmpntReferenceTransformer
  
• CmpntTransformer
  
• ConfigParamCmpntTransformer
  
• ContentLinkTransformer
  
• ContentSpotCmpntTransformer
  
• ContentTransformer
  
• ContextPathCmpntTransformer
  
• ControllableNodeValueTransformer
  
• ControllableTransformer
  
• DateCmpntTransformer
  
• EmailActionTransformer
  
• ExpireActionTransformer
  
• ExternalLinkTransformer
  
• FEDCmpntReferenceTransformer
  
• FEDCmpntTransformer
  
• FileResourceCmpntTransformer
  
• HistoryCmpntTransformer
  
• HTMLCmpntTransformer
  
• IDCmpntTransformer
  
• ImageResourceCmpntTransformer
  
• IndentCmpntTransformer
  
• IndexCmpntTransformer
  
• InlineEditCmpntTransformer
  
• InlineEditReferenceCmpntTransformer
  
• JSPCmpntTransformer
  
• LinkCmpntTransformer
  
• MenuCmpntTransformer
  
• NavigatorCmpntTransformer
  
• NoPrefixBasePathCmpntTransformer
  
• NoPrefixServletPathCmpntTransformer
  
• NumericCmpntTransformer
  
• ObjectSummaryTransformer
  
• OptionSelectionCmpntTransformer
  
• PageInfoCmpntTransformer
  
• PagingCmpntTransformer
  
• PDMCmpntReferenceTransformer
  
• PDMCmpntTransformer
  
• PlaceholderCmpntTransformer
  
• PlutoSubscriberTransformer
  
• PlutoSyndicatorTransformer
  
• PrefixPathCm pn tT ransformer
  
• ProfileCmpntTransformer
  
• PublishActionTransformer
  
• ResourceCmpntTransformer
  
• ScheduledMoveActionTransformer
  
• SearchCmpntTransformer
  
• SecurityCmpntTransformer
  
• ServletPathCmpntTransformer
  
• SiteAreaTransformer
  
• SiteTransformer
  
• StyleSheetCmpntReferenceTransformer
  
• StyleSheetCmpntTransformer
  
• StyleTransformer
  
• TaxonomyCmpntTransformer
  
• TaxonomyTransformer
  
• TemplateTransformer
  
• TextCmpntTransformer
  
• UsernameCmpntTransformer
  
• UserSelectionCmpntTransformer
  
• WCMURLCmpntTransformer
  
• WorkflowActionTransformer
  
• WorkflowCmpntTransformer
  
• WorkflowStageTransformer
  
• WorkflowTransformer
  

<xmp><wp_home>/wcm/migration/config/migration.properties</xmp>

trace.level = FINE

Thus, a trace log will be created if the trace level is FINE, FINER, or FINEST. An update to this value requires a server restart.

NOTE: Setting the tracing level to FINER or FINEST will slow down the migration and is unnecessary because the FINE trace level should capture any necessary logging. Also, if you have http/network connection issues, you can add the following parameter at the end of the migration.properties file:

debug.http=true

Examples of common exceptions

In this section, we describe some examples of common Web Content Management-related exceptions, including their causes and solutions.

RenderException IWKPC1007X

Symptom:
IWKPC1087X: Exception while rendering embedded in-lined component type class com.aptrix.pluto.cmpnt.ArrayCmpnt. Inline Component class is: class com.aptrix.pluto.cmpnt.CmpntReference - Exception: com.aptrix.pluto.renderer.RenderException: IWKPC1007X: Could not find an identity for name (resolved reference key): Will continue rendering.

The exception points to an issue with a particular component; however, the component name does not appear in the exception as expected. These SystemOut.log entries appear as exceptions with the above format.

Cause:
These exceptions are caused when a component tag that does not contain a component name is rendered. An example would be a Presentation Template that contains the following:

<Component name=""/>

Since no component name is specified in the tag, the above exception is thrown in the logs each time the Presentation template is used by Web Content Management. Though there is no loss of product functionality, these error messages can cause the logs to grow excessively large.

If required, implement the following trace string setting to identify where the component is being called:

com.aptrix.*=all

Resolution:
To resolve these errors, ensure that all component tags contain a specified component name. Remove any tags that do not contain a name value.

Note that many other exceptions of the class com.aptrix.pluto.cmpnt.ArrayCmpnt have been resolved by various ifixes.

AuthorizationException IWKPY1017X

Symptom:
com.ibm.workplace.wcm.api.exceptions.AuthorizationException: IWKPY1017X: Unauthorised access on {a0700080463f468997 e2bfd42fcab686, com.aptrix.pluto.site.Site} by {{John Approver, uid=wcmapprover,o=default organization, 5462d300-6456-11dc-a0ac-832e46ed2b7e, en, Type: User}, 4, {false, {userAccess={}}, {editorAccess={}}, {managerAccess={}}, [all_auth_portal_users%all_auth_portal_users_group_id, anonymous_user%anonymous_user_id, all_users%all_users_group_id, uid=wcmapprover,o=default organization%5462d300-6456-11dc-a0ac-832e46ed2b7e]}} - /TestSite

Resolution:
Check the end of the exception for the resource for which the user requires permission. In the exception above, the missing permission was on the "Test Site" root site area.

NullPointerException SRVE0068E

Symptom:
A blank page is displayed in the Web Content Management authoring portlet. Error code: SRVE0068E. The Portal Server's SystemOut.log indicates a java.lang.NullPointerException when trying to open the content item.

This problem was observed when a Web Content Management administrator attempted to open a presentation template in a Web content library that was recently imported from another Web Content Management server.

Example of the Syste mOut.log exception generated for this specific case:

[8/7/08 21:56:19:056 PDT] 0000006f ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet
/jsp/html/AuthoringUIView.jsp. Exception thrown : java.lang.NullPointerException
at com.aptrix.pluto.cmpnt.CmpntUtils.setSourceIDAndName(CmpntUtils.java:629 )
at com.aptrix.pluto.cmpnt.CmpntUtils.setSourceIDAndName(CmpntUtils.java:608 )
at com.aptrix.pluto.cmpnt.codec.AptrixLibCmpntExtension.generateCmpntFragme nt(AptrixLibCmpntExtension.java:283)
at com.aptrix.pluto.cmpnt.codec.SXMLCodec.cmpntToFragments(SXMLCodec.java:2 79)
at com.aptrix.pluto.cmpnt.codec.SXMLCodec.cmpntToFragments(SXMLCodec.java:2 49)
at com.aptrix.pluto.cmpnt.codec.SXMLCodec.toSXMLString(SXMLCodec.java:114)

at com.aptrix.pluto.cmpnt.ArrayCmpnt.getStringForComponent(ArrayCmpnt.java: 321)

Cause:
The problem can be caused by a component reference tag in the body of the presentation template referring to a library that doesn't exist on the system. Web Content Management library export/import does not prevent export/import of a single library, even if its content items have references to othe r libraries.

In this case, the component tag inside the body of the presentation template refers to a component library that was not imported to the target system where the exception occurred. Since the presentation template contained a reference to an invalid library, the presentation template was no longer able to be opened in read or edit mode.

This results in redirection to the Web Content Management authoring portlet's blank page and generation of the NPE log exception.

NOTE: This exception is not limited to presentation templates; it may occur with any content item that can render component tags.

Resolution:

• Ensure that when exporting and importing Web Content Management content libraries, you export/import all linked libraries. This is required in order to maintain referential integrity.
• Delete the content item and recreate it with the correct library reference.
• Use syndication. Syndication has additional reference checking that may help avoid referential integrity problems.

Symptom:
You notice the exceptions below appearing in the log files for your Web Content Management system. The specified string [{0}] can neither be de-serialized as an object ID nor resolved as a unique name error while using the Web Content Management Authoring UI exception.

Exception 1:

EJPDB0124E: The specified string
com.ibm.wps.hiddenpage.wcm.control.Authoring_PortletÜ can neither be de-serialized as an object ID nor resolved as a unique name.
at com.ibm.wps.services.identification.IdentificationService.deserialize(Unknown Source)
at com.ibm.wps.services.serialize.StringDeserializerFactory.readObjectID (StringDeserializerFactory.java:71)
at com.ibm.workplace.wcm.app.ui.portlet.formmapper.util.FieldBuilder. getCompositionNode(FieldBuilder.java:1483)
at com.ibm.workplace.wcm.app.ui.portlet.formmapper.util.FieldBuilder. buildPortalLink(FieldBuilder.java:1422)
at com.ibm.workplace.wcm.app.ui.portlet.command.remote.APIUtils.getURLToHiddenPortlet(APIUtils.java:56)
at com.ibm._jsp._AuthoringUIView._jspService(_AuthoringUIView.java:588)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:91)

Caused by: com.ibm.wps.services.identification.SerializationExceptionImpl:EJPDB0117E: The serialized object ID com.ibm.wps.hiddenpage.wcm.control. Authoring_Portlet cannot be read due to an invalid format.
at com.ibm.wps.datastore.id.RecreatableTransientObjectID. read(Recreata bleTransientObjectID.java:216)

Exception 2:

7/3/07 9:24:01:701 EDT] 00000043 APIUtils E com.ibm.workplace.wcm.app.ui.portlet.command.remote.APIUtils

com.ibm.wps.services.identification.SerializationExceptionImpl: EJPDB0124E: The specified string [com.ibm.wps.hiddenpage.wcm.Authoring_Portlet] can neither be de-serialized as an object ID nor resolved as a unique name

1. Log on to the Integrated Solutions Console (ISC) and select Administration > Manage Pages.
2. Determine whether the page "com.ibm.wps.hiddenpage.wcm.Authoring_Portlet" e xists.
3. If it does, then choose the "Page Properties" option to view the details of the page, verify the following, and update if necessary:
• The title is "com.ibm.wps.hiddenpage.wcm.Authoring_Portlet".
• The unique name is "com.ibm.wps.hiddenpage.wcm.Authoring_Portlet".
4. Navigate back to Manage Pages and click Edit Layout Properties on the "com.ibm.wps.hiddenpage.wcm.Authoring_Portlet" page.
5. Verify that the Web Content Management Authoring Portlet is chosen.
6. Before redeploying the authoring portlets, back up any custom .jsp files that are located in the local and remote rendering or authoring portlet directories.
7. Redeploy the authoring portlets as follows:
• Windows® only: WP_HOME\config\WPSconfig.bat configure-wcm-authoring -DPortalAdminPwd=[wpsadmin password]
• Unix/Linux® only: WP_HOME\config\WPSconfig.sh configure-wcm-authoring -DPortalAdminPwd=[wpsadmin password]

EJPDB0124E The specified string can neither be deserialized as an object

Symptom:
"...00001311 UrlGeneration E com.ibm.wps.engine.tags.UrlGenerationTag setContentNode EJPEJ0016E: Could not deserialize content node ID.
com.ibm.wps.services.identification.SerializationExceptionImpl: EJPDB0124E: The specified string [ibm.portal.Home] can neither be deserialized as an object ID nor resolved as a unique name.

Cause:
The label with page title "Home" has the unique name "ibm.portal.Home" by default, as InitVirtualPortal.xml specifies

<was_home>\installedApps\<node>\wps.ear\wps.war\virtualportal\InitVirtualPortal.xml

If this unique name is changed, and if other resources (often themes) refer to this label by the unique name "ibm.portal.Home", then when WebSphere Portal renders pages with these errant references, it will write the EJPDB0124E error above to SystemOut.log .

NOTE: Unique name changes for resources other than the "Home" label could cause similar errors. The solution below focuses on errors caused by references to "ibm.portal.Home" specifically.

Resolution:
To resolve the issue, update the WebSphere Portal configuration such that references to unique names are consistent with actual unique names. (In practice, an administrator inadvertently updating the unique name for "Home" most often causes this error.) To do this, access the Custom Unique Names portlet and change the unique name for "Home" back to "ibm.portal.Home" and then restart WebSphere Portal.

If, however, the unique name was changed deliberately, then take a full export of the WebSphere Portal configuration via XmlAccess and search for "ibm.portal.Home" to find the offending resource definitions.

DuplicatePathExceptions during Web Content Management syndication

Symptom:
During Web Content Management syndication, you see the following type of exceptions:

[18:36:53:539 EDT] 00000219 PackageProces W IWKPD1029X: Could not store doc: Something.doc, IdRef: {d5fae78044cc33dc96f9f6e01882c414, com.aptrix.pluto.content.Content}

com.ibm.workplace.wcm.services.repository.DuplicatePathException: An item already exists at path /contentRoot/icm:libraries[8]/Content/Site/Site Area/Site Areas/Sometihng.doc.
at com.ibm.workplace.wcm.services.transaction.steps.repository.RepositoryAdd.internalAdd(RepositoryAdd.java:437)
at com.ibm.workplace.wcm.services.transaction.steps.repository.RepositoryAdd.preExecute(RepositoryAdd.java:303)
at com.ibm.workplace.wcm.services.transaction.TxUnitOfWork.run(TxUnitOfWork.java:68).

When these errors are seen, the object mentioned in the exception is not saved or updated, and thus your changes are not syndicated as expected.

Cause:
The JCR does not allow items with the same name to exist under the same parent. This rule applies to any design artifact or content item.

When syndication decides what to add or update, it does so by attempting to find an item by ID in the repository. If an item already exists in the repository, then it does an update; otherwise, it does an add.

It is possible that an item with the same name (but with different ID) already exists under the parent to which you are goi ng to add an item. In this case, you cannot do an update. It may be a totally different item that the user added at the subscriber, so Web Content Management should not overwrite it. This is by design.

Note, however, that there are cases when the objects are not being added, and this can indicate an issue within Web Content Management.

Resolution:
Duplicate Path Exceptions can indicate an issue with the product or an issue with the way Web Content Management is being used. What follows is an example of a Web Content Management syndication use case that would be expected to cause a Duplicate Path Exception:

1. An author creates a publish action named "publish" on AuthServer1.
2. Another author also creates a publish action named "publish" on AuthServer2.
3. These authoring servers syndicate to a third delivery server. This syndication then causes a duplicate path exception, but this situation is not a defect. The exception here is informational, letting the user know that Web Content Management will not save the object with the same name so as to not violate the uniqueness of the object.

There are other examples in which the exceptions can be indicating that a user is not creating unique objects. If you suspect that the use case is valid, refer to the IBM Support Technote “Troubleshooting Duplicate Path Exceptions in Web Content Management” to continue with problem diagnosis.

Authoring search throws Unique constraint violated exception in Web Content Management

Symptom:
Web Content Management authoring search does not return results as expected (no results are returned) as the search index contains duplicated records.

Exception message: Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (WCMICMADMIN.SYS_C0036649) violated.

Cause:
The Web Content Management authoring search does not return results due to a unique constraint violation. The unique constraint violation is caused by a bug in the Juru code (the search engine used by Web Content Management authoring UI behind the scene) that can lead to duplicated documents existing in the search index:

Caused by: com.ibm.icm.ts.tss.ls.DatabaseException: Error inserting hit AB001001N07I24C13202364209 with score 89.20031517183564 to result table TSSTBL_1.
at com.ibm.icm.ts.tss.ls.LibraryServerImpl$ResultTable.newHit(LibraryServer Impl.java:544) ;
at com.ibm.icm.ts.tss.SearchRequestImpl.processRequest(SearchRequestImpl.java:176)
... 18 more
Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (WCMICMADMIN.SYS_C0036649) violated

Resolution:
This issue has been fixed ;in Juru version 5.0.3.6. and is included in WebSphere Portal Version 6.0.1.1.

You can determine the Juru version by looking at the following:

ItemNotFoundException Item with identity null could not be found

Symptom:
Rendering portlets configured for content currently are not available on the Web Content Management system. This exception typically appears in SystemOut.log similar to the example below:

[9/8/08 15:39:29:072 EDT] 00000051 CoreQueries W Retrieval of objects from repository failed with error /contentRoot/icm:libraries[9]/Content/department/mydepartment/memos
[9/8/08 15:39:29:119 EDT] 00000051 WCM_Rendering W Exception caught processing request. Cause: Item with identity null could not be found.
com.ibm.workplace.wcm.services.content.ItemNotFoundException: Item with identity null could not be found.
at com.ibm.workplace.wcm.services.repository.RepositoryServiceImpl.checkItemsOnPath(RepositoryServiceImpl.java:2220)
at com.aptrix.pluto.renderer.RenderContext.generateContext(RenderContext.java:476)
more....

Cause:
Most commonly, this exception is due to content that is deleted or removed from published status still being referenced by the local or remote rendering portlets.

Resolution:
To isolate the page or portlet referencing the content and generating the error, do the following:

1. Tail the systemout.log while surfing the pages that you suspect are involved. For example: ..../portalserver/log/tail -f SystemOut.log

2. As appropriate, remove references to the deleted content, or have the missing content published.

4.9 NoClassDefFoundError

Symptom:
Web Content Management migration to v6 fails during validate task with NoClassDefFoundError exception:

Exception in thread "main" java.lang.NoClassDefFoundError: javax/jcr/RepositoryException
at com.ibm.workplace.wcm.app.migration.util.MigrationProperties.validateCharacter(MigrationProperties.java:900)
at com.ibm.workplace.wcm.app.migration.util.MigrationProperties.validate(MigrationProperties.java:688)
at com.ibm.workplace.wcm.app.migration.Migration.validateMigrationProperties(Migration.java:854
at com.ibm.workplace.wcm.app.migration.Migration.doValidate(Migration.java:531)
at com.ibm.workplace.wcm.app.migration.Migration.execute(Migration.java:488)
at com.ibm.workplace.wcm.app.migration.Migration.main(Migration.java:202

Cause:
The shell or batch script is missing one of the .jar file definitions that must be added to the classpath variable.

Resolution:
Edit the file:

<wp_home>/w cm/migration/wcmmigrate.bat (or wcmmigrate.sh)

as follows:

UNIX, Linux platforms:
1. Append :..\..\jcr\lib\jcr.jar to the end of the set CLASSPATH_CMD
2. Run the ./wcmmigrate.sh command again

Windows platforms:
1. Append ;..\..\jcr\lib\jcr.jar to the end of the set CLASSPATH_CMD
2. Run the wcmmigrate command again

DB2 SQL0551N exception when using IBM DB2 for zOS

Symptom:
When you try to create content in Web Content Management, you find that the content is not written to storage, and the following error in the SystemOut.log indicates an exception in IBM DB2 for z/OS:

[6/19/07 11:03:38:252 GMT+01:00] 00000055 PLookupItemsI EPLookupItemsImpl getIDMappings Error while calling a function getIDMappings of PLS data manager. COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI driver][DB2] SQL0551N "USER_1" does not have the privilege to perform operation "SELECT" on object "DB2_INSTANCE.ICMSTJCRN00011". SQLSTATE=42501
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(Unknown Source)

Cause:
The user "USER_1" does not have proper database permissions to perform a query on the dynamic tables, causing an exception to be thrown.

Resolution:
To resolve this issue, refer to the IBM Support Technote, “DB2 for z/OS Database Rights Definition for the Portal Runtime Databa se User.”

NullPointerException when prerendering content on a schedule

Symptom:
The following Web Content Management exception is thrown repeatedly and logged in SystemOut.log each time the scheduler attempts to update a pre-rendered site:

[12/10/07 11:58:35:950 PST] 00000048 ServletWrappe A SRVE0242I: [wps] [/wps] [login]: Initialization successful.
[12/10/07 11:58:36:043 PST] 00000048 CacheServiceI I DYNA1001I: WebSphere Dynamic Cache instance named ws/com.ibm.wps.datastore.portaliddescriptor.VPIDCache initialized successfully. [12/10/07 11:58:40:200 PST] 00000049 CacherContext I IWKPL1029X: Updating cacher delay to busy delay: 5
[12/10/07 11:58:40:215 PST] 0000004b AbstractCache I Extracting site: web+content\DefaultSite
[12/10/07 11:58:59:934 PST] 0000004b AbstractCache I IWKPL1017X: Finished extracing site: web+content\DefaultSite
[12/10/07 11:59:06:950 PST] 0000004a CacherUpdateT I IWKMU1008X: Starting.
[12/10/07 11:59:07:106 PST] 0000004a Scheduler W (null message)

java.lang.NullPointerException
at com.ibm.workplace.wcm.services.query.CoreQue ries.getSiteIdentityReference(CoreQueries.java:2064)
at com.aptrix.cacher.CacherContext.addCacher(CacherContext.java:423)
at com.aptrix.cacher.CacherUpdateTask.execute(CacherUpdateTask.java:268)
at com.presence.connect.dispatcher.Scheduler$1.run(Scheduler.java:131)
at com.ibm.wps.services.workmanager.impl.WasWorkWrapper.run(WasWorkWrapper.java:41)
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java:258)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at javax.security.auth.Subject.doAs(Subject.java:477)
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java:118)
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java:325)
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:709)
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java:218) & nbsp;
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:154)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1471)

Cause:
The WCMConfigService.properties file is misconfigured; in this case, square brackets appear where none are needed, as in this example:

connect.moduleconfig.cacher.task.sites=[LibraryA/SiteA],[LibraryB/SiteB]

This configuration means that, on a schedule, Web Content Management is trying to prerender two sites, [LibraryA/SiteA] and [LibraryB/SiteB] (including the square brackets). These libraries and sites will not be found because the scheduler attempts to locate “[LibraryA" and "SiteA]" instead of "LibraryA" and "SiteA".

Resolution:
To resolve the issue, remove the square brackets from the configuration. The WCMConfigService.properties file should look like the following:

connect.moduleconfig.cacher.task.sites=LibraryA/SiteA,LibraryB/SiteB

Note that manual pre-rendering will work with the brackets in the configuration, as long as the correct library and site names are specified in the request.

MemberNotFoundException Startup fails

Symptom:
You start your Web Content Management system, but the startup sequence fails with an error in the SystemOut.log that resembles the following:

“The Member: cn=wcmadmins Could not be found in the User Repository. Reason: Message: EJPSG0002E: Requested Member does not exist.”

Cause:
The display name of the wcmadmin s group does not match the value specified in the Web Content Management configuration file.

Resolution:
In Web Content Management v5.1 and earlier:

1. Stop the WebSphere Portal/Web Content Management server.
2. Edit the following in the /WPHOME/wcm/configconnect.cfg file:

AdminGroupComminName value="wcmadmins"/>

3. Save and close the configconnect.cfg file.
4. Restart the WebSphere Portal/Web Content Management server.

In Web Content Management v6:

1. Stop the WebSphere Portal/Web Content Management server.
2. Edit the WCMConfigServices.properties located at:
/WPHOME/wcm/shared/app/config/wcmservices/WCMConfigServices.properties
3. Set the following value: connect.usermanagement.admingroupcommonname=wcmadmins
4. Save the WCMConfigServices.properties file.
5. Restart the WebSphere Portal/Web Content Management server.

Unauthorized access exceptions to site area with read access

Symptom:
You are unable to copy content to Web Content Management site area with read access to content and site area. Unauthorized access exceptions appear in the Web Content Management log output.

Resolution:
To copy contents from one site area to another, the Web Content Management user must have edit access (not just reader access) to the content within that workflow stage. For example, workflow security on the content object should be set to edit access, but access on the workflow stage itself is not edit.

ReferentialIntegrityExceptions during syndication

Symptom:
During the Web Content Management syndication process, a large number of ReferentialIntegrityExceptions are seen in the logs. When these errors are seen, the objects are not saved on the Web Content Management subscriber, and therefore some updates are not coming over as expected. Here is an example of the stack trace:

Could not save object in repository.
javax.jcr.ReferentialIntegrityException: Path Add/Rename/Delete operation failed; Deleted item: 1 is still referred by: AB001001N07F22A80100104146: Path Add/Rename/Delete operation failed; Deleted item: 1 is still referred by: AB001001N07F22A80100104146
at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2611)
at com.ibm.icm.jcr.NodeImpl.save(NodeImpl.java:2465

Cause:
A ReferentialIntegrityException occurs because a reference constraint has been violated. Due to the way Web Content Management enforces references in v6, there is potential for getting a large number of referential integrity exceptions in the logs.

One possible cause is having many references to another library that is not being syndicated. To ensure referential integrity, you should always syndicate all the appropriate libraries to the subscriber.

In v6, Web Content Management validates the references between objects that are either "to" or "from" each object. During syndication, the subscriber will request the Web Content Management objects and then attempt to store the objects in the database. While saving objects to the database, the references are also validated.

If an object fails to save for any reason, all the objects that reference that object will potentially not save either, and this condition will likely throw many occurrences of the exception ReferentialIntegrityException.

Note that there are several scenarios in w hich an object would fail to save during Web Content Management syndication, but only one scenario is addressed here. For others, refer to these Technotes:

- Deleting a Site Area and its default content on the syndicator and then syndicating the changes cause a referential integrity error on the subscriber

- Draft items in "All Items" not syndicating correctly in Web Content Management (WCM) when the event log has been cleared

Resolution:
One failing scenario involves object references that span different libraries. A cross-library reference occurs when an object (or many objects) from library A references objects from library B. If you only syndicate library A onto the subscriber, Web Content Management will look to save all the objects being referenced.

If the subscriber Web Content Management instance fails to find them, the current object will not be saved, and the syndication will end with errors.

To prevent this scenario:

1. Syndicate all libraries that have cross references.
2. Make each library mutually exclusive. In this configuration, there are no cross- library references, so any library can be syndicated by itself to any machine.
3. Create a JavaServer Pages (JSP) using the Web Content Management API to put all the test content into a draft stage on the test server. Thus, if you use the Live Item gatherer, the test content will not get syndicated.
4. Configure two-way syndication from the design server back to the authoring server and vice versa. In this configuration, all changes will be reflected on both machines.

ModuleAccessDeniedException CacherModule

Symptom:
You are running the CacherModuler manually in Web Content Management, as described in the Information Center instructions, by entering a command such as follows:

http://host_name:port_number/wps/wcm/connect?MOD=Cacher&SRV=cacheSite&Site=site_name&library=library_name

However, an error occurs in the systemout.log file:

“[12:15:52:182 EDT] 00000049 ModuleManager E IWKCT1382X: Major exception caught: com.presence.connect.business.module.ModuleAccessDeniedException: IWKCT1375X: Cacher cannot be accessed externally.”

And you see the following error in your Web browser:

“HTTP Error 403 - Forbidden Internet Explorer Not authorized to view this page”

Cause:
The parameter connect.businesslogic.module.cacher.remoteaccess has been commented out in the WCMConfigService.properties file.

Resolution:
To correct the error, remove the comment (uncomment) the following line in the WCMConfigService.properties file:

connect.businesslogic.module.cacher.remoteaccess=true

J2CA0056I Portlet unavailable

Symptom:
Your Web Content Management users report that portlets fail to render content, and the following log:

PortalServer_Home> <em><portalserver_home></portalserver_home></em>\log\SystemOut.log

reports a J2CA0056I exception similar to the following:

J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jdbc/jcrDS. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: No more data to read from socket W Error retrieving information from the server. [ErrorCode:7015] During an SQL operation in the library server, an unexpected error. :No more data to read from socket com.ibm.websphere.ce.cm.StaleConnectionException: No more data to read from socket

The problem is most noticeable after restarting the WebSphere Portal / Web Content Management server.

Cause:
During the server startup process, Web Content Management attempts to connect and initialize the JCR database (in this case, the Oracle Database Server 10G). At this point, the above-mentioned exception is logged to the SystemOut.log when Web Content Management is initializing.

Resolution:
Applying Oracle Patch 4939157 or Oracle Merge Patch 5227920 should correct the problem.

Note that the required Oracle database patches are referenced in the WebSphere Portal 6.0 InfoCenter (select Supported software, then the section Configuring Oracle).

NoClassDefFoundError This portlet is unavailable

Symptoms:
After you successfully log into WebSphere Portal, you do not see any Web Content Management content displayed when browsing to the WCM tab. Also, after browsing to the Administration portlet to verify that the current user is part of the Web Content Management administrators group, you see the message "This portlet is unavailable".

In addition, if you check the SystemOut.log file, you see the following error messages:

ServletWrappe E SRVE0014E: Uncaught service() exception root cause My Portlets:

com.ibm.wps.pe.pc.legacy.impl.TransferPortletException: com/ibm/psw/wcl/components/marquee/WMarquee
at com.ibm.wps.pe.pc.legacy.impl.PortletContextImpl.includeDirect(PortletCo ntextImpl.java:253)
at com.ibm.wps.pe.pc.legacy.impl.PortletContextImpl.include(PortletContextImpl.java:197)
at com.ibm.wps.portlets.struts.WpsStrutsUtil.include(WpsStrutsUtil.java:2179)
at com.ibm.wps.portlets.struts.WpsStrutsViewJspCommand.includeURL(WpsStrutsViewJspCommand.java:189)
at com.ibm.wps.portlets.struts.WpsStrutsViewJspCommand.execute(WpsStrutsViewJspCommand.java:162)
at com.ibm.wps.portlets.struts.WpsStrutsUtil.executeCommand(WpsStrutsUtil.java:1449)
at com.ibm.wps.portlets.struts.WpsStrutsUtil.executeCommand(WpsStrutsUtil.java:1322)
at com.ibm.wps.portlets.struts.WpsStrutsUtil.executeSavedCommand(WpsStrutsUtil.java:1240)
at com.ibm.wps.portlets.struts.WpsStrutsPortlet.doService(WpsStrutsPortlet.java:1325)
at com.ibm.wps.portlets.struts.WpsStrutsPortlet.doView(WpsStrutsPortlet.java:1368)
at org.apache.jetspeed.portlet.PortletAdapter.service(PortletAdapter.java:158)

Nested Exception is java.lang.NoClassDefFoundError: com/ibm/psw/wcl/components/marquee/WMarquee
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java(Compiled Code))
at com.ibm.psw.wcl.core.ClassLoaderUtil.forName(ClassLoaderUtil.java:190)

ItemLocked Exception

Symptoms:
Syndication is failing in your Web Content Management system. Possibly a large volume of messages are being logged in the SystemOut.log with an ItemLockedException message that implicates IWKPD1029X.

A Message similar to that below is seen in the SystemOut.log on the subscriber system. The following will vary from system to system:

<Content_Name>

Content_UUID>

the item type may also vary:

[6/6/08 15:13:38:928 EDT] 000009d2 PackageProces W IWKPD1029X: Could not store doc: (Content_Name), IdRef: {(Content_UUID), com.aptrix.pluto.content.Content} com.ibm.workplace.wcm.services.repository.RepositoryException: IWKMU1062X: Message: An unexpected transaction exception occurred., Cause:
com.ibm.workplace.wcm.services.content.ItemLockedException: Item with identity {(Content_UUID), com.aptrix.pluto.content.Content} is locked.
at com.ibm.workplace.wcm.services.content.ContentServiceImpl.lock(ContentServiceImpl.java(Compiled Code))
at com.ibm.workplace.wcm.services.content.ContentServiceImpl.lock(ContentServiceImpl.java(Inlined Compiled Code))
at com.ibm.workplace.wcm.services.content.ContentServiceUtils.ensureLocked(ContentServiceUtils.java(Compiled Code))
at com.ibm.workplace.wcm.services.content.ContentServiceImpl.update(ContentServiceImpl.java(Compiled Code))
at com.aptrix.deployment.subscri ber.PackageProcessor.repositoryUpdate(PackageProcessor.java(Compiled Code))
at com.aptrix.deployment.subscriber.PackageProcessor.updateItemsInRepository(PackageProcessor.java(Com piled Code))
at com.aptrix.deployment.subscriber.PackageProcessor.finishPackage(PackageProcessor.java(Compiled Code))
at com.aptrix.deployment.subscriber.PackageProcessor.processUpdate(PackageProcessor.java(Compiled Code))
at com.aptrix.deployment.subscriber.PackageProcessor.process(PackageProcessor.java:466)
at com.aptrix.deployment.subscriber.PlutoSubscriberInterface.processPackage(PlutoSubscriberInterface.java:231)
at com.aptrix.syndication.business.subscriber.SubscriberTaskManager.processUpdate(SubscriberTaskManager.java:148)
at com.aptrix.syndication.business.subscriber.SubscriberTaskManager$UpdateTask.doManagedWork
(SubscriberTaskManager.java:109)
at com.aptrix.syndication.business.TaskManager$ManagedTask.run(TaskManager.java:839)
at com.ibm.wps.services.workmanager.impl.WasWorkWrapper.run(WasWorkWrapper.java(Compiled Code))
at com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at javax.security.auth.Subject.doAs(Subject.java(Compiled Code))
at com.ibm.websphere.security.auth.WSSubject.doAs(WSSubject.java(Compiled Code))
at com.ibm.ws.asynchbeans.J2EEContext$DoAsProxy.run(J2EEContext.java(Compiled Code))
at java.security.AccessController.doPrivileged1(Native Method)
at java.security.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java(Compiled Code))
at com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithExecutionContextImpl.java(Compiled Code))
at com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java(Compiled Code))
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))

Caused by: com.ibm.workplace.wcm.services.content.ItemLockedException: Item with identity {, com.aptrix.pluto.content.Content} is locked.
at com.ibm.workplace.wcm.services.repository.RepositorySer viceImpl.lock(RepositoryServiceImpl.java(Compiled Code))
... 26 more

Cause:
The item is locked on the subscriber Web Content Management system. Syndication of the item is failing on the lock.

Resolution:
To resolve the issue:

1. Use the (Content_Name) from the error message to find the piece of content on the syndicator system, using the authoring portlet.

2. Use the authoring portlet to unlock the piece of content identified in step 1. This will prevent the error on the subscriber system the next time syndication is run.

Authorization exception

Symptom:
Authorization exception IWKCC1174X occurs when you follow a link generated by a Web Content Management component linking to a Portal Document Manager object.

Cause:
This error can be due to a mismatch between the PumaService.properties configuration setting user.fbadefault.filter and the WebSphere Member Manager userSecurityNameAttribute par ameter.

Resolution:
Web Content Management uses the attribute of the logged-in user and therefore the attribute specified in the wmm.xml file with the userSecurityNameAttribute parameter.

When authorizing users, Web Content Management searches for them by using the attribute specified in the PumaService.properties configuration setting user.fbadefault.filter. If the attribute specified in the userSecurityNameAttribute (wmm.xml) and the attribute specified by the user.fbadefault.filter (PumaService.properties) setting do not match, then this issue can occur.

user.fbadefault.filter =
Defines the default search attribute for users. Usually this is the same as the Relative Distinguished Name (RDN) attribute of the LDAP. Depending on your environment, it might be a different attribute. The default is set to the same value as that of the LDAPUserPrefix in the file wpconfig.properties.

For version 6.x, you can check and change this setting by logging into the WebSphere Application Server Administrative Console and navigating to Resources > Resource Environment Providers > WP Puma Service > Custom properties.

If needed, update the user.fbadefault.filter. For more information, refer to the Technote, “Usage of the PumaService properties user.fbadefault.filter and user.template.attribute.

Unauthorized error EJPEJ0044I

Symptom:
The portal session times out, so you refresh the screen that contains a Web Content Management viewer rendering portlet. An unauthorized exception occurs with an entry in the ../portalserver/log/systemout.log similar to the following:

[21:29:31:520 EDT] 0000003c WPActionPhase E com.ibm.wps.engine.phases.WPActionPhase isAuthorized EJPEJ0044I:
Unauthorized access to /wps/portal/!ut/p/c1/hZDNDoJADISfxRewBQTkiIBI3BCJ_CxcyIobggHWAJL49i6JV7Q9fp2ZTKEAuT2bm5pNjehZCxQK
o3QISSzdRsRjZKJ6CTxHO4QKJqrkuVEmqXWMSKAovu7bqBok8Qi6iu9qf9TZkvdbv3BcGRshh8JcTThJ3vKaVW_IZqD83kwQnkTHIfKGQQxXPo6yZtx0XLwm6UW_1_lPz8I694JqJmSsWt4E6ci2sba7oV5VCM-O4kPP9zytNx9XTMyW

Cause:
The error occurs when the session object has been invalidated. In this case, it was due to a session timeout. In one particular case, the error occurred when the session object was invalidated by the timeout; that is, it had been 30 minutes since the last activity on the logged-in session.

This error can occur for other issues with the session, for example, with multiple interacting WebSphere Application Server environments using the same name for the session cookie.

WCM Server is not available IllegalStateException

Symptom:
IllegalStateException appears in the WebSphere Portal SystemOut.log "Caused by: java.lang.IllegalStateException: WCM Server is not available"

Cause:
This message will display if WebSphere Portal is installed before the Web Content Management portlet is configured. The “Web Content Management server is not available” exception might be thrown in the WebSphere Portal application server log while stopping WebSphere Portal.

Resolution:
You can safely disregard this error message, which will appear only until the Deploy Authoring portlets customization task runs.
Note that various other causes for IllegalStateException have been resolved by iFixes.

SQL0101N The statement is too long or too complex

Symptom:
Menu components do not render, and the SystemOut.log reports output similar to the following:

[3/26/08 10:06:19:925 EDT] 0000008b Query E com.ibm.icm.da.portable.query.Query openQueryCursor()
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0101N The statement is too long or too complex. SQLSTATE=54001 COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/NT] SQL0101N The statement is too long or too
complex. SQLSTATE=54001
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(Unknown Source)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2PreparedStatement.execute2(Unknown Source)
at COM.ibm.db2.jdbc.app.DB2PreparedStatement.executeQuery(Unknown Source)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteQuery(WSJdbcPreparedStatement.java(Compiled Code))
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeQuery(WSJdbcPreparedStatement.java(Compiled Code))
at com.ibm.icm.da.portable.common.sql.PPreparedStatement.executeQuery(PPreparedStatement.java(Compiled Code))
at com.ibm.icm.da.portable.query.Query.openQueryCursor(Query.java(Compiled Code))

Resolution:
Increasing the STMTHEAP (statement heap) size parameter for DB2 resolves this issue. In most cases the default value of this parameter will be acceptable. However, if you have very large SQL statements and the database manager issues an error that the statement is too complex when it attempts to optimize a statement, you should do the following:

1. Increase the value of the STMTHEAP (statement heap) size parameter for DB2 in regular increments (such as 256 or 1024).
2. Observe the performance of the system, noting if the error reoccurs ("The statement is too long or too complex").
3. Stop increasing the STMTHEAP size when the message ceases to appear.

The Default Ranges for this value are as follows:

32-bit platforms:
2048 [ 128 - 524 288 ]

64-bit platforms:
4096 [ 128 - 524 288 ]

For more information, refer to the Technote, “SQL0101N the statement is too long or too complex. SQLSTATE=54001.”

NOTE: To resolve exceptions related to syndication, refer to the Technote, “Troubleshoot: Web Content Management (WCM) v6 syndication known issues.”

Conclusion

This document has detailed how and what trace strings to enable, depending on the different problematic situations for Web Content Management 6.0. Included are numerous examples of known exceptions, their symptoms, causes, and steps that customers can use to resolve the issue on their own.

Resources

- IBM WebSphere Portal, Version 6.0 Information Center:
http://publib .boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp

- IBM WebSphere Application Server Information Center:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.home.doc/welcome.html

About the author

Noushad Nazmi is a technical consultant for the Lotus Web Content Management team in the IBM Technical Support Center in Pune, India. He is a Web Content Management certified developer and worked extensively with other Portal Server (Weblogic Portal) and Web Content Management software (Interwoven Teamsite) before joining IBM in 2007. He holds degrees in Mathematics and Master of Computer Application with honors. You can reach him at noushad.nazmi@in.ibm.com.


Trademarks
- DB2, IBM, Lotus, Web Content Management, WebSphere, and z/OS are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both.
- Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States, other countries, or both.
- Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
- Other company, product, and service names may be trademarks or service marks of others. >http://publib.boulder.ibm.com/infocenter/wpdoc/v6r0/index.jsp

- IBM WebSphere Application Server Information Center:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/topic/com.ibm.websphere.home.doc/welcome.html