at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.java:1316)
at ditto.createPeerGoneMsg(ConnectionManager.java:1172)
at ditto.handleIdentifyRequest(ConnectionManager.java:228)
at ditto.dispatch(ConnectionManager.java628)
...
Any help would be appreciated.
Thanks
What is the version of the weblogic you're using, and when does
it happen? Do you have a full stack trace? Can you post it here?
Regards,
Slava Imeshev
"Tim" <tho...@san.rr.com> wrote in message
news:cad541a0.03073...@posting.google.com...
Thanks for asking. I regret that it has taken me so long to get back
to you, I hope I haven't discouraged you from maintaining the dialog!
I'm running 6.1 with service pack 3. There is very little more on the
stack trace, but I'll get as much copy as I can and I'll post a second
response to this thread as soon as I can (probably tomorrow, because I
do not have access to the server today). The exception does not
propogate to causing an EJB failure. The interesting thing is that
whenever this exception does NOT occur, I get a transaction timeout
when two or more EJBs are 'chained' together in a container managed
transaction. That is, each bean is flagged as container managed (in
the weblogic-ejb-jar file) and each bean has it's methods flagged as
transaction 'required' (in the ejb-jar files).
Again, I'll post more shortly. If the additional information I have
provided gives you any clues that might help me, please respond at
your earliest.
Thanks,
Tim
"Slava Imeshev" <ime...@yahoo.com> wrote in message news:<3f29460f$1...@newsgroups.bea.com>...
Here is the full stack trace:
<Aug 7, 2003 7:45:31 AM PDT> <Error> <NT Performance Pack> <failure in processSo
ckets() - GetData: 'weblogic.socket.GetData@7ebb41 - fd: '3320', numBytes: '2048
''
java.lang.NullPointerException
at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.jav
a:1316)
at weblogic.rjvm.ConnectionManager.createPeerGoneMsg(ConnectionManager.j
ava:1172)
at weblogic.rjvm.ConnectionManagerServer.handleIdentifyRequest(Connectio
nManagerServer.java:228)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:628)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:658)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:
24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any ideas?
Thanks,
Tim
tho...@san.rr.com (Tim) wrote in message news:<cad541a0.03080...@posting.google.com>...
Regards,
Slava Imeshev
"Tim" <tho...@san.rr.com> wrote in message
news:cad541a0.03080...@posting.google.com...