Syndication troubleshooting

Syndication troubleshooting

Issues

Issue Solution
Unable to reach host 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.
Syndicator becomes unresponsive during syndication Syndication can require a large amount of resources to run successfully. Consequently, if server is performing other tasks at the same time as syndication, the process of syndication may slow or stop altogether. You should schedule syndication to occur at times when the server load is at its lowest.
Syndicator status hangs on "Pending", or "Pending, Active" If you are attempting to update or rebuild a syndicated library containing large number of items, the syndicator status might hang on "Pending", or "Pending, Active". This can occur because the syndicator keeps retrying to syndicate when some items fail to syndicate to the subscriber, or when a system timeout occurs on the subscriber when saving data.
Improving the performance of database can help avoid these situations. For example, two of the database attributes that DB2 relies upon to perform optimally are:

Database catalog statistics
Physical organization of the data in the tables

Catalog statistics (DB2 runstats) should be recomputed periodically during the life of the database, particularly after periods of heavy data modifications (inserts, updates, and deletes).
Time-outs during syndication Often caused by the failure of large items to be saved. Increasing the total transaction lifetime timeout setting of IBM WebSphere Portal server can address this issue. The total transaction lifetime timeout setting of subscriber should be at least the same as the syndicator.
To change total transaction lifetime timeout, from the dmgr console...
Servers | Server Types | WebSphere application servers | portal_server | Container Services | Transaction Service

Subscriber becomes unresponsive during syndication If you are attempting to syndicate a library containing more than 10000 items, the subscriber machine might become unresponsive during the syndication operation. This can occur due to an insufficient Java heap size setting on the subscriber.
To update the maximum Java heap size:
System administration | Deployment manager | Java and Process Management | Process Definition | Java Virtual Machine

A value of at least 1024 MB is recommended.
In addition, ensure that you have at least as much swap space allocated on the subscriber machine as you have physical memory.

Options

Reset the web content event log. To assist in the troubleshooting process you can reset the web content event log.
Set deployment.enableReport on the subscriber. To enable high level reporting of syndication to the SystemOut log on the subscriber server, from the WCM WCMConfigService service, specify:
deployment.enableReport = true

Provides a summary of items that were processed, and which items failed syndication.

Syndication concepts

Previous

Set service configuration properties

+
Search Tips | Advanced Search

Issue	Solution
Unable to reach host	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.
Syndicator becomes unresponsive during syndication	Syndication can require a large amount of resources to run successfully. Consequently, if server is performing other tasks at the same time as syndication, the process of syndication may slow or stop altogether. You should schedule syndication to occur at times when the server load is at its lowest.
Syndicator status hangs on "Pending", or "Pending, Active"	If you are attempting to update or rebuild a syndicated library containing large number of items, the syndicator status might hang on "Pending", or "Pending, Active". This can occur because the syndicator keeps retrying to syndicate when some items fail to syndicate to the subscriber, or when a system timeout occurs on the subscriber when saving data. Improving the performance of database can help avoid these situations. For example, two of the database attributes that DB2 relies upon to perform optimally are: Database catalog statistics Physical organization of the data in the tables Catalog statistics (DB2 runstats) should be recomputed periodically during the life of the database, particularly after periods of heavy data modifications (inserts, updates, and deletes).
Time-outs during syndication	Often caused by the failure of large items to be saved. Increasing the total transaction lifetime timeout setting of IBM WebSphere Portal server can address this issue. The total transaction lifetime timeout setting of subscriber should be at least the same as the syndicator. To change total transaction lifetime timeout, from the dmgr console... Servers \| Server Types \| WebSphere application servers \| portal_server \| Container Services \| Transaction Service
Subscriber becomes unresponsive during syndication	If you are attempting to syndicate a library containing more than 10000 items, the subscriber machine might become unresponsive during the syndication operation. This can occur due to an insufficient Java heap size setting on the subscriber. To update the maximum Java heap size: System administration \| Deployment manager \| Java and Process Management \| Process Definition \| Java Virtual Machine A value of at least 1024 MB is recommended. In addition, ensure that you have at least as much swap space allocated on the subscriber machine as you have physical memory.