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

[Kurt Stam (JIRA)]

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

Kurt Stam closed JBESB-1201.
----------------------------

    Resolution: Done

I deployed the aggregator part into jbossesb (see aggregator.esb.zip attachment), so I could easily hook up the debugger, and I can't reproduce the issue reported. I've also added a unittest to make sure the timeout works properly. 

While doing this is did run into a problem with deserializing attachments (JBESB-1252)

I'm rejecting this, but please retest and reopen if it is reproducible.

--Kurt

> 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