You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Andreas Ländle (JIRA)" <ji...@apache.org> on 2010/12/29 11:19:45 UTC

[jira] Created: (AMQNET-300) Add new startupMaxReconnectAttempts option to the Failover Transport

Add new startupMaxReconnectAttempts option to the Failover Transport
--------------------------------------------------------------------

                 Key: AMQNET-300
                 URL: https://issues.apache.org/jira/browse/AMQNET-300
             Project: ActiveMQ .Net
          Issue Type: Improvement
          Components: ActiveMQ
    Affects Versions: 1.4.1
            Reporter: Andreas Ländle
            Assignee: Timothy Bish
            Priority: Trivial
             Fix For: 1.5.0


Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.



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

[jira] Updated: (AMQNET-300) NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport

Posted by "Andreas Ländle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Ländle updated AMQNET-300:
----------------------------------

          Component/s:     (was: ActiveMQ)
                       Stomp
        Fix Version/s:     (was: 1.5.0)
          Description: 
Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.

This would also make sense for the STomp Failover-Transport - patch attached.

  was:
Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.



           Patch Info: [Patch Available]
    Affects Version/s:     (was: 1.4.1)
                       1.4.0
              Summary: NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport  (was: Add new startupMaxReconnectAttempts option to the Failover Transport)

> NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-300
>                 URL: https://issues.apache.org/jira/browse/AMQNET-300
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: Stomp
>    Affects Versions: 1.4.0
>            Reporter: Andreas Ländle
>            Assignee: Timothy Bish
>            Priority: Trivial
>         Attachments: startupMaxReconnectAttempts.patch
>
>
> Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  
> This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.
> This would also make sense for the STomp Failover-Transport - patch attached.

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

[jira] Resolved: (AMQNET-300) NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport

Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-300.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0

Patch applied, thanks.

> NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-300
>                 URL: https://issues.apache.org/jira/browse/AMQNET-300
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: Stomp
>    Affects Versions: 1.4.0
>            Reporter: Andreas Ländle
>            Assignee: Timothy Bish
>            Priority: Trivial
>             Fix For: 1.5.0
>
>         Attachments: startupMaxReconnectAttempts.patch
>
>
> Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  
> This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.
> This would also make sense for the STomp Failover-Transport - patch attached (shamelessly a copy of the solution of AMQNET-295).

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

[jira] Updated: (AMQNET-300) NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport

Posted by "Andreas Ländle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Ländle updated AMQNET-300:
----------------------------------

    Description: 
Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.

This would also make sense for the STomp Failover-Transport - patch attached (shamelessly a copy of the solution of AMQNET-295).

  was:
Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  

This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.

This would also make sense for the STomp Failover-Transport - patch attached.


> NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-300
>                 URL: https://issues.apache.org/jira/browse/AMQNET-300
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: Stomp
>    Affects Versions: 1.4.0
>            Reporter: Andreas Ländle
>            Assignee: Timothy Bish
>            Priority: Trivial
>         Attachments: startupMaxReconnectAttempts.patch
>
>
> Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  
> This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.
> This would also make sense for the STomp Failover-Transport - patch attached (shamelessly a copy of the solution of AMQNET-295).

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

[jira] Updated: (AMQNET-300) NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport

Posted by "Andreas Ländle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Ländle updated AMQNET-300:
----------------------------------

    Attachment: startupMaxReconnectAttempts.patch

> NMS.Stomp: Add new startupMaxReconnectAttempts option to the Failover Transport
> -------------------------------------------------------------------------------
>
>                 Key: AMQNET-300
>                 URL: https://issues.apache.org/jira/browse/AMQNET-300
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: Stomp
>    Affects Versions: 1.4.0
>            Reporter: Andreas Ländle
>            Assignee: Timothy Bish
>            Priority: Trivial
>         Attachments: startupMaxReconnectAttempts.patch
>
>
> Add a new option to the FailoverTransport that allows the user to set the number of reconnect attempts allowed when the transport has started but not connected to anything yet.  
> This would superceed the maxReconnectAttempts settings when set only as long as the transport has not connected to anything, once a connection is made then the mxReconnectAttempts option is used from then on.
> This would also make sense for the STomp Failover-Transport - patch attached.

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