Uploaded image for project: 'JBoss A-MQ'
  1. JBoss A-MQ
  2. ENTMQ-2201

[AMQ 6, MessagePull, timeout ] Pull request intermittently do not timeout as expected

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • JBoss A-MQ 6.3.x
    • JBoss A-MQ 6.3
    • broker
    • None
    • +
    • Hide

      It depends what is causing work for the scheduler.

      one configure change that might help is to turn off the periodic expiry tasks for queue and topics in the PolicyEntry , something like

      <policyEntry topic=">"   expireMessagesPeriod="0"  ... 
      ...
      <policyEntry queue=">"   expireMessagesPeriod="0"  ... 
      
      
      Show
      It depends what is causing work for the scheduler. one configure change that might help is to turn off the periodic expiry tasks for queue and topics in the PolicyEntry , something like <policyEntry topic= ">" expireMessagesPeriod= "0" ... ... <policyEntry queue= ">" expireMessagesPeriod= "0" ...
      • will try to add a test case when I have time later

    Description

      When using a prefetch=0 and javax.jms.MessageConsumer#receive(timeout), the user would expect the call to be timeout after the specified period.
      Periodically this scenario is not timing out and the receive call does not finish.

      Analysis:
      With prefetch=0 the client will use send a MessagePull command with the timeout associated. The broker will scheduler a NullMessage to be sent back to the client if no message has been dispatched before the timeout expires. It uses the brokers scheduler. If the scheduler is busy with other tasks (e.g expiry timeouts on queues, topics) these Pull request timeouts can remain in the queue for a significant time waiting to get fired. This can lead to receive(timeout) calls not timing out.

      Attachments

        Activity

          People

            gtully@redhat.com Gary Tully
            rhn-support-pfox Patrick Fox (Inactive)
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: