I'm trying to access a stateful session bean from
a C# client application using Janeva (Borland).
Janeva is basically a CORBA implementation for .Net platform, that allows us to access any CORBA server and
any J2EE 1.3 application server. Therefore, I've registered
my session bean as an iiop-accesible EJB using the following jboss.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<configuration-name>Standard Stateful SessionBean</configuration-name>
Nextly I deploy the session bean and all seems to go well. I browse the Naming service with a generic client
and there is really an object reference bound to the
name "Interest". However if I inspect the object reference I can see that it points to the direction:
0.0.0.0:3528, and, as a result, if i try to use the
object reference i get an exception saying that
it's impossible to contact the host 0.0.0.0.
It seems that the IP direction is not properly configured in the object reference.
I'm using Jboss 3.2.2 with the configuracion "all" and
the jvm 1.4.2_01 from Sun.
Any idea ?
In addition, if a use a jndi name such as "interest/Interest",
only the first token is registered (as a Naming Context)
in the Naming Service; but not the object reference "Interest".
Yes, this is a bug in JBoss 3.2.2. The bug was not present in JBoss 3.2.2.RC4. It will be fixed in the next release. Meanwhile, there is an easy workaround: pass the server the "--host=<my-ip-addr-or-hostname>" command line argument to set the host address. E.g.:
run.sh -c all --host=my.host.name
run.sh -c all --host=xxx.xxx.xxx.xxx
Without the "--host" argument, JBoss 3.2.2 will use 0.0.0.0 (which is not a valid endpoint) as the host address.