Re: Software Caused Connection Abort (10053) on Client
Bob Scheifler <[email protected]>
| Newsgroups | gmane.comp.java.sun.rmi |
|---|---|
| Message-ID | <[email protected]> |
> FINE: RMI TCP Connection(20)-192.168.54.152: (port 9898) exception:
> java.io.IOException: unknown transport op 115
Ah, that's an important clue.
> I was thinking that if something
> when wrong in StreamRemoteCall that this 115 could be residual data
> before the socket is closed. But then again, you can see that if
> serverCall( call ) returns false,k the socket is closed in the finally
> block, so that seems unlikely.
As Peter Jones pointed out in an earlier thread, server-side failures
don't all result in serviceCall returning false. Read the bug report
he previously referred to:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4716483
Turning on server-side exception logging
-Dsun.rmi.server.exceptionTrace=true
or setting the server-side call logging (sun.rmi.server.call) level
to FINE should make the preceding server-side exception visible,
if that's the culprit.
- Bob
===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS". For general help, send email to
[email protected] and include in the body of the message "help".
For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html
To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html