Syndication troubleshooting

Syndication troubleshooting

+
Search Tips | Advanced Search

Document (item) errors

The document could not be retrieved from the syndicator by the subscriber:

During the syndication update process, the syndicator sends to the subscriber a package that contains the URLs of all the documents that it needs to retrieve to be up to date. The subscriber works through this package retrieving each document from the specified URL. However, the syndicator may not always be able to dispatch the document. There could be several reasons for this:

The document no longer exists: if this is the case, the next update will send through the deletion notice for the document.

The document could not be retrieved: this could be due to the document being corrupted or not being complete. For example some documents rely on external data for completeness. This includes resources and users. Check the syndicator's document errors and you will find a message describing which document it could not retrieve and why. You will need to correct the data for the document in question to be syndicated.

The document could not be saved by the subscriber:

Once the subscriber has all the documents from the syndicator, it then goes ahead and starts to save them (as long as they are valid replication-wise). Some documents may not save because they are expecting other documents to exist. Check the subscriber's document errors and you will find a message describing which document it could not save and why.

Unable to reach host This is a common reason why syndication does not work. The URL for the syndicator or the subscriber may not be valid. You may need to use the IP address rather than the domain name.
Time-outs during syndication Time-outs during syndication are often caused by the failure of large items to be saved. Increasing the total transaction lifetime timeout setting of the WebSphere Portal server can address this issue. The total transaction lifetime timeout setting of the subscriber should be at least the same as the syndicator.
The total transaction lifetime timeout setting is changed using the WebSphere Application Server administrative console. Go to...
Application Servers | server | Container Services | Transaction Service

DuplicateKeyException is thrown while syndicating When items are purged from subscriber the event log table for versions is not properly updated -- version entries are not removed. When doing a full update, and the subscriber attempts to recreate the item, the event log throws a DuplicateKey exception because it still has an entry for the item version.
After purging an item on the subscriber and a full update is kicked off from the syndicator, the subscriber throws an exception when attempting to recreate the item because the version entry for the item still exists in the event log's version table (JCR.EV_VERSION).
0000005a PackageProces W IWKPD1029X: Could not store doc: LONDON Leasing, IdRef: {4b578980435d4685be69ff82fa89bead, com.aptrix.pluto.site.SiteArea} java.lang.RuntimeException: com.ibm.workplace.wcm.services.eventlog.EventLogException: IWKMU1062X: Message: Cannot add version entry for item [Ljava.lang.Object;@adfe8b6., Cause: com.ibm.websphere.ce.cm.DuplicateKeyException: [IBM][CLI Driver][DB2/AIX64] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "JCR.EV_VERSION" from having duplicate rows for those columns. SQLSTATE=23505
Fix: See: PK37257 DuplicateKeyException is thrown while syndicating.

To fix the following...
IWKSY1037X: Unexpected exception thrown while updating subscription: IWKSY1096X: [IceId: <308234234> Current State: <ICE-INITIAL>], exception: java.lang.NumberFormatException: For input string: "N" java.lang.NumberFormatException: For input string: "N" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Long.parseLong(Long.java:394) at java.lang.Long.<init>(Long.java:630)

...redeploy your fixes and then run the update-wcm task after CF updates.

Parent Topic
Syndication

Document (item) errors	The document could not be retrieved from the syndicator by the subscriber: During the syndication update process, the syndicator sends to the subscriber a package that contains the URLs of all the documents that it needs to retrieve to be up to date. The subscriber works through this package retrieving each document from the specified URL. However, the syndicator may not always be able to dispatch the document. There could be several reasons for this: The document no longer exists: if this is the case, the next update will send through the deletion notice for the document. The document could not be retrieved: this could be due to the document being corrupted or not being complete. For example some documents rely on external data for completeness. This includes resources and users. Check the syndicator's document errors and you will find a message describing which document it could not retrieve and why. You will need to correct the data for the document in question to be syndicated. The document could not be saved by the subscriber: Once the subscriber has all the documents from the syndicator, it then goes ahead and starts to save them (as long as they are valid replication-wise). Some documents may not save because they are expecting other documents to exist. Check the subscriber's document errors and you will find a message describing which document it could not save and why.
Unable to reach host	This is a common reason why syndication does not work. The URL for the syndicator or the subscriber may not be valid. You may need to use the IP address rather than the domain name.
Time-outs during syndication	Time-outs during syndication are often caused by the failure of large items to be saved. Increasing the total transaction lifetime timeout setting of the WebSphere Portal server can address this issue. The total transaction lifetime timeout setting of the subscriber should be at least the same as the syndicator. The total transaction lifetime timeout setting is changed using the WebSphere Application Server administrative console. Go to... Application Servers \| server \| Container Services \| Transaction Service
DuplicateKeyException is thrown while syndicating	When items are purged from subscriber the event log table for versions is not properly updated -- version entries are not removed. When doing a full update, and the subscriber attempts to recreate the item, the event log throws a DuplicateKey exception because it still has an entry for the item version. After purging an item on the subscriber and a full update is kicked off from the syndicator, the subscriber throws an exception when attempting to recreate the item because the version entry for the item still exists in the event log's version table (JCR.EV_VERSION). 0000005a PackageProces W IWKPD1029X: Could not store doc: LONDON Leasing, IdRef: {4b578980435d4685be69ff82fa89bead, com.aptrix.pluto.site.SiteArea} java.lang.RuntimeException: com.ibm.workplace.wcm.services.eventlog.EventLogException: IWKMU1062X: Message: Cannot add version entry for item [Ljava.lang.Object;@adfe8b6., Cause: com.ibm.websphere.ce.cm.DuplicateKeyException: [IBM][CLI Driver][DB2/AIX64] SQL0803N One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "1" constrains table "JCR.EV_VERSION" from having duplicate rows for those columns. SQLSTATE=23505 Fix: See: PK37257 DuplicateKeyException is thrown while syndicating.