qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Rudyy (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (QPID-4473) [Java Client] Resolve "stream might not be closed" issue reported by findbugs tool in JMSObjectMessage
Date Mon, 26 Nov 2012 14:32:58 GMT

     [ https://issues.apache.org/jira/browse/QPID-4473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Rudyy reassigned QPID-4473:
--------------------------------

    Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie,
Could you please review the change?
                
> [Java Client] Resolve "stream might not be closed" issue reported by findbugs tool in
JMSObjectMessage
> ------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-4473
>                 URL: https://issues.apache.org/jira/browse/QPID-4473
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client
>    Affects Versions: 0.16, 0.18
>            Reporter: Alex Rudyy
>            Assignee: Robbie Gemmell
>            Priority: Minor
>             Fix For: 0.21
>
>
> Findbugs reports the error
> "org.apache.qpid.client.message.JMSObjectMessage.read(ByteBuffer) may fail to close stream"

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message