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 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 >occurs while creating the InitialContext object. > >The JBoss server is behind a router. The first >problem was port 1099 was closed and this caused a >timeout exception. > >I suspect this java.rmi.ConnectException is caused by >the JBoss returning 192.168.1.1 as its name and not >the full name of the machine. The Java client >application is started using a shell script and is >configured using >java.naming.provider.url=jnp://full.host.name:1099 > >I've already tried putting following line: >192.168.1.1 full.host.name >in the /etc/hosts file of the JBoss server. The JBoss >server is running on Red Hat 7.2, with SUN JDK 1.4 and >is at version 3.0.0. > >Any suggestions? > >Thanks, >Leon > > >The exception: > >javax.naming.CommunicationException. Root exception >is >java.rmi.ConnectException: Connection refused to host: >192.168.1.1; >nested exception is: > java.net.ConnectException: Connection refused > at >sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567) > at >sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185) > at >sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171) > at >sun.rmi.server.UnicastRef.invoke(UnicastRef.java:101) > at org.jnp.server.NamingServer_Stub.lookup(Unknown >Source) > at >org.jnp.interfaces.NamingContext.lookup(NamingContext.java:445) > at >org.jnp.interfaces.NamingContext.lookup(NamingContext.java:429) > at >javax.naming.InitialContext.lookup(InitialContext.java:347) > at Tool.<init>(Unknown Source) > at Tool.main(Unknown Source) >Caused by: java.net.ConnectException: Connection >refused > at java.net.PlainSocketImpl.socketConnect(Native >Method) > at >java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) > at >java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161) > at >java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) > at java.net.Socket.connect(Socket.java:425) > at java.net.Socket.connect(Socket.java:375) > at java.net.Socket.<init>(Socket.java:290) > at java.net.Socket.<init>(Socket.java:118) > at >sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22) > at >sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:122) > at >sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562) > > > > >__________________________________________________ >Do you Yahoo!? >Yahoo! News - Today's headlines >http://news.yahoo.com > > >------------------------------------------------------- >Sponsored by: AMD - Your access to the experts on Hammer Technology! >Open Source & Linux Developers, register now for the AMD Developer >Symposium. Code: EX8664 http://www.developwithamd.com/developerlab >_______________________________________________ >JBoss-user mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/jboss-user > > ------------------------------------------------------- This SF.NET email is sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
