activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQCPP-260) Wrong exception propogated from Transport close methods
Date Mon, 31 Aug 2009 20:19:22 GMT

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

Timothy Bish resolved AMQCPP-260.
---------------------------------

    Resolution: Fixed

Resolved in trunk.  Transports layer is no longer dependent on CMS interfaces.  The close.
stop and start methods all throw IOException now.  

> Wrong exception propogated from Transport close methods
> -------------------------------------------------------
>
>                 Key: AMQCPP-260
>                 URL: https://issues.apache.org/activemq/browse/AMQCPP-260
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 3.0.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.1
>
>
> some close methods in the Transports layer allow exceptions other than the declared type
to be thrown which can cause segfaults on some systems.

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


Mime
View raw message