Error 500 MAPPING configuration| JBoss.org Content Archive (Read Only)

1. Re: Connection refused to host: 127.0.0.1

deathstar Jan 21, 2002 9:34 AM (in response to adrian.brock)

"Tobias" wrote:
"Tobias" wrote:
On newer versions of JBoss the error message may vary, one reads:

javax.naming.CommunicationException. Root exception is
java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:567)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)

RedHat installations are known to have a wrong /etc/hosts file on the SERVER. You need to check the following on the SERVER.

The command "hostname" returns the used hostname, let's say it is "peterpan". /etc/hosts needs to look like this then:

10.0.0.1 peterpan
127.0.0.1 localhost.localdomain localhost

After that change "ping peterpan" should NOT ping to 127.0.0.1 but to the server IP address which was assumed to be 10.0.0.1 in the above example.

Restart the JBoss server now and try again.

2. Re: Connection refused to host: 127.0.0.1

tommygan Jan 21, 2002 9:34 AM (in response to adrian.brock)

"arabin" wrote:
"arabin" wrote:
I am running Jboss 3.2.2RC3 on Linux RedHat 9, version 2.4.20-8 #1
I am experiancing problems with connecting from java program on one machine (192.168.1.43) to Jboss running on another one (192.168.1.40).
The java program creates initial context using the following code
{
Properties prop = new Properties ();
prop.put (Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
prop.put (Context.PROVIDER_URL, jnp://192.168.1.40:1099");
prop.put (Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
initCtx = new InitialContext (prop);
}
Then it creates
QueueConnectionFactory qfact = (QueueConnectionFactory) initCtx.lookup("QueueConnectionFactory");

Then it creates other staff (QueueConnection, Queue, QueueSender) and sends the message.

Everything works OK under Windows (when both machines are windows XP machines), the messages from machine 192.168.1.43 are sent correctly to machine 192.168.1.40

Under Linux situation is different. I try various versions of the file /etc/hosts on machine 192.168.1.40, as well as different ways to start Jboss on 192.168.1.40 machine. Those two different ways are with the line -Djava.rmi.server.hostname=192.168.1.40 and without this option in my run.sh file.

Any ideas?

The results are the following:
/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
option -Djava.rmi.server.hostname=192.168.1.40
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.1.40 192.168.1.40
option -Djava.rmi.server.hostname=192.168.1.40
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost 192.168.1.40
option -Djava.rmi.server.hostname=192.168.1.40
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
no output, send from 192.168.1.43 completed correctly, but message driven bean on 192.168.1.40 did not get the results

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.40 localhost.localdomain localhost 127.0.0.1
option -Djava.rmi.server.hostname=192.168.1.40
server output (192.168.1.40)
2003-10-17 17:49:40,720 DEBUG [org.jboss.mq.il.oil.OILClientIL] ConnectionReceiverOILClient is connecting to: 127.0.0.1:54027
2003-10-17 17:49:40,726 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
2003-10-17 17:49:40,742 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-10-17 17:49:40,745 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-10-17 17:49:40,746 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-10-17 17:49:40,746 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:827)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:183)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
... 5 more
client output (192.168.1.43)
no output, send from 192.168.1.43 completed correcttly

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.40 localhost.localdomain localhost
option -Djava.rmi.server.hostname=192.168.1.40
server output (192.168.1.40)
2003-10-17 17:53:40,769 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
2003-10-17 17:53:40,842 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-10-17 17:53:40,846 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-10-17 17:53:40,846 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-10-17 17:53:40,846 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:827)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:183)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
... 5 more
client output (192.168.1.43)
no output, send from 192.168.1.43 completed correcttly

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
no option -Djava.rmi.server.hostname=192.168.1.40, just plain start
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correcttly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
IP 192.168.1.40 Host 192.168.1.40 initCtx javax.naming.InitialContext@cb6009
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSenderImpl.obtainQueueConnectionFactory(MessageServiceObjectSenderImpl.java:357)
>That is call initCtx.lookup("QueueConnectionFactory");
at com.wrn.teamworks.cms.cms.MessageServiceObjectSender.finallySendToHubAndWait(MessageServiceObjectSender.java:378)
at com.wrn.teamworks.cms.cms.MessageServiceObjectHighSender.sendAndWaitResponse(MessageServiceObjectHighSender.java:382)
at com.wrn.teamworks.cms.cms.MessageServiceObject.sendAndReceive(MessageServiceObject.java:659)
at com.wrn.teamworks.cms.client.ExampleRemoteSenderAndAsynchWaiter.main(ExampleRemoteSenderAndAsynchWaiter.java:59)
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.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:528)
... 7 more
Caused by: java.net.ConnectException: Connection refused
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:124)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 12 more

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.1.40 192.168.1.40
no option -Djava.rmi.server.hostname=192.168.1.40, just plain start
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correcttly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
same thing
IP 192.168.1.40 Host 192.168.1.40 initCtx javax.naming.InitialContext@cb6009
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSenderImpl.obtainQueueConnectionFactory(MessageServiceObjectSenderImpl.java:357)
>That is call initCtx.lookup("QueueConnectionFactory");
at com.wrn.teamworks.cms.cms.MessageServiceObjectSender.finallySendToHubAndWait(MessageServiceObjectSender.java:378)
at com.wrn.teamworks.cms.cms.MessageServiceObjectHighSender.sendAndWaitResponse(MessageServiceObjectHighSender.java:382)
at com.wrn.teamworks.cms.cms.MessageServiceObject.sendAndReceive(MessageServiceObject.java:659)
at com.wrn.teamworks.cms.client.ExampleRemoteSenderAndAsynchWaiter.main(ExampleRemoteSenderAndAsynchWaiter.java:59)
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.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:528)
... 7 more
Caused by: java.net.ConnectException: Connection refused
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:124)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 12 more

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost 192.168.1.40
no option -Djava.rmi.server.hostname=192.168.1.40, just plain start
server output (192.168.1.40)
no output, send from 192.168.1.43 completed correcttly, but message driven bean on 192.168.1.40 did not get the results
client output (192.168.1.43)
same thing
IP 192.168.1.40 Host 192.168.1.40 initCtx javax.naming.InitialContext@cb6009
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: 127.0.0.1; nested exception is:
java.net.ConnectException: Connection refused]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:647)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSenderImpl.obtainQueueConnectionFactory(MessageServiceObjectSenderImpl.java:357)
>That is call initCtx.lookup("QueueConnectionFactory");
at com.wrn.teamworks.cms.cms.MessageServiceObjectSender.finallySendToHubAndWait(MessageServiceObjectSender.java:378)
at com.wrn.teamworks.cms.cms.MessageServiceObjectHighSender.sendAndWaitResponse(MessageServiceObjectHighSender.java:382)
at com.wrn.teamworks.cms.cms.MessageServiceObject.sendAndReceive(MessageServiceObject.java:659)
at com.wrn.teamworks.cms.client.ExampleRemoteSenderAndAsynchWaiter.main(ExampleRemoteSenderAndAsynchWaiter.java:59)
Caused by: java.rmi.ConnectException: Connection refused to host: 127.0.0.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:528)
... 7 more
Caused by: java.net.ConnectException: Connection refused
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:124)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:562)
... 12 more

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.40 localhost.localdomain localhost 127.0.0.1
no option -Djava.rmi.server.hostname=192.168.1.40, just plain start
server output (192.168.1.40)
2003-10-17 18:09:42,049 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
2003-10-17 18:09:42,076 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-10-17 18:09:42,079 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-10-17 18:09:42,080 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-10-17 18:09:42,080 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:827)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:183)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
... 5 more
2003-10-17 18:09:42,265 DEBUG [org.jboss.mq.il.oil.OILClientIL] ConnectionReceiverOILClient is connecting to: 127.0.0.1:54494
2003-10-17 18:09:42,266 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.close(OILClientIL.java:72)
at org.jboss.mq.server.JMSDestinationManager.connectionClosing(JMSDestinationManager.java:569)
at org.jboss.mq.server.JMSServerInterceptorSupport.connectionClosing(JMSServerInterceptorSupport.java:112)
at org.jboss.mq.security.ServerSecurityInterceptor.connectionClosing(ServerSecurityInterceptor.java:61)
at org.jboss.mq.server.TracingInterceptor.connectionClosing(TracingInterceptor.java:158)
at org.jboss.mq.server.JMSServerInvoker.connectionClosing(JMSServerInvoker.java:114)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:268)
at java.lang.Thread.run(Thread.java:534)
client output (192.168.1.43)
javax.jms.IllegalStateException: The session is closed
at org.jboss.mq.SpyQueueSession.createSender(SpyQueueSession.java:128)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSenderImpl.getQueueHubSender(MessageServiceObjectSenderImpl.java:864)
> in the line QueueSender queueSender = session.createSender(queue);
at com.wrn.teamworks.cms.cms.MessageServiceObjectSender.finallySendToHubAndWait(MessageServiceObjectSender.java:383)
at com.wrn.teamworks.cms.cms.MessageServiceObjectHighSender.sendAndWaitResponse(MessageServiceObjectHighSender.java:382)
at com.wrn.teamworks.cms.cms.MessageServiceObject.sendAndReceive(MessageServiceObject.java:659)
at com.wrn.teamworks.cms.client.ExampleRemoteSenderAndAsynchWaiter.main(ExampleRemoteSenderAndAsynchWaiter.java:59)

/etc/hosts on machine 192.168.1.40
# Do not remove the following line, or various programs
# that require network functionality will fail.
192.168.1.40 localhost.localdomain localhost
no option -Djava.rmi.server.hostname=192.168.1.40, just plain start
server output (192.168.1.40)
2003-10-17 18:15:19,061 DEBUG [org.jboss.mq.il.oil.OILClientIL] ConnectionReceiverOILClient is connecting to: 127.0.0.1:54578
2003-10-17 18:15:19,067 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
2003-10-17 18:15:19,093 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.parentTraceEnabled=true
2003-10-17 18:15:19,096 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2003-10-17 18:15:19,097 DEBUG [org.jboss.util.NestedThrowable] org.jboss.util.NestedThrowable.detectDuplicateNesting=true
2003-10-17 18:15:19,097 WARN [org.jboss.mq.il.oil.OILServerILService] Client request resulted in a server exception:
org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:827)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterceptorSupport.java:308)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java:712)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java:310)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:329)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:183)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java:112)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.java:823)
... 5 more
2003-10-17 18:15:19,279 DEBUG [org.jboss.mq.il.oil.OILClientIL] ConnectionReceiverOILClient is connecting to: 127.0.0.1:54578
2003-10-17 18:15:19,279 ERROR [org.jboss.mq.il.oil.OILClientIL] Cannot connect to the ConnectionReceiver/Server
java.net.ConnectException: Connection refused
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:153)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java:175)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java:156)
at org.jboss.mq.il.oil.OILClientIL.close(OILClientIL.java:72)
at org.jboss.mq.server.JMSDestinationManager.connectionClosing(JMSDestinationManager.java:569)
at org.jboss.mq.server.JMSServerInterceptorSupport.connectionClosing(JMSServerInterceptorSupport.java:112)
at org.jboss.mq.security.ServerSecurityInterceptor.connectionClosing(ServerSecurityInterceptor.java:61)
at org.jboss.mq.server.TracingInterceptor.connectionClosing(TracingInterceptor.java:158)
at org.jboss.mq.server.JMSServerInvoker.connectionClosing(JMSServerInvoker.java:114)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.java:268)
at java.lang.Thread.run(Thread.java:534)
client output (192.168.1.43)
javax.jms.IllegalStateException: The session is closed
at org.jboss.mq.SpyQueueSession.createSender(SpyQueueSession.java:128)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSenderImpl.getQueueHubSender(MessageServiceObjectSenderImpl.java:864)
at com.wrn.teamworks.cms.cms.MessageServiceObjectSender.finallySendToHubAndWait(MessageServiceObjectSender.java:383)
at com.wrn.teamworks.cms.cms.MessageServiceObjectHighSender.sendAndWaitResponse(MessageServiceObjectHighSender.java:382)
at com.wrn.teamworks.cms.cms.MessageServiceObject.sendAndReceive(MessageServiceObject.java:659)
at com.wrn.teamworks.cms.client.ExampleRemoteSenderAndAsynchWaiter.main(ExampleRemoteSenderAndAsynchWaiter.java:59)

3. Re: Error 500 MAPPING configuration

adrian.brock Jan 21, 2002 9:38 AM (in response to adrian.brock)

The correct url is
http://localhost/jboss

JBoss does not use the Tomcat configuration.
Instead Tomcat/Catalina is running embedded within
JBoss.
Web Applictions run from $JBOSS_HOME/jboss/deploy.

There is a test deployment when you first install
JBoss2.4.4, but this is not in the "ROOT" context.
Instead it is in "/jboss".

If you look in jboss-test.ear at META-INF/application.xml
you will see where this is specified.

Regards,
Adrian

4. Re: Error 500 MAPPING configuration

skarlson Jan 29, 2002 7:50 PM (in response to adrian.brock)

You could for example make a empty war containing only
WEB-INF/web.xml and map it in the application.xml to
the root context /

5. Re: Error 500 MAPPING configuration

li_zjun Feb 5, 2002 7:45 PM (in response to adrian.brock)

How can I access the web page of "index.html" under the dirctory of ROOT

6. Re: Error 500 MAPPING configuration

adrian.brock Feb 6, 2002 6:32 AM (in response to adrian.brock)

1) Create a directory called ".war"
2) Add a file called index.html
3) Add a sub-directory called WEB-INF
4) In WEB-INF create a web.xml with the following content
[pre]
<?xml version="1.0" encoding="ISO-8859-1"?>

<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">

<web-app>
</web-app>
[/pre]
5) Copy the directory to jboss/deploy
6) Use http://localhost:8080/

To avoid the .war rubbish, use a ROOT.ear and set
the context in application.xml (not explained here)

Regards,
Adrian

7. Re: Error 500 MAPPING configuration

mbuc Feb 13, 2002 3:35 AM (in response to adrian.brock)

Great, it works!
I also tried to make a war file called ".war" in the deploy directory as you specified and it also worked.

thanks,
Marco.

8. Re: Error 500 MAPPING configuration

igor_dik Feb 13, 2002 6:08 PM (in response to adrian.brock)

In Windows you are not allowed to create .war directory - so I've created ROOT.war - it works.

9. Re: Error 500 MAPPING configuration

adrian.brock Feb 14, 2002 5:23 AM (in response to adrian.brock)

:-)

This is a bug in explorer.exe, it is typically
windows nannying.

If you use your mouse and do start/run
and run cmd.exe

The type
mkdir .war

you can create a .war directory.

Regards,
Adrian

10. Re: Error 500 MAPPING configuration

igor_dik Feb 14, 2002 11:22 PM (in response to adrian.brock)

Yes, you are right

11. Re: Error 500 MAPPING configuration

jimskit Apr 11, 2002 11:05 PM (in response to adrian.brock)

I am using Jboss 2.4.4 Tomcat 4.0.1 and Java 1.4
and after creating and successfully deploying the ROOT.war directory and files into the deploy directory I get the same error.

Is there any other stuff to do apart from the war deploy?

Thanks for you help.

12. Re: Error 500 MAPPING configuration

jwalker Apr 18, 2002 11:22 AM (in response to adrian.brock)

I have also had this problem with 2.4.4. Making the .war directory under the deploy directory thing worked although I'm not too sure what this is aiming to achieve. I can't seem to get jboss to automatically extract .war files at all. I have tried placing them in the webapps directory under catalina and the deploy directory under jboss without any joy in either case. Anybody know why jboss has changed the way it works like this, things seemed a helluva lot easier before.

13. Re: Error 500 MAPPING configuration

jmichel Jun 29, 2002 6:53 AM (in response to adrian.brock)

Have a look at: http://telia.dl.sourceforge.net/sourceforge/jboss/JBoss.3.0QuickStart.pdf

14. Re: Error 500 MAPPING configuration

xbird Jun 30, 2002 4:05 AM (in response to adrian.brock)

I'm a beginner.
If I don't want to orginized my jsp files into .war file.
How i can do?
For example, i already have an app(just jsp and servlet) can run in single tomcat.Now i want to immigrate to jboss-3.0.0_tomcat-4.0.3.
In the single tomcat ,i can config the server.xml and set the docBase,then i can visit my app via URL i defined .
But now, the jboss will not use the \catalina\conf\server.xml,
I want to visit my app vis http://127.0.0.1:8080/myApp/index.jsp. how i can achieve it!