My guess is that the error is due to timeout of winsock while reading the response
from the server. Any ideas on how to increase this timeout value? Any help regarding
this matter will be appreciated. My email address is ragg...@coxygen.com
Thanks
-Rakesh
STACK TRACE for exception at the JMS (sender) client:
=====================================================
<Mar 10, 2002 1:32:16 AM PST> <Error> <JavaSocketMuxer> <IOException on socket:
'Socket[addr=rakesh/192.168.1.104,port=7001,localport=1166]'
java.net.SocketException: Descriptor not a socket: JVM_recv in socket input stream
read
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:90)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:
281)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:2
33)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
WebLogic Server (any version) is currently not supported on Windows XP
platform.
Jane Sampson
Developer Relations Engineer
BEA Support
"Rakesh Aggarwal" <ragg...@coxygen.com> wrote in message
news:3c916d3e$1...@newsgroups.bea.com...
_sjz.
"Rakesh Aggarwal" <ragg...@coxygen.com> wrote in message
news:3c916d3e$1...@newsgroups.bea.com...
>
The rest of the stack trace should be my application code invoking the JMS send
in the client.
Anyway, I think Jane's reply on this thread closes the problem for now. WLS is
not certified on XP yet.
-Rakesh
http://groups.google.com/groups?q=SocketException+WLS+6.1+JMS&ie=UTF-8&hl=en&btnG=Google+Search