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] [Updated] (AMQCPP-457) Refactor Transports layer for more control over started / stopped state during initialization
Date Fri, 08 Feb 2013 23:53:13 GMT

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

Timothy Bish updated AMQCPP-457:
--------------------------------

    Description: 
Need to revisit the Transports layer and make the whole create / start / stop process more
deterministic.  The transports should do any connection logic until the filter chain is built
and started as a whole, and once stopped no more async exceptions should come out.  

The filter chain also needs to be modified to better deal with close and destroy.  We need
to ensure that the next Transport is held until destroy and that we walk down the chain and
destroy the lowest one first before allowing high levels Transports to be destroyed. 

  was:Need to revisit the Transports layer and make the whole create / start / stop process
more deterministic.  The transports should do any connection logic until the filter chain
is built and started as a whole, and once stopped no more async exceptions should come out.
 

    
> Refactor Transports layer for more control over started / stopped state during initialization
> ---------------------------------------------------------------------------------------------
>
>                 Key: AMQCPP-457
>                 URL: https://issues.apache.org/jira/browse/AMQCPP-457
>             Project: ActiveMQ C++ Client
>          Issue Type: Improvement
>          Components: Transports
>    Affects Versions: 3.5.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 3.6.0
>
>
> Need to revisit the Transports layer and make the whole create / start / stop process
more deterministic.  The transports should do any connection logic until the filter chain
is built and started as a whole, and once stopped no more async exceptions should come out.
 
> The filter chain also needs to be modified to better deal with close and destroy.  We
need to ensure that the next Transport is held until destroy and that we walk down the chain
and destroy the lowest one first before allowing high levels Transports to be destroyed. 

--
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

Mime
View raw message