[
https://issues.apache.org/activemq/browse/AMQNET-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michel Van Hoof updated AMQNET-172:
-----------------------------------
Priority: Major (was: Minor)
Issue Type: New Feature (was: Improvement)
I have upped the priority since at this point, this is a blocker on an
infrastructure we are building. When you have clients that are not under your
own control with a connection that is not under your control, you want to be
able to determine if you can send data or should. Once you start sending data
on a connection that is no longer active ( internet problems ?) and the machine
get's rebooted by the local people, you will loose messages or have a hanging
application (will keep on trying to send while connection is not there)
This could simply be avoided with the possibility to check the actual state of
the underlying transport (isConnected , then yes.. try to send, if not, don't
try)
> Extend IConnection with connection information
> ----------------------------------------------
>
> Key: AMQNET-172
> URL: https://issues.apache.org/activemq/browse/AMQNET-172
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: ActiveMQ Client
> Environment: Any
> Reporter: Michel Van Hoof
> Assignee: Jim Gomes
> Fix For: 1.2.0
>
>
> 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.
