[ http://jira.jboss.com/jira/browse/JBESB-1204?page=all ] Mark Little updated JBESB-1204: ------------------------------- Fix Version/s: 4.2.1 -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=comments#action_12384954 ] Jaroslaw Kijanowski commented on JBESB-1204: -------------------------------------------- Right, but please have a look at the aggregator QS. Shouldn't the aggregator wait until *all* 3 messages arrive and then create one big message and pass it to the next action item? It looks like the aggregator sends 3 different messages. You can easily reproduce it by delaying the red, blue or green service. You will notice that the print-after method is called at least two times. -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=all ] Mark Little updated JBESB-1204: ------------------------------- Fix Version/s: 4.2.1 CP (was: 4.2.1) Since 4.2.1 has been released, moving this to CP1. -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=comments#action_12386204 ] Jaroslaw Kijanowski commented on JBESB-1204: -------------------------------------------- JBESB-1201 is about timeout, which IMO, doesn't work well, a message which should timed out is printed as "alive". The issue here is that the aggregator creates a seperate message for every message it gets. I think the aggregator should wait for *all* messages, which belong together and then, after all have arrived, create one big message. To see this, just delay one service (= delay delivery of message to the aggregator) and you will notice that the aggregator will send several messages to the next action item. But it shouldn't right? The splitter has sent out 3 messages (hence those messages belong together) to 3 services and the aggregator should wait for all 3 messages untl it creates an aggregated message, am I right? -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=all ] Tom Fennelly reassigned JBESB-1204: ----------------------------------- Assignee: Tom Fennelly (was: Kurt Stam) -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=all ] Work on JBESB-1204 started by Tom Fennelly. -- 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

[ http://jira.jboss.com/jira/browse/JBESB-1204?page=all ] Tom Fennelly closed JBESB-1204. ------------------------------- Resolution: Done done -- 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