Hmm I don't know if Jahia is involved here. Basically we take the connection string and give it unmodified to the OpenJMS implementation. Do you get more details on the EOFException ?
Regards, Serge Huber.
Chris Stephens wrote:
Hi folks,
I am setting up a Jahia cluster according to the instructions in the Jahia Clustering HOWTO (v2).
If I set up my two Jahia instances to use RMI to connect to OpenJMS (running on a third server) all is well - except that I cannot then firewall the machines properly because of the anonymous ports used (cf. http://sourceforge.net/mailarchive/message.php?msg_id=9099205).
So I switched across to the TCP connector following the instructions on openjms.sourceforge.net for the setup of OpenJMS. For Jahia I presume this means just changing the line:
org.jahia.cache.jmsCacheContextProviderURL = rmi\://blah.com.au\:1099/
to read:
org.jahia.cache.jmsCacheContextProviderURL = tcp\://blah.com.au\:3030/
And also opening up the appropriate ports: 3030 and 3035.
But this doesn't work and I get the following error in catalina.out:
1315607 [JMS Reconnection] WARN - org.jahia.services.cache.JMSConnectionException: JMS Connection error, Could not get the InitialContext [org.exolab.jms.jndi.InitialContextFactory] on provider [tcp://blah.com.au:3030/]., root cause:Operation getNameParser failed: java.io.EOFException root cause=javax.naming.NamingException: Operation getNameParser failed: java.io.EOFException
I have flushed my iptables so I know it is not a firewall problem.
Is there something else in jahia.properties that should be changed or is this an OpenJMS config error (in which case I'll happily take my query elsewhere: it's just the instructions for OpenJMS appear very complete and the configuration appears very simple).
Thanks in advance,
Chris
*Chris Stephens* > Technology Director phone > +61 2 9779 0129 mobile > +61 403 074 567 fax > +61 2 9779 0199 *http://www.netreturn.com.au*
