activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Work logged: (AMQNET-172) Extend IConnection with connection information
Date Wed, 14 Oct 2009 20:25:52 GMT


Timothy Bish logged work on AMQNET-172:

                Author: Timothy Bish
            Created on: 14/Oct/09 01:25 PM
            Start Date: 14/Oct/09 01:24 PM
    Worklog Time Spent: 2 hours 
      Work Description: Added the Connection interrupted / resumed events to the IConnection
interface and implemented the notifications in the Connection class for NMS.ActiveMQ

Issue Time Tracking

            Time Spent: 2 hours
    Remaining Estimate: 0 minutes

> Extend IConnection with connection information
> ----------------------------------------------
>                 Key: AMQNET-172
>                 URL:
>             Project: ActiveMQ .Net
>          Issue Type: New Feature
>          Components: ActiveMQ
>         Environment: Any
>            Reporter: Michel Van Hoof
>            Assignee: Timothy Bish
>             Fix For: 1.2.0
>          Time Spent: 2 hours
>  Remaining Estimate: 0 minutes
> I think it would be "nice" to have some properties on the IConnection interface to get
a status from the connection since while in most cases, you can get this through an exception,
there is no realy way to know when your consumer is connected/disconnected from the broker
when using the failover protocol
> I have tryed to access the FailOverTransport.IsConnected property but apparently, there
is no way to to this when using the IConnectionFactory
> I don't know if it is possible to trigger an event on connect/disconnect from the broker
and create an "isconnected" property ?

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

View raw message