Hi Yanfeng,
I'm sorry, but we don't use temporary queues, I'm afraid I can't help you on this. Best regards, Julien Avitech GmbH Engineering AxL Tel.: +49 (0)7541/282-177 Fax: +49 (0)7541/282-199 e-mail: julien.cha...@avitech.aero ________________________________________________ Avitech GmbH Principal Office: Bahnhofplatz 1 | 88045 Friedrichshafen | Germany Court Registration: Amtsgericht Ulm | HRB 728293 Geschäftsführer/Managing Director: Antonio Maria Gonzalez Gorostiza http://avitech.aero This message may contain confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. -----Ursprüngliche Nachricht----- Von: Yanfeng Liu [mailto:yanfeng....@ygomi.com] Gesendet: Donnerstag, 23. Juli 2015 12:28 An: proton@qpid.apache.org Betreff: RE: proton-j messenger connection issues Julien, Sorry to hear your story with proton-J. Can I ask you happened to know how to get the name of a temporary queue created by proton-J program? See https://issues.apache.org/jira/browse/PROTON-938 for more details. Regards, Yanfeng From: Julien Charon [mailto:julien.cha...@avitech.aero] Sent: Thursday, July 23, 2015 4:58 PM To: proton@qpid.apache.org Subject: proton-j messenger connection issues Hi everybody, We are using proton-j Messenger to build clients that subscribe to an AMQP broker to get messages from a queue. It all works fine, we are getting messages and are able to process them. However, we observe 2 behaviours concerning connections when the clients run for a long time: 1. After a couple of hours, it seems that the broker resets the connection (see attached proton_conn_reset.log). After that, the client never gets messages again and seems to hang in the Messenger.recv() method. Is there a possibility to recover the messenger after connection resets, i.e. try to reconnect? 2. When the connection gets lost, the messenger crashes (see attached proton_conn_lost.log) with an IllegalArgumentException. Again, is there a possibility to recover from that, i.e. trigger the client to try to reconnect a certain number of times until the connection is available again? At the moment, the only possibility we see is to create a new messenger that tries to connect to the broker again. But this would require to get notified that the connection was reset, which is not the case because the IOException caused by the connection reset is swallowed somewhere and the caller to recv() is not aware of the fact that something went wrong. Best regards, Julien Avitech GmbH Engineering AxL Tel.: +49 (0)7541/282-177 Fax: +49 (0)7541/282-199 e-mail: julien.cha...@avitech.aero<mailto:julien.cha...@avitech.aero> ________________________________________________ Avitech GmbH Principal Office: Bahnhofplatz 1 | 88045 Friedrichshafen | Germany Court Registration: Amtsgericht Ulm | HRB 728293 Geschäftsführer/Managing Director: Antonio Maria Gonzalez Gorostiza http://avitech.aero<http://avitech.aero/> This message may contain confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.