We have recently had a tricky issue to diagnose, so I thought it best to
report it to the mailing list. I have seen a few messages reporting
similar problems so here goes:
Linux based repositories (guessing it doesn't affect win/mac etc.) have
JMS issues with the default openjms.xml config. the webdav repository
connections works fine, and the client connects to the JMS (at the TCP
level) fine, but no messages get sent back to the client.
An error message is reported by our client app every 3 minutes ( we are
using the java adapter ):
11:46:39,831 WARN event:124 - Failed to create JMS Topic connection:
Failed to create connection: java.net.ConnectException: Connection timed
out
11:46:39,831 WARN event:66 - Initializing JMS failed, will retry in
1000 milliseconds.
So it gets connection to the JMS, but then no response to the request
for a topic. In our case, this meant that items were not geting
cache-invalidated, as the client app never recieved change messages.
I found this chunk of info hiding on the hippo site:
"The settings for OpenJMS are very important. Somehow (probably because
of IPv4 and IPv6 interactions) localhost does not resolve correctly
under Linux:
* openjms.server.host should be set to the IP-address of the host.
* openjms.server.internhalhost should be set to localhost."
( from http://www.hippocms.org/display/CMS/2.+Hippo+Repository+Download%
2C+Install+and+Build )
This means that the fix is to find in "(repo-home)/config/openjms.xml"
this line:
<ServerConfiguration host="127.0.0.1" embeddedJNDI="true" />
and switch it to the real (ie. eth0's or whatever) IP address.
Yay we have proper caching across the network again!
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
