[esb-issues] [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly

Mon Oct 29 18:41:01 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12384960 ] 

Jaroslaw Kijanowski commented on JBESB-1201:
--------------------------------------------

Have you tried t run the whole QS which I've attached?
DEBUG level is enabled for the aggregator. You should see followig info when a (IMO timedout) messages arrives at the aggregator:

     [java] 23:31:20,298 DEBUG [pool-1-thread-1][Aggregator] Current time=11:31:20 PM message expiration=11:31:25 PM
     [java] 23:31:20,298 DEBUG [pool-1-thread-1][Aggregator] message is alive.

This shouldn't be true, because the splitter has processed the message over 60 seconds ago (by 6000 milis set for aggregator's timeout), here's the last DEBUG message from the splitter:

23:30:13,719 DEBUG [pool-1-thread-1][DefaultJMSPropertiesSetter] Setting outgoing JMSProperty, key : aggregatorTag, value : [21c85506-15f2-4dbc-bdbc-f5301f13c36d:1:3:1193697012382, 21c85506-15f2-4dbc-bdbc-f5301f13c36d:2:3:1193697012382, 21c85506-15f2-4dbc-bdbc-f5301f13c36d:3:3:1193697012382]

> Aggregator's timeout doesn't work properly
> ------------------------------------------
>
>                 Key: JBESB-1201
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1201
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Content Based Routing
>    Affects Versions: 4.2.1 IR2
>            Reporter: Jaroslaw Kijanowski
>         Assigned To: Kurt Stam
>             Fix For: 4.2.1
>
>         Attachments: aggregator.esb.zip, aggregator.tar
>
>
> I've modified the aggregator QS: set the aggregator's timeout to 6 seconds and delayed the delivery of messages to the aggregator for 65 seconds (see attached QS). All messages didn't expire:
>      [java] 14:01:31,406 DEBUG [pool-1-thread-1][Aggregator] Current time=2:01:31 PM message expiration=2:01:31 PM
>      [java] 14:01:31,407 DEBUG [pool-1-thread-1][Aggregator] message is alive.
> You can find the whole aggreator log in listener.log inside the QS.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira