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

Tom Fennelly (JIRA) jira-events at lists.jboss.org
Tue Nov 13 07:34:44 EST 2007


    [ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387246 ] 
            
Tom Fennelly commented on JBESB-1201:
-------------------------------------

I think I can see what's happening here.

This quickstart does the following...

1. Routes a message to 3 different services (red, green and blue).  It uses the StaticRouter.
2. Each of the services (red, green and blue) route the message to the aggregator services.  The use the StaticRouter again.
3. The Aggregator puts the 3 message back together again based on UUID + timestamp info

I think the problem is with how this info is getting added.  The static router uses the MessageMulticaster class to route the message to multiple destinations.  This is the class that sets the UUID + timestamp info.  I think (fairly sure) the problem arises at step #2 above... the StaticRouter is used again, which uses the MessageMulticaster class, which clobbers the aggregation info added to the message at step #1.

So basically, the MessageMulticaster class should be checking the message and only adding the aggregation info if it's not already set on the message.

> 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

        



More information about the esb-issues mailing list