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

Timothy Bish commented on QPIDJMS-409:
--------------------------------------

There isn't quite enough to go on in the logs provided, could you ensure that 
the ENV var PN_TRACE_FRM is set to "true".  Also a reproducer will go a lot 
further in finding out what is going on as otherwise we are just guessing. 

> JMS Scheduled Delivery delivers messages before time under load
> ---------------------------------------------------------------
>
>                 Key: QPIDJMS-409
>                 URL: https://issues.apache.org/jira/browse/QPIDJMS-409
>             Project: Qpid JMS
>          Issue Type: Bug
>          Components: qpid-jms-client
>    Affects Versions: 0.35.0
>         Environment: Application is a Spring Boot application - version 
> 2.0.4.RELEASE
> Qpid JMS Client version is 0.35.0
> Operating system where problem occurs is Windows 10
> I have found this problem using the following different message brokers:
>  * Apache Artemis 2.4.0
>  * Apache Artemis 2.6.2
>  * Apache Qpid Broker 7.0.6
>            Reporter: Ian Rowlands
>            Priority: Major
>         Attachments: successful_delayed_delivery.txt
>
>
> When under system load, the Qpid JMS client doesn't handle scheduled message 
> delivery correct - it delivers the message prior to the required time.
> When running one request, the scheduling works correctly. The load to 
> reproduce this isn't very high (i.e running about 5 of my job processes 
> simultaneously seems to trip it up pretty quickly).
> I have used different JMS Brokers with the same client code and the same 
> problem occurs with both Brokers (see environment).
> I am using Spring JMS Template to send the JMS message. The key piece of code 
> is something like:
> {{delayedDeliveryjmsTemplate.setDeliveryDelay(timeoutPeriod);}}
> {{delayedDeliveryjmsTemplate.convertAndSend(queueName, timeoutMsg, (Message 
> jmsMessage) -> {}}
> {{ jmsMessage.setStringProperty(OBJECT_TYPE_FIELD, 
> timeoutMsg.getClass().getSimpleName());}}
> {{jmsMessage.setStringProperty(OBJECT_TYPE_FIELD, 
> timeoutMsg.getClass().getSimpleName());}}
> {{ return jmsMessage;}}
> {{});}}
> I realise you want more logging details but I'm unsure what would be best to 
> log. Please let me know and I'll do so.
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to