[esb-issues] [JBoss JIRA] Commented: (JBESB-1361) IllegalArgumentException in aggregator QS

[Tom Fennelly (JIRA)]

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

Good stuff :-)

In general, the aggregator needs to be followed by an action that pieces the aggregated messages back together in some meaningful way, before sending it on.  The aggregator quickstart has a comment in the config around the SystemPrintln action re adding such an action.  Maybe we should actually do that rather than leaving it to the user.

In general, I think that aggregator quickstart is a bit too complex and could benefit from a flow diagram of some sort.

> IllegalArgumentException in aggregator QS
> -----------------------------------------
>
>                 Key: JBESB-1361
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1361
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Examples
>    Affects Versions: 4.2.1 CP1
>            Reporter: Jaroslaw Kijanowski
>         Assigned To: Tom Fennelly
>
> Just try to run the aggregator QS, enable DEBUG level for the aggreagtion service, send a message and watch the aggregator's console:
>      [java] java.lang.IllegalArgumentException: value must be Serializable
>      [java]     at org.jboss.internal.soa.esb.message.format.xml.AttachmentImpl.addItem(AttachmentImpl.java:101)
>      [java]     at org.jboss.soa.esb.actions.Aggregator.createAggregateMessage(Aggregator.java:236)
>      [java]     at org.jboss.soa.esb.actions.Aggregator.process(Aggregator.java:185)
>      [java]     at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316)
>      [java]     at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303)
>      [java]     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
>      [java]     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
>      [java]     at java.lang.Thread.run(Thread.java:595)
> .
> .
> .
>      [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] message is alive.
>      [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] Current time=12:07:17 PM message expiration=12:07:18 PM
>      [java] 12:07:17,808 DEBUG [Thread-1][Aggregator] message is alive.
>      [java] 12:07:18,309 DEBUG [Thread-1][Aggregator] Current time=12:07:18 PM message expiration=12:07:18 PM
>      [java] 12:07:18,309 DEBUG [Thread-1][Aggregator] message expired.
>      [java] Exception in thread "Thread-1" java.lang.NullPointerException
>      [java]     at org.jboss.soa.esb.actions.Aggregator$TimeoutChecker.run(Aggregator.java:297)

-- 
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