This week's book giveaway is in the General Computing forum.
We're giving away four copies of Arduino in Action and have Martin Evans, Joshua Noble, and Jordan Hochenbaum on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Error while running EjbStateless Client. Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Reply Bookmark "Error while running EjbStateless Client." Watch "Error while running EjbStateless Client." New topic
Author

Error while running EjbStateless Client.

Shubha shitole
Greenhorn

Joined: Oct 12, 2004
Posts: 4
I am using eclipse 3.1 and jboss-3.2.5. Everything works fines till the time I create Stateless Ejb Bean. While running the client application I get the following error. Can anybody help me.
11:51:14,830 WARN [NamingContext] Failed to connect to 192.168.50.142:1099
javax.naming.CommunicationException: Failed to connect to server 192.168.50.142:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.50.142:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:213)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1185)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.test.EjbClient.FirstClient.getHome(FirstClient.java:26)
at com.test.EjbClient.FirstClient.testBean(FirstClient.java:48)
at com.test.EjbClient.FirstClient.main(FirstClient.java:66)
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 192.168.50.142:1099 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:187)
... 7 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:211)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:69)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:62)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:183)
... 7 more
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 192.168.50.142:1099
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1198)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.test.EjbClient.FirstClient.getHome(FirstClient.java:26)
at com.test.EjbClient.FirstClient.testBean(FirstClient.java:48)
at com.test.EjbClient.FirstClient.main(FirstClient.java:66)
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: Error while running EjbStateless Client.
 
Similar Threads
EJB 3.0 Timer Service
how to check whether server is running or not
jboss test suite errors
Eclipse 3 with Jboss3.2.3 using Lomboz 3.0 -> CommunicationException
stopping jboss in myeclipse