[
https://issues.apache.org/activemq/browse/AMQNET-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59550#action_59550
]
Timothy Bish commented on AMQNET-254:
-------------------------------------
Failover for a Stomp client is a bit tricky since the Stomp protocol doesn't
have the concept of fault tolerance built in, there's not a simple means of
restoring the active sessions / subscriptions / transactions that were in place
when the connection died. To make things more interesting there's also no
heartbeat mechanism to test if a connection is alive or not so you are left
with using some timeout to determine if the connection is dead which can lead
to needless failover for clients that are simply inactive.
It could be done although on a more simplistic form that what's in the ActiveMQ
client, the failover would need to purge any pending messages and transaction
state info for the client and resubscribe for all the active consumers.
You could take a look at the FailoverTransport and Inactivity monitor classes
in NMS.ActiveMQ and contribute a scaled down version of these to the project,
we love contributions.
> Implement a 'failover' transport for STOMP-provider (similar to the
> ActiveMq-provider)
> --------------------------------------------------------------------------------------
>
> Key: AMQNET-254
> URL: https://issues.apache.org/activemq/browse/AMQNET-254
> Project: ActiveMQ .Net
> Issue Type: Wish
> Components: NMS
> Reporter: Andreas Ländle
> Assignee: Jim Gomes
> Priority: Minor
>
> The NMS implementation for the OpenWire protocol directly supports 'failover'
> - it would be a nice feature if the STOMP provider also supports 'failover'.
> As always - please let me know if i was unclear or if i should provide
> better/more information. Also excuse my bad English.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
