Change you hostname in /etc/hostname to the globally unique ip. Also
consider using http-invoker to tunnel thru port 80. Check changelog for
JBoss 3.0.2.
Leon Doud wrote:
>We have successfully deployed EJBs that are used by a
>web application and a Java client application. Both
>of these run
I believe I solved the machine name portion of this:
http://java.sun.com/j2se/1.4/docs/guide/rmi/javarmiproperties.html
Check out the section on java.rmi.server.hostname
Setting this parameter in run.sh fixes the name
returned by RMI to whatever is passed in. In this
case I used the full name of
i changed the following line (i use Suse 8) :
127.0.0.2 tec-ecargnin.sicredi.com.br tec-ecargnin
Leon Doud wrote:
> Here is the hosts file on the JBoss server:
>
> 127.0.0.1 localhost.localdomain localhost
> 192.168.1.1 myname.mydomain.com myname
>
>
> The Java client application u
Here is the hosts file on the JBoss server:
127.0.0.1 localhost.localdomain localhost
192.168.1.1 myname.mydomain.com myname
The Java client application uses:
java.naming.provider.url=jnp://myname.mydomain.com:1099
The JBoss server is behind a Cayman router, so it is
using NAT.
--- Emerson_C
changing the hosts file of the server machine solved the problem for me...
could you show your host file of the server?
Leon Doud wrote:
> We have successfully deployed EJBs that are used by a
> web application and a Java client application. Both
> of these run on the same machine as JBoss.
>
We have successfully deployed EJBs that are used by a
web application and a Java client application. Both
of these run on the same machine as JBoss.
Currently we are trying to run the Java client
application on a different machine and receive the
exception at the bottom of this email. The error
