You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomee.apache.org by Billy Vandory <bi...@yahoo.com> on 2010/04/05 17:43:38 UTC

WARNING: Failover: Cannot connect to server(s): ejbd://0.0.0.0:4201

Hi,

I'm running a non-clustered Geronimo 2.2 "out-of-the-box".  If I try and
jndi to openejb on the same machine as geronimo, everything is fine.  If I
jndi from another machine, I get:

WARNING: 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.

Then it promptly fails over to the correct address, connects, and everything
is good.  Here is my client config:

env.put("java.naming.factory.initial",
"org.apache.openejb.client.RemoteInitialContextFactory");
env.put(Context.PROVIDER_URL, "192.168.0.102:4201");

As per another user in this list who had the same issue: I have added
-Dorg.apache.geronimo.openejb.EjbDaemonGBean.host=192.168.0.102 to the
geronimo startup, as well verified I have the latest version of openejb with
the port/host / discoveryURI properties.  

Below is a snip of the config in plan.xml in:

C:\geronimo-tomcat6-javaee5-2.2\repository\org\apache\geronimo\configs\openejb\2
.2\openejb-2.2.car\META-INF>

  <gbean name="EJBNetworkService"
class="org.apache.geronimo.openejb.EjbDaemonGBean">
    <attribute name="port">4201</attribute>
    <attribute name="host">192.168.0.102</attribute>
    <attribute name="threads">200</attribute>
    <attribute name="multicastPort">6142</attribute>
    <attribute name="multicastHost">239.255.3.2</attribute>
    <attribute name="clusterName">cluster1</attribute>
    <attribute name="enableMulticast">true</attribute>
    <attribute name="discoveryURI">ejb:ejbd://192.168.0.102:4201</attribute>
    <attribute name="secure">false</attribute>
    <dependency>
      <name>OpenEjbSystem</name>
    </dependency>
  </gbean>

Shanks,

bv


-- 
View this message in context: http://n4.nabble.com/WARNING-Failover-Cannot-connect-to-server-s-ejbd-0-0-0-0-4201-tp1751735p1751735.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Re: WARNING: Failover: Cannot connect to server(s): ejbd://0.0.0.0:4201

Posted by Kevan Miller <ke...@gmail.com>.
On Apr 5, 2010, at 11:43 AM, Billy Vandory wrote:

> 
> Hi,
> 
> I'm running a non-clustered Geronimo 2.2 "out-of-the-box".  If I try and
> jndi to openejb on the same machine as geronimo, everything is fine.  If I
> jndi from another machine, I get:
> 
> WARNING: 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.
> 
> Then it promptly fails over to the correct address, connects, and everything
> is good.  

Hi Billy,
Sorry for slow response... In your geronimo installation, edit var/config/config-substitution.properties and change

ServerHostname=0.0.0.0
to 
ServerHostname=192.168.0.102

Let me know, if that doesn't work for you. 

--kevan

Re: WARNING: Failover: Cannot connect to server(s): ejbd://0.0.0.0:4201

Posted by David Blevins <da...@visi.com>.
On Apr 5, 2010, at 8:43 AM, Billy Vandory wrote:

>
> Hi,
>
> I'm running a non-clustered Geronimo 2.2 "out-of-the-box".  If I try  
> and
> jndi to openejb on the same machine as geronimo, everything is  
> fine.  If I
> jndi from another machine, I get:
>
> WARNING: 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.
>
> Then it promptly fails over to the correct address, connects, and  
> everything
> is good.  Here is my client config:
>
> env.put("java.naming.factory.initial",
> "org.apache.openejb.client.RemoteInitialContextFactory");
> env.put(Context.PROVIDER_URL, "192.168.0.102:4201");
>
> As per another user in this list who had the same issue: I have added
> -Dorg.apache.geronimo.openejb.EjbDaemonGBean.host=192.168.0.102 to the
> geronimo startup, as well verified I have the latest version of  
> openejb with
> the port/host / discoveryURI properties.
>
> Below is a snip of the config in plan.xml in:
>
> C:\geronimo-tomcat6-javaee5-2.2\repository\org\apache\geronimo 
> \configs\openejb\2
> .2\openejb-2.2.car\META-INF>
>
>  <gbean name="EJBNetworkService"
> class="org.apache.geronimo.openejb.EjbDaemonGBean">
>    <attribute name="port">4201</attribute>
>    <attribute name="host">192.168.0.102</attribute>
>    <attribute name="threads">200</attribute>
>    <attribute name="multicastPort">6142</attribute>
>    <attribute name="multicastHost">239.255.3.2</attribute>
>    <attribute name="clusterName">cluster1</attribute>
>    <attribute name="enableMulticast">true</attribute>
>    <attribute name="discoveryURI">ejb:ejbd://192.168.0.102:4201</ 
> attribute>
>    <attribute name="secure">false</attribute>
>    <dependency>
>      <name>OpenEjbSystem</name>
>    </dependency>
>  </gbean>

Hi Bill,

Setting the discoveryURI should have fixed that completely.  Kevan and  
I have been doing some work in that area in Geronimo 2.2.1 (under  
development).  If you're willing to give that a try we might be able  
to get to the bottom of it -- might already be fixed.  Maybe Kevan can  
push a binary for you to test.

-David