[jira] Created: (AMQNET-294) durable subscription message loss when master broker fails to slave

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (AMQNET-294) durable subscription message loss when master broker fails to slave

JIRA jira+amqnet@apache.org
durable subscription message loss when master broker fails to slave
-------------------------------------------------------------------

                 Key: AMQNET-294
                 URL: https://issues.apache.org/activemq/browse/AMQNET-294
             Project: ActiveMQ .Net
          Issue Type: Bug
          Components: NMS
    Affects Versions: 1.4.1
         Environment: Windows 7 (client), Windows Server 2008 64-bit (server brokers run on), Sql Server 2008 (database)
            Reporter: Mark Gellings
            Assignee: Jim Gomes
             Fix For: 1.5.0
         Attachments: Apache.NMS.Test.zip

We are seeing message loss on a durable subscription when using NMS ActiveMQ v1.4.1 and ActiveMQ v5.4.1.

Please run the included NUnit test and watch the console output.  When it says "Failover the broker now!" do as it says.  About 75% of the time less than half of the expected 250 messages come through.

Using version 1.1 of NMS the majority of the time the test passes.  I have seen it fail only a few times with this earlier version, and when it does there are only a couple messages that don't come through.

In the zip file will be the unit test, and a config directory containing the master and slave activemq configurations.  We are using JDBC master/slave.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (AMQNET-294) durable subscription message loss when master broker fails to slave

JIRA jira+amqnet@apache.org

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

Mark Gellings updated AMQNET-294:
---------------------------------

    Attachment: Apache.NMS.Test.zip

> durable subscription message loss when master broker fails to slave
> -------------------------------------------------------------------
>
>                 Key: AMQNET-294
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-294
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.4.1
>         Environment: Windows 7 (client), Windows Server 2008 64-bit (server brokers run on), Sql Server 2008 (database)
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>             Fix For: 1.5.0
>
>         Attachments: Apache.NMS.Test.zip
>
>
> We are seeing message loss on a durable subscription when using NMS ActiveMQ v1.4.1 and ActiveMQ v5.4.1.
> Please run the included NUnit test and watch the console output.  When it says "Failover the broker now!" do as it says.  About 75% of the time less than half of the expected 250 messages come through.
> Using version 1.1 of NMS the majority of the time the test passes.  I have seen it fail only a few times with this earlier version, and when it does there are only a couple messages that don't come through.
> In the zip file will be the unit test, and a config directory containing the master and slave activemq configurations.  We are using JDBC master/slave.

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

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQNET-294) durable subscription message loss when master broker fails to slave

JIRA jira+amqnet@apache.org
In reply to this post by JIRA jira+amqnet@apache.org

    [ https://issues.apache.org/activemq/browse/AMQNET-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63581#action_63581 ]

Jan Vogelgesang commented on AMQNET-294:
----------------------------------------

It looks that it can be similar problem to AMQNET-293.

If you your connection to broker is lost when you are in OnMessage method then your consumer may not be recovered. I suspect that if you remove Sleep(200) from OnMessage it will behave better... (less time you spend in OnMessage then less chance that connection break will happen there)

Please build NMS from trunk but use the MessageConsumer.cs file I put as the solution to the AMQNET-293 and let me know if it helps.


> durable subscription message loss when master broker fails to slave
> -------------------------------------------------------------------
>
>                 Key: AMQNET-294
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-294
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.4.1
>         Environment: Windows 7 (client), Windows Server 2008 64-bit (server brokers run on), Sql Server 2008 (database)
>            Reporter: Mark Gellings
>            Assignee: Jim Gomes
>             Fix For: 1.5.0
>
>         Attachments: Apache.NMS.Test.zip
>
>
> We are seeing message loss on a durable subscription when using NMS ActiveMQ v1.4.1 and ActiveMQ v5.4.1.
> Please run the included NUnit test and watch the console output.  When it says "Failover the broker now!" do as it says.  About 75% of the time less than half of the expected 250 messages come through.
> Using version 1.1 of NMS the majority of the time the test passes.  I have seen it fail only a few times with this earlier version, and when it does there are only a couple messages that don't come through.
> In the zip file will be the unit test, and a config directory containing the master and slave activemq configurations.  We are using JDBC master/slave.

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