I added some configuration options to the Geronimo plan and related
gbean: http://svn.apache.org/viewvc?view=revision&revision=881988
You can actually set the two properties I added in that commit as -D
vm properties.
I think the use of 0.0.0.0 is the issue. It should be fine to do that
on the server side, but we may just need to work around it for now and
fix it later. Try setting your ${PlanServerHostname} to a "real"
address that is addressable by the client. You may need to update the
"ejbd.discovery" property as well to use the same address, but I think
it might just pick it up.
-David
Begin forwarded message:
Resent-From: <[email protected]>
From: Quintin Beukes <[email protected]>
Date: November 16, 2009 1:14:42 AM PST
To: OpenEJB Users List <[email protected]>
Subject: Odd OpenEJB Remote Connection Behaviour
Reply-To: [email protected]
Hey,
I have noticed something odd, not sure what is causing this.
When I have a client on machine A connecting to a remote OpenEJB
server on machine B everything works well. If I take the exact same
setup but I have another server running on machine A as well (so there
is a client+server on machineA and a server on machineB), OpenEJB
successfully authenticated against machine B but then immediately
switches over all it's following connections to it's own machine (ie.
localhost).
I've noticed if there is no server on machineA with the client, then I
receive the following error on stdout:
WARNING [OpenEJB.client]: Failover: Cannot connect to server(s):
ejbd://0.0.0.0:4201 Exception: Cannot connect to server
'ejbd://0.0.0.0:4201'. Check that the server is started and that the
specified serverURL is correct.. Trying next.
When the server is running, then this doesn't happen. I first noticed
this as follows:
1. I created a user on serverB
2. Authenticated the client against it which worked, so it obviously
connected to the server
3. Started capturing data. The client was showing the data is there,
but the server's database doesn't reflect it.
4. When I did a netstat I noticed a localhost :4201 connection.
5. I removed ALL users from the local machine, but it kept
authenticating.
6. So I restarted the client and did a netstat, there was both a
localhost and 10.0.0.200 :4201 connection. The latter being in
TIME_WAIT.
7. Whenever I stop the server on the local machine all works well as
intended.
Quintin Beukes
