river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Jones (JIRA)" <j...@apache.org>
Subject [jira] Created: (RIVER-143) (mux) missing session-handling logic after InputStream.close
Date Fri, 27 Jul 2007 22:09:52 GMT
(mux) missing session-handling logic after InputStream.close

                 Key: RIVER-143
                 URL: https://issues.apache.org/jira/browse/RIVER-143
             Project: River
          Issue Type: Bug
          Components: net_jini_jeri
    Affects Versions: jtsk_2.0
            Reporter: Peter Jones
            Priority: Minor

Bugtraq ID [5088260|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5088260]

>From an old note-- I haven't investigated this in detail recently, but the assertions
still seem true:

bq. In looking at the mux code, I see that there is some missing logic in the handling of
InputStream.close in that it doesn't provide a way to keep sending IncrementRations (important
if the server hasn't terminated the session), nor does it automatically send Close if appropriate
(if the server has finished the session)-- the order in which our code does things doesn't
expose these deficiencies, though.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message