Watched folder stops working in cluster

[Carman2313]

Hi.

Have you ever seen this, when an XML file is picked up in the watched folder??

2009-08-27 17:52:16,660 ERROR [STDERR] Aug 27, 2009 5:52:16 PM com.adobe.idp.jobmanager.util.JobManagerUtil getQueueConnectionFactory

SEVERE: JobManager:getQueueConnectionFactory():Error:Could not dereference object

2009-08-27 17:52:16,660 ERROR [com.adobe.idp.jobmanager.ejb.JobManagerBean] JobManager:createJob:error sending message:java.lang.RuntimeException: JobManager:getQueueConnectionFactory():Error:

Windows 2003 Server + JBoss + LiveCycle 8.2.1 SP3

Two machines in a cluster.

Works fine in a non-clustered dev environment.  Ported the app to the cluster, changed the watch folder to one shared by both machines, and got this.

Here is the watched folder:

\\xxxfile01a-906\as_shared\livecycle.xxxx.com\shared\documents\LCLetters\

And I know this file was written:

\\xxxfile01a-906\as_shared\livecycle.xxxx.com\shared\documents\LCLetters\input\RAMMLetter.xml

When the file is written, the above quoted errors are posted in server.log.

After those errors appear, the "input" folder mentioned above becomes empty.

In the test environment the watched folder was not a shared folder via UNC, but a local folder in C:  In the new clustered environment, where a shared folder must be used, I have not yet ever seen the watched folder work.  This is the first time I was able to get a file into that watched folder to try.  (In other words, it's not that watched folders were working in the cluster before, and have now stopped.  It's not that other watched folders are working in the cluster.  This is the first and only watched folder being used in the cluster.)

Any ideas?

[JayanKandathil]

Is your JMS configured correctly?  Dbl-check your JMS config instructions.

[Carman2313]

SOLVED:

The following note from a different forum explained and solved the problem:

Your JBoss is not yet fully configured for LiveCycle 8.0.1.  There was a period of time when LiveCycle's documentation accidentally excluded the following configuration steps:

Add the following XML for defining a couple of connection factories to %JBOSS_HOME%\server\all\deploy\jms\hajndi-jms-ds.xml
  <tx-connection-factory>
    <track-connection-by-tx>true</track-connection-by-tx>
    <jndi-name>adobe_JmsQueueXA</jndi-name>
    <xa-transaction/>
    <rar-name>jms-ra.rar</rar-name>
    <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</con nection-definition>
    <adapter-display-name>JMS Adapter</adapter-display-name>
    <config-property type="java.lang.String" name="SessionDefaultType">javax.jms.Topic</config-property>
    <security-domain-and-application>JmsXARealm</security-domain-and-application>
    <config-property type="java.lang.String" name="JmsProviderAdapterJNDI">java:/DefaultJMSProvider</config-property>
  </tx-connection-factory>
  <tx-connection-factory>
    <track-connection-by-tx>true</track-connection-by-tx>
    <jndi-name>adobe_JmsTopicXA</jndi-name>
    <xa-transaction/>
    <rar-name>jms-ra.rar</rar-name>
    <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</con nection-definition>
    <adapter-display-name>JMS Adapter</adapter-display-name>
    <config-property type="java.lang.String" name="SessionDefaultType">javax.jms.Topic</config-property>
    <security-domain-and-application>JmsXARealm</security-domain-and-application>
    <config-property type="java.lang.String" name="JmsProviderAdapterJNDI">java:/DefaultJMSProvider</config-property>
  </tx-connection-factory>