activemq-dev mailing list archives

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


Saira Gul commented on AMQ-1746:

 I am using activeMQ supports for Ajax in my application. i've created queues like amq.sendMessage("queueName",
 and to receive a message i've added listener like amq.addListener(myId, myDestination, myHandler.revMessage);

 When i send request with amq.sendMessage("queueName", message); it will make JMS message,
fetch response and 
 send the message back to myHandler. this code works fine.. 

the problem is that if network connection lost, all handlers will also lost and the handlers
would not be able to get response back from JMS.. requests are getting fine to activeMQ server
and the response is also generating and MessageListenerServlet fail to send back response
to javascript...

Is there any way to activate handlers again when network connection got enabled after disabled.

Thank you

Quoted from:

> 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:     ESTABLISHED

> tcp        0      0 ::ffff:     ::ffff:     ESTABLISHED

> 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 raw message