Subscriber Distribution View Times Out with -503 error

1) Modify the SYS:\ADMINSRV\CONF\MOD_JK\WORKER.PROPERTIES file.

2) Go to the "DEFAULT ajp13 TOMCAT 5 WORKER DEFINITION" section.

3) Modify the worker.ajp13tc5.reply_timeout value and set it to 0.

The following explanation of reply_timeout was taken from http://tomcat.apache.org/connectors-doc-archive/jk2/jk/workershowto.html.

reply_timeout property told web server to wait some time for reply to a forwarded request before considering the remote tomcat is dead and eventually switch to another tomcat in a cluster group.

 

Notes:

 

By default on NetWare the web server will wait 180000 milliseconds. The parameter is the number of milliseconds to wait for reply.  By setting it to 0 it allows for an indefinite wait.  This allows tomcat to keep speaking with Apache while it waits for the XML parsing to finish on the distributor.  To further explain the Subscriber Distribution Process see below.

 

1.  For each subscriber the iManager plug-in makes an edirectory call to get the information about channels and for each channel get the distributions, and for eachdistribution get the distributor object. All these are read and kept.

 

2.  Get all distribution objects for eachdistributor (through xmlrpc process in the form of XML) from distributor. Here a request is made to the distributor to return all the distributions that a subscriber has.

 

3.  For each distribution in the channel get the status of the distribution through xmlrpc or XML format from the distributor. The distributor will read thedistributionTracking.ted& extractionTracking.ted to get information about the distribution  and extraction status, form the XML data and return it to the iManager server.

 

4.  Step 3 is repeated for each distribution that a subscriber has.  If multiple subscribers were picked as part of the subscriber distribution view it parses thedistributionTracking.ted&extractionTracking.ted files once looking for all subscribers selected.

 

5.  Once all status xml's are returned to iManager, they are processed and status is displayed on the SDV view.

 

This process can be seen by setting the log level in iManager to Errors, Warnings and Debug Information messages and watching the Logger Screen on the server.