activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gul <>
Subject Re: [jira] Commented: (AMQ-1746) ActiveMQ server does not release the connection on a reconnect
Date Tue, 10 Jun 2008 10:27:10 GMT

When i disable the network i got the following exception at activemq
console, after network connection has established again, the javascript
application running on same machine (where server is running also) works
fine but the other machines running same javascript application  connected
to my machine(server running on my machine) unable to work properly.. in
this case all handlers are lost which are establised using
amq.addListener("id", myTopic, myHandler); MessageListenerServlet fail to
get JMS response 

ERROR MulticastDiscoveryAgent        - Failed to advertise our service:
ActiveMQ-4.alive.%localhost%tcp://sgul:61616 No route to host: Datagram send failed
        at Method)

JIRA wrote:
>     [
> ] 
> Hari commented on AMQ-1746:
> ---------------------------
> saira, i think an exception would be thrown on the clientside when a
> disconnect happens, in which case you will have to manually reconnect to
> the server. 
>> ActiveMQ server does not release the connection on a reconnect
>> --------------------------------------------------------------
>>                 Key: AMQ-1746
>>                 URL:
>>             Project: ActiveMQ
>>          Issue Type: Bug
>>          Components: Connector
>>    Affects Versions: 5.2.0
>>         Environment: Redhat Linux , jdk 1.5_0_6
>>            Reporter: Hari
>>            Assignee: Rob Davies
>> I have tried this with activemq 5.0,5.1 and latest snapshot of activemq
>> as of 20080521. I am using apacha client. On a connect it
>> receives messages and on a regular shutdown the connection is
>> disconnected and everything shutsdown w.r.t that connection in the server
>> side. Now if there is network issue or when we disable and enable the
>> network from the client side , a reconnect request is sent with a new
>> clientid and the connection is established.But the old connection is
>> still active which is evident from a netstat on the server machine. The
>> client side netstat shows only the latest connection which is on port
>> 1870.
>> tcp        0      0 ::ffff:     ::ffff:    
>> tcp        0      0 ::ffff:     ::ffff:    
>> The server is 
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.

View this message in context:
Sent from the ActiveMQ - Dev mailing list archive at

View raw message