createQueueConnection and RC: 134 Transport end points not connected

[ach...@telcordia.com]

Hi guys -

I am very new to websphere app server .

we are using JMS default messaging in WAS 6.1 .

When we try to make following call
queueConnection = getQueueConnectionFactory().createQueueConnection();
queueConnection.start();

I get this message

Jun 22, 2009 3:40:26 PM com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl
AUDIT: chain.started

and its just hangs here .

when i looked at ffdc logs

i saw that during this time its throws following message

tack Dump = com.ibm.ws.sib.jfapchannel.JFapConnectionBrokenException: CWSIJ0051E: An unexpected condition caused a network connec
tion from host 192.4.2.2 using chain InboundBasicMessaging to close.
at com.ibm.ws.sib.jfapchannel.impl.InboundConnection.invalidateImpl(InboundConnection.java:147)
at com.ibm.ws.sib.jfapchannel.impl.Connection.nonThreadSafeInvalidate(Connection.java:1202)
at com.ibm.ws.sib.jfapchannel.impl.Connection.invalidate(Connection.java:1183)
at com.ibm.ws.sib.jfapchannel.impl.ConnectionReadCompletedCallback.error(ConnectionReadCompletedCallback.java:592)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:208)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AbstractAsyncFuture.completed(AbstractAsyncFuture.java:170)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:206)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:751)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:881)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)
Caused by: java.io.IOException: Async IO operation failed, reason: RC: 134 Transport endpoint is not connected
... 4 more

My questions is
do i need to specify something in Connection factory so that it will allow outside JMS client to connect ??
when i used IBM JMS client this works fine .

I even tried to specify end provider info in Queue Connection factory but no luck .

I would really appreciates if somebody know what to do .

Thanks,

[Anant]

Can you enable the trace with the following string. You will get some more detailed info on this error.

TCPChannel=fine:
com.ibm.io.async.*=all:
ChannelFramework=all:
ChannelFrameworkService=all:
SIBCommunications=all:
SIBJFapChannel=all

Anant

[ach...@telcordia.com]

Thanks for getting back to me . I tried with above trace

still get java.io.IOException: Async IO operation failed, reason: RC: 134

no verbose error .

-:(