Hi Tim,
From the openjms.xml page [1]:
This is only applicable when the OpenJMS server is behind a NAT
firewall. It becomes the internal address the server is known by and the
host address in ServerConfiguration is the external address. Clients
will attempt to connect to host first. If that fails, they will try to
connect to internalHost.
So basically if you set one of both properties to the external ip it
will work fine. To avoid timeouts you're probably better of by setting
the host to the external ip address (like you've done). You only need to
do this if you connect to the repository from a remote server of course.
It's indeed an easy thing to overlook, so I guess it could have a more
prominent place on the wiki.
Regards,
Bart
[1] http://openjms.sourceforge.net/config/reference.html
toolman wrote:
Just make the wiki state this a bit more forcefully, very easy to miss!
-Toolman
On Wed, 2008-05-14 at 16:01 +0200, Ard Schrijvers wrote:
Hello Tim,
Really great to share your findings with us and give feedback! Do you
have some recommendation about how to adjust
http://www.hippocms.org/display/CMS/2.+Hippo+Repository+Download%252C+In
stall+and+Build
To avoid others having the same troubles you guys were experiencing? Is
the page not complete enough, or is the page hard to find, or is it easy
to overlook, or...anything else?
Regards Ard and thanks again for sharing
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
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
--
Hippo B.V. - Amsterdam
Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466
Hippo USA Inc. - San Francisco
101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646
-----------------------------------------------------------------
http://www.onehippo.com - [EMAIL PROTECTED]
-----------------------------------------------------------------
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
