Connection refused to host: 127.0.0.1| JBoss.org Content Archive (Read Only)

15. Re: Connection refused to host: 127.0.0.1

abhishek_amity Aug 13, 2003 11:49 PM (in response to adrian.brock)

"Abhishek_Amity" wrote:
"Abhishek_Amity" wrote:
hi ryanho,
i am getting the same problem on windows plateform,
i have used -Djava.rmi.server.hostname entry in run.bat but it doesn't work

In jndi.properties (at client which i try to run from same host) i have specify following entries:

java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
java.naming.provider.url=192.168.0.47:1099
java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

The same application working perfectly while deploying on Jboss3.2.1

Please tell me what should i do to work...

16. Re: Connection refused to host: 127.0.0.1

vashistvishal Aug 14, 2003 7:08 AM (in response to adrian.brock)

"vashistvishal" wrote:
"vashistvishal" wrote:
Under Linux (red hat)
you go to /etc/hosts file
and declare like this,

127.0.0.1 localhost/yrname locahost.localdomain xxxx.tusc.com.au

where xxx is yr name in DNS.
But as aspecified in post you can specify the parameters in run.sh/run.bat in case of windows.
As far as declaring this under windows, I presume you can look into it.

Good Luck....

17. Re: Connection refused to host: 127.0.0.1

holter Aug 19, 2003 1:49 AM (in response to adrian.brock)

"holtermp" wrote:
"holtermp" wrote:
Thanks all,
the solutions provided here work well for me at the moment, but leave me with a new question:

Suppose I have to networks connected to my jboss machine via two network interfaces.
Say one network is 10.20.x.x the other is 10.30.x.x.
Is there any chance to connect to jboss from both networks?

18. Re: Connection refused to host: 127.0.0.1

jonlee Aug 19, 2003 7:56 AM (in response to adrian.brock)

"jonlee" wrote:
"jonlee" wrote:
Yes. The problem is not with external or remote resolution but instead with the JBoss JVM resolving the local network interface to use and correctly binding to that definition.

19. Re: Connection refused to host: 127.0.0.1

claude.glauser Sep 5, 2003 8:30 AM (in response to adrian.brock)

"claude.glauser" wrote:
"claude.glauser" wrote:
The option -Djava.rmi.server.hostname=192.168.1.34
worked well for me if the client connects from the local
network.

Clients outside the network can do nothing with my
local network ipaddress.

Is there a way to provide a callbackhandler, so that
each time my hostname is requested, I can return the
dynamacially assigned ip address of my firewall ?

Thanks a lot for your answers.

20. Re: Connection refused to host: 127.0.0.1

mortena Sep 13, 2003 9:58 AM (in response to adrian.brock)

"mortena" wrote:
"mortena" wrote:
Problem with PostGreSQL connection after this problem has been solved.

I've solved the problem with wrong ip-number, so that the JBoss server now knows that its ip-number is 168.192.1.5, but this gives me a problem as I try to connect to my underlying PostGreSQL server, that will only accept userrequests from localhost. I tryed to edit a .conf file in postGreSQL, so that all connections from the local network is accepted, but without luck.

Any suggestions or links?

21. Re: Connection refused to host: 127.0.0.1

jonlee Sep 14, 2003 11:01 PM (in response to adrian.brock)

"jonlee" wrote:
"jonlee" wrote:
With the latest PostgreSQL releases 7.3.3 and 7.3.4, you enable TCP/IP in postgresql.conf. The line should be:
tcpip_socket = true

I assume this is working and has been tested - telnet to port 5432 of your PostgreSQL server to check.

You can start/restart PostgreSQL with pg_ctl start/pg_ctl reload as appropriate.

If you think your IP address in the JDBC TCP/IP connection is causing the problem, you can change the acceptance value in pg_hba.conf:
host all all 168.192.1.5 255.255.255.0 trust

Modify this accordingly. However, I wouldn't have thought that spoofing packets in Java would be accomplished by the command-line definition of the IP address.

Otherwise, report the errors you are getting in PostgreSQL for the connection, by enabling a sufficient level for debugging - see the PostgreSQL documentation for more information http://www.postgresql.org/.

22. Re: Connection refused to host: 127.0.0.1

swing Oct 7, 2003 10:35 PM (in response to adrian.brock)

"swing" wrote:
"swing" wrote:
I have without any luck tryed to solve our "Connection refused to host" - problem.
We are having no problems connecting from whitin our LAN, but when connectiong from the internet, we get: "Connection refused to host: 192.168.1.11"

We have routed port 1099 to the server, and as I understand, this error indicates that the routing succedes.

We have tryed to correct the etc/host file, but its a little difficult to understand the given examples....

Given my setup:
Local LAN IP of JBoss serverhost: 192.168.1.11
Local LAN computername of JBoss serverhost: \\swing
Extern IP (provided by my ISP): 213.237.XXX.XXX

How should my "host"-file look like (I presume it's the .../system32/drivers/etc/host !?)
I just can't convert the examples in this thread to a configuration we can use.
My original host-file looked like this: 127.0.0.1 localhost

When altering the run.bat, by adding: -Djava.rmi.server.hostname=213.237.XXX.XXX , JBoss will not deploy properly.

By adding: -Djava.rmi.server.hostname=swing , JBoos deploys, but clients get's:
"Connection refused to host: swing"

Using:
JBoss3.2.1
WIN2K PRO DK

I've been working on the problem the whole night know, so I really needs some new ideas !

swing

23. Re: Connection refused to host: 127.0.0.1

claude.glauser Oct 8, 2003 2:09 PM (in response to adrian.brock)

"claude.glauser" wrote:
"claude.glauser" wrote:
Yes, this seems to be a problem.
The address of your server (ip address
or dns name) must be the same outside
and inside your local network because
the object registry (of jndi) returns the address
(where the remote object resides) to the client.
Then the client uses this address (ip or dns name)
to communicate with (or create) that object.

My recommondation: use a dyndns server
or something alike (www.dyndns.org).

24. Re: Connection refused to host: 127.0.0.1

swing Oct 8, 2003 4:22 PM (in response to adrian.brock)

"swing" wrote:
"swing" wrote:
Thank's for the reply, claude!

How would a dyndns server solve my problem?
I already got a public domain (safeon.dk) pointing to my IP.
My IP is static, by the way (213.237.XXX.XXX could be misunderstod as a dynamic IP).

I have web and fileservers running, so port 80, 8080, 21, and 20 is NOT routed to the JBoss server host. Maybe that is a problem...?..... I'll try rerouting port 80 and 8080 to the JBossserver..

swing

PS: I registred yesterday, why does it say: "Registered: Oct, 2001" at my post...lol...?

25. Re: Connection refused to host: 127.0.0.1

claude.glauser Oct 11, 2003 6:44 AM (in response to adrian.brock)

"claude.glauser" wrote:
"claude.glauser" wrote:
Did you try

-Djava.rmi.server.hostname=safeon.dk

?

Your server must be available inside and outside
of your network as safean.dk

Hope this helps.

26. Re: Connection refused to host: 127.0.0.1

swing Oct 11, 2003 5:17 PM (in response to adrian.brock)

"swing" wrote:
"swing" wrote:
Yes, I've tryed that.
The deploy error when trying "-Djava.rmi.server.hostname=safeon.dk" is:
java.net.BindException: Cannot assign requested address: JVM_Bind

Its properly because JBoss cannot access safeon.dk from inside the network, as you said it should.

I've tryed with the following ports routed to the JBoss server: 1099, 1090, 80, 8080, 8083

Am I missing a port or two?
And how do I make the server reachable as safeon.dk from inside my LAN?

thank's, swing

27. Re: Connection refused to host: 127.0.0.1

claude.glauser Oct 13, 2003 12:45 PM (in response to adrian.brock)

"claude.glauser" wrote:
"claude.glauser" wrote:
Hi, I don't think that
you are missing a port
(if you are using a default configuration).

On my machine (linux), I would set the hostname
as follows:

1. On the server machine where JBoss runs, open the file
/etc/hosts as root. Now you should be able to start
JBoss without bind exceptions.

2. Add this line to the bottom of the file "hosts"
192.168.1.33 safeon.dk safeon

3. Save the file and test it:
ping safeon.dk

4. On each client (of your app) on your local area network,
do the same and test it with:

ping safeon.dk

The name safeon.dk must resolve to an ip properly on each
client !

For windows systems (client and server), you don't have a
hosts file (afaik). Look at the online helps.

Hope this helps.

28. Re: Connection refused to host: 127.0.0.1

swing Oct 14, 2003 5:52 PM (in response to adrian.brock)

"swing" wrote:
"swing" wrote:
That helped...
The server now deploys with the "-Djava.rmi.server.hostname=safeon.dk" parameter (thankyou lord....and claude!).

I'm a W2K user, so I added this line in "system32\drivers\etc\hosts":
192.168.1.11 safeon.dk safeon

But...... the client still throws the "Connection refused to host" exception. The hostname is correct, so the change in the "hosts" file is effective.
The client hangs for about 4 minutes, before timing out. Maybe that could give a clue of what i going on.

Heres is a stacktrace of the clientexception:
javax.naming.CommunicationException. Root exception is java.rmi.ConnectException: Connection refused to host: safeon.dk; nested exception is:
java.net.ConnectException: Connection timed out: connect 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:492) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471) at javax.naming.InitialContext.lookup(InitialContext.java:347) at Main.main(Main.java:29) Caused by: java.net.ConnectException: Connection timed out: connect 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) ... 8 more

JNDI properties:
INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"
URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces"
PROVIDER_URL, "safeon.dk:1099"

Context lookup:
jndiContext.lookup("safeon/UserManager")

Ping safeon.dk from remote client resolves into my extern IP, without any change in "hosts" file.

Thank's for u'r help Claude, cause this is a bitch... ;-)

swing

29. Re: Connection refused to host: 127.0.0.1

arabin Oct 17, 2003 5:15 PM (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)