[ 
https://issues.apache.org/jira/browse/QPID-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002458#comment-16002458
 ] 

Kapila Arora edited comment on QPID-7767 at 5/9/17 10:49 AM:
-------------------------------------------------------------

Hi Rob, 
Now you can see the Stdout logging generated after setting  parameter 
PN_TRACE_FRM as true value . I am attaching the file for your reference as 
"apacheQpidJMS0.11.1_protocolLog_withDelivery34_DataMasking.log" 

With respect to Re-delivery , My understanding , we need to understand , Why 
this re-delivery is happening , either JMS Client is not able to read the 
message in first attempt  then only AMQP server is trying to re-deliver the 
message . I hope , that also require some clarity .

In our case , One Message/Data Packets can have maximum 256 KB Size and current 
messages of almost around 100 KB size.  

I will try to investigate on server side as well , Earlier with QPID 0.32 , 
there were also having lot many messages re-delivred as JMS Client was not able 
to read and complete and service bus re-delivering the message and after max 
delivery attempt , AMQP Server (Azure Service bus ) sending these messages on 
deadletterQueue. So I also need to enquire on there side if this also the case 
with JMS 0.11.1 as well.  






was (Author: kapilaarora):
Hi Rob, 
Now you can see the stdout logging generated after setting  parameter 
PN_TRACE_FRM as true value. 


> 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]

Reply via email to