JBossMQ and Unix/Windows mix

[reedmccauley]

Hi,
I'm running JBossMQ (JBoss 3.0.3) on Unix (Tru64). When messages are sent via queues/topics from/to Windows, the trailing exceptions occur. Can you tell me why? Note that message I/O with other Unices works. Thanks very much for any input here.
Reed

15:13:15,635 ERROR [OILClientIL] Cannot connect to the ConnectionReceiver/Server

java.net.SocketException: errno: 47, error: Address family not supported by prot
ocol family for fd: 108
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java, Compiled Cod
e)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java, Compi
led Code)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java, Compiled Code)

at java.net.Socket.(Socket.java, Compiled Code)
at java.net.Socket.(Socket.java, Compiled Code)
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java, Co
mpiled Code)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java, Compile
d Code)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java, Compiled Code)

at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.
java, Compiled Code)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterce
ptorSupport.java, Compiled Code)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java,
Compiled Code)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java, Comp
iled Code)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.
java, Compiled Code)
at java.lang.Thread.run(Thread.java:484)
15:13:15,713 WARN [OILServerILService] Client request resulted in a server exce
ption:
org.jboss.mq.SpyJMSException: Could not pong; - nested throwable: (java.rmi.Remo
teException: Cannot connect to the ConnectionReceiver/Server)
at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.
java, Compiled Code)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterce
ptorSupport.java, Compiled Code)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java,
Compiled Code)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java, Comp
iled Code)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.
java, Compiled Code)
at java.lang.Thread.run(Thread.java:484)
+ nested throwable:
java.rmi.RemoteException: Cannot connect to the ConnectionReceiver/Server
at org.jboss.mq.il.oil.OILClientIL.createConnection(OILClientIL.java, Co
mpiled Code)
at org.jboss.mq.il.oil.OILClientIL.checkSocket(OILClientIL.java, Compile
d Code)
at org.jboss.mq.il.oil.OILClientIL.pong(OILClientIL.java, Compiled Code)

at org.jboss.mq.server.JMSDestinationManager.ping(JMSDestinationManager.
java, Compiled Code)
at org.jboss.mq.server.JMSServerInterceptorSupport.ping(JMSServerInterce
ptorSupport.java, Compiled Code)
at org.jboss.mq.server.TracingInterceptor.ping(TracingInterceptor.java,
Compiled Code)
at org.jboss.mq.server.JMSServerInvoker.ping(JMSServerInvoker.java, Comp
iled Code)
at org.jboss.mq.il.oil.OILServerILService$Client.run(OILServerILService.
java, Compiled Code)
at java.lang.Thread.run(Thread.java:484)

[kerny]

We have the same problem, however, our fd number is "fd: 25".
We are running JBoss 3.0.3 on Linux 2.4.18 (Intel), our JMS client is running on Windows 2000.
Any help is appreciated! What would be nice to know is this "fd: 25" (or "fd: 108" in Reed's stack trace).

Thanks,
-Martin

[kerny]

We fixed it.
It was a mixture of classes compiled with different compilers and running with different JVMs (here: JDK 1.3.1 and JDK 1.4.1)
Check if you are running your classes with the appropriate JVM or recompile them.
Good Luck!
-Martin

[reed]

Hey Martin, Thanks! I'll give it a shot.

Interestingly enough, the Window's JVM is 1.4.1 and Unix' JVM is 1.3.1. It was built on Unix. I would think that backward JVM compatibility would rule-the-day here!

Reed