[esb-issues] [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387269 ]
Tom Fennelly commented on JBESB-1201:
-------------------------------------
Possibly would explain both issues.
Why didn't they timeout... I guess because the message delay was on the first hop
(i.e. from splitter to RGB services), where there was no timeout check (because the RGB
services are not aggregating) .... the messages going from the RGB services to the
aggregator would have a brand new timestamps on them, so the timeout check on the
aggregator is against a wrong (but more recent) timestamp.
Anyway, I'm just in the process of putting together more concrete tests.
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
Reporter: Jaroslaw Kijanowski
Assigned To: Tom Fennelly
Fix For: 4.2.1 CP1
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