RE: proton-j messenger connection issues

Thanks. Our use case is Android app, so we can't provision queues beforehand. Probably we need consider using proton-C via JNI from Java or look at other ways. Regards, Yanfeng -Original Message- From: Julien Charon [mailto:julien.cha...@avitech.aero] Sent: Friday, July 24, 2015 2

AW: proton-j messenger connection issues

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 G

Re: 0.10 beta1

And I spoke too soon... https://issues.apache.org/jira/browse/PROTON-958 - blocker. Actually found this under 0.9.1, but definitely a problem for 0.10 that will result in subtle hard to debug failures of the python install. Got a proposed fix that I think is actually a better approach to the pr

[jira] [Commented] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so

[ https://issues.apache.org/jira/browse/PROTON-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639440#comment-14639440 ] Ken Giusti commented on PROTON-958: --- Reviewboard link: https://reviews.apache.org/r/367

[jira] [Created] (PROTON-958) [python] pip installed binding fails to find correct libqpid-proton.so

Ken Giusti created PROTON-958: - Summary: [python] pip installed binding fails to find correct libqpid-proton.so Key: PROTON-958 URL: https://issues.apache.org/jira/browse/PROTON-958 Project: Qpid Proton

Problem with Proton-j 0.9.1

Hi all, We have a broker that uses proton-j 0.9.1 and we execute a test that does a NULL lookup caused by the JMSSession.unsubscribe(name) call. The test passes when using the QPID Proton JMS 0.3.0 but fails when run used the QPID legacy JMS 0.32 with the following error: javax.jms.JMSExceptio

potential proton-c issue with receiving multi-frame messsages

Hi folks, I wanted to draw attention of some proton-c literate folks to look at https://issues.apache.org/jira/browse/QPID-6651 as so far the issue looks like it could be on the proton-c side. This was raised during a discussion on the qpid-users list: http://mail-archives.apache.org/mod_mbox/qpi

[jira] [Commented] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638834#comment-14638834 ] Robbie Gemmell commented on PROTON-954: --- Missing comments issue raised as INFRA-1003

[jira] [Commented] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638809#comment-14638809 ] Robbie Gemmell commented on PROTON-954: --- Not sure why but the bot missed 4 other com

[jira] [Resolved] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-954. --- Resolution: Fixed > miscelaneous cleanup > > > Key: PROTO

[jira] [Commented] (PROTON-955) [proton-j] only the payload for the current frame, and not the entire remainder for the delivery, should be handed to the trace logging / frame tracer

[ https://issues.apache.org/jira/browse/PROTON-955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638718#comment-14638718 ] Robbie Gemmell commented on PROTON-955: --- Not sure why the bot hasnt commented, but t

[jira] [Resolved] (PROTON-955) [proton-j] only the payload for the current frame, and not the entire remainder for the delivery, should be handed to the trace logging / frame tracer

[ https://issues.apache.org/jira/browse/PROTON-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-955. --- Resolution: Fixed > [proton-j] only the payload for the current frame, and not the entire > r

[jira] [Resolved] (PROTON-957) [proton-j] make trace logging of transfer frames more useful

[ https://issues.apache.org/jira/browse/PROTON-957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-957. --- Resolution: Fixed > [proton-j] make trace logging of transfer frames more useful > ---

[jira] [Resolved] (PROTON-956) [proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer

[ https://issues.apache.org/jira/browse/PROTON-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-956. --- Resolution: Fixed > [proton-j] avoid some overhead when sending frames if the trace logging is

[jira] [Commented] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638710#comment-14638710 ] ASF subversion and git services commented on PROTON-954: Commit 47

[jira] [Commented] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638708#comment-14638708 ] ASF subversion and git services commented on PROTON-954: Commit ff

[jira] [Commented] (PROTON-956) [proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer

[ https://issues.apache.org/jira/browse/PROTON-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638707#comment-14638707 ] ASF subversion and git services commented on PROTON-956: Commit 13

[jira] [Commented] (PROTON-957) [proton-j] make trace logging of transfer frames more useful

[ https://issues.apache.org/jira/browse/PROTON-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638709#comment-14638709 ] ASF subversion and git services commented on PROTON-957: Commit de

[jira] [Commented] (PROTON-954) miscelaneous cleanup

[ https://issues.apache.org/jira/browse/PROTON-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638711#comment-14638711 ] ASF subversion and git services commented on PROTON-954: Commit d3

[jira] [Updated] (PROTON-955) [proton-j] only the payload for the current frame, and not the entire remainder for the delivery, should be handed to the trace logging / frame tracer

[ https://issues.apache.org/jira/browse/PROTON-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-955: -- Description: Only the payload for the current frame, and not the entire remainder for the delive

[jira] [Updated] (PROTON-955) [proton-j] only the payload for the current frame, and not the entire remainder for the delivery, should be handed to the trace logging / frame tracer

[ https://issues.apache.org/jira/browse/PROTON-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-955: -- Summary: [proton-j] only the payload for the current frame, and not the entire remainder for the

[jira] [Created] (PROTON-957) [proton-j] make trace logging of transfer frames more useful

Robbie Gemmell created PROTON-957: - Summary: [proton-j] make trace logging of transfer frames more useful Key: PROTON-957 URL: https://issues.apache.org/jira/browse/PROTON-957 Project: Qpid Proton

[jira] [Created] (PROTON-956) [proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer

Robbie Gemmell created PROTON-956: - Summary: [proton-j] avoid some overhead when sending frames if the trace logging isnt enabled and there is no frame tracer Key: PROTON-956 URL: https://issues.apache.org/jira/br

[jira] [Created] (PROTON-955) [proton-j] only the payload for the current frame, and not the entire delivery, should be handed to the trace logging / frame tracer

Robbie Gemmell created PROTON-955: - Summary: [proton-j] only the payload for the current frame, and not the entire delivery, should be handed to the trace logging / frame tracer Key: PROTON-955 URL: https://issues

[jira] [Created] (PROTON-954) miscelaneous cleanup

Robbie Gemmell created PROTON-954: - Summary: miscelaneous cleanup Key: PROTON-954 URL: https://issues.apache.org/jira/browse/PROTON-954 Project: Qpid Proton Issue Type: Bug Componen

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]

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: