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

Jim Gomes resolved AMQNET-87.
-----------------------------

    Fix Version/s: 1.0
                       (was: 1.1)
       Resolution: Fixed

> CLONE -Strange Disconnect issues with .Net and VS2005
> -----------------------------------------------------
>
>                 Key: AMQNET-87
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-87
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows XP, VS2005, grabbed head of .Net client as of 
> 2/12, useing ActiveMQ 4.1 on server
>            Reporter: Anthony Enache
>            Assignee: Jim Gomes
>             Fix For: 1.0
>
>         Attachments: ResponseCorrelator.patch
>
>
> I have a strange issue.  I'm testing bad network conditions, where the client 
> looses connectivity to the server.  If the server is remote, and the client 
> is inside my lan, and my lan looses internet connection, at least 1 time in 3 
> when the consumer gets created (or at least throws no error messages), but 
> doesn't actually consume messages off of the queue.  This leads to no error 
> message that I can catch, but the client never recieving another message.  
> For reasons that escape me, this happens FAR more frequently when you run 
> this program OUTSIDE of vs2005.  When I run through the debugger, or even 
> through a "Release" build inside vs2005, this very rarely occurs.  Also, 
> though this is much more minor, when the client does manage to reconnect 
> cleanly, I get 2 messages for each one I send, as if the consumer prior to 
> the internet connection loss isn't being deleted.  However, once I start and 
> stop the Connection, I get just one message recieved per message sent.  I'll 
> show this in step form below.  Thanks for your assistance!
> Jamie
> Steps:
> 1.  Run a standard ActiveMQ server on a remote point
> 2.  Run a client inside your lan  (Fixing IP address and port for where the 
> server resides)
> 3.  Click "start" on the app, you'll see the messages your recieving start 
> scrolling down
> 4.  Yank the cord from your router that gives you an external internet 
> connection
> 5.  After about 8 seconds, the text will tell you the disconnect occured, 
> then replug in the cord
> 6.  Click "start" again.  might need to do it more then once, as sometimes 
> it's slow to get a good connection again
> 7.  At least 1 in 3 times after you click "start" it'll clear the text, but 
> you'll never see another message, even if you "stop" and "start" again 
> (leaving the cord alone)
> 8.  The rest of the time you'll see 2 messages appear for each one sent, 
> after clicking "stop" and "start" again, you'll see normal behavior.  
> I've attached both the client project I'm using for testing.  I was using the 
> stock ActiveMQ 4.1 server, only changing the IP Address of the TCP connection 
> to point to the correct address.

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

Reply via email to