[jboss-jira] [JBoss JIRA] Closed: (JBREM-376) problem versioning with not using connection checking

Wed Sep 26 05:31:21 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBREM-376?page=all ]

David Lloyd closed JBREM-376.
-----------------------------


> problem versioning with not using connection checking
> -----------------------------------------------------
>
>                 Key: JBREM-376
>                 URL: http://jira.jboss.com/jira/browse/JBREM-376
>             Project: JBoss Remoting
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: general
>    Affects Versions: 2.0.0.Beta1
>            Reporter: Tom  Elrod
>         Assigned To: Tom  Elrod
>             Fix For: 2.0.0.Beta1
>
>
> Now that remoting sends a byte on the wire to indicate the version, there is a problem when connection checking is turned off (meaning it will not do ack with client to keep connection open).
> The problem stems from ServerThread::processInvocation() where it reads the first byte from the wire.  If not using connection checking and the client closes the connection, the value read will be -1 (which is the behavior when just reading a byte, if where reading an object for example, would have thrown EOFException).  Currently, this -1 will be passed as the version when goes to do versionedRead() call, thus throwing the exception that the given version is not valid.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira