[
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002428#comment-16002428
]
Robbie Gemmell commented on QPID-7767:
--------------------------------------
That initial logging you posted is from the client itself, and not what I was
discussing, however it does show you are getting connected. The PN_TRACE_FRM
logging comes from Proton, and looks quite different from the rest of the
logging from the client itself.
As noted in the docs, it goes to stdout and you need to set PN_TRACE_FRM as an
environment variable, not a Java system property. For example, here is a small
section of the PN_TRACE_FRM output while running the clients HelloWorld
example. The snippet shows protocol trace logging of the client sending a
message, the broker accepting it, the consumer receiving the message back, and
then accepting it:
{noformat}
[qpid-jms-examples]$ PN_TRACE_FRM=true java -cp
"target/classes/:target/dependency/*" org.apache.qpid.jms.example.HelloWorld
...
[766939720:1] -> Transfer{handle=0, deliveryId=0, deliveryTag=0,
messageFormat=0, settled=null, more=false, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (149)
"\x00Sr\xc1)\x04\xa3\x0ex-opt-jms-destQ\x00\xa3\x12x-opt-jms-msg-typeQ\x05\x00Ss\xc0Q\x0a\xa1/ID:8baa0be0-0e16-44ca-8e65-79f3abbded3e:1:1:1-1@\xa1\x0dqueue://queue@@@@@@\x83\x00\x00\x01[\xec\x95\x0c\xbb\x00Sw\xa1\x0cHello
world!"
[766939720:1] <- Disposition{role=RECEIVER, first=0, last=0, settled=true,
state=Accepted{}, batchable=false}
[766939720:1] <- Transfer{handle=1, deliveryId=0, deliveryTag=0,
messageFormat=0, settled=null, more=false, rcvSettleMode=null, state=null,
resume=false, aborted=false, batchable=false} (149)
"\x00Sr\xc1)\x04\xa3\x0ex-opt-jms-destQ\x00\xa3\x12x-opt-jms-msg-typeQ\x05\x00Ss\xc0Q\x0a\xa1/ID:8baa0be0-0e16-44ca-8e65-79f3abbded3e:1:1:1-1@\xa1\x0dqueue://queue@@@@@@\x83\x00\x00\x01[\xec\x95\x0c\xbb\x00Sw\xa1\x0cHello
world!"
[766939720:1] -> Disposition{role=RECEIVER, first=0, last=0, settled=true,
state=Accepted{}, batchable=false}
...
{noformat}
If you can't use PN_TRACE_FRM, you can try the second route documented to
configure the client+logging framework to direct similar output to the clients
log output.
That the messages are marked redelivered and have a JMSXDeliveryCount of up to
10 just means the AMQP message received from the server had a delivery-count >0
with value of up to 9 (its 0-based, JMSXDeliveryCount is 1-based), which isn't
necessarily surprising here and has no specific interest to the client itself
beyond reporting the value (unless specifically configured with the redelivery
policy bits), which is what it should do.
There remains little I can suggest with the minimal information available here.
Perhaps some protocol trace logging will show something, but I've yet to see
anything suggesting an issue with the client.
> Unknown endpoint Transfer issue on AMQP Connection
> --------------------------------------------------
>
> Key: QPID-7767
> URL: https://issues.apache.org/jira/browse/QPID-7767
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.32
> Environment: AMQP Client - Qpid 0.32 runs on Java run time 1.7 on
> Linux box on softLayer
> AMQP Server - Azure Service bus on Public cloud
> Reporter: Kapila Arora
> Priority: Critical
> Fix For: 0.32
>
> Attachments: Qpid_error_log.txt
>
>
> Getting Errors in the AMQP Client
> 2017-05-03 06:45:15.048 212 Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> Data Packets
> Unknown endpoint
> Transfer{handle=0,deliveryId=2,deliveryTag=\xf3\x99\x90\x5cL\xb1\xdeF\x9da\xa3o\xb0\x5cdm,messageFormat=0,more=true,batchable=true}
> 2017-05-03 06:45:15.396 212 Unknown endpoint Transfer{handle=0,more=false}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
