7:10 a.m.
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: Mark Little
Attachments: 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
7:10 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Jaroslaw Kijanowski updated JBESB-1201:
---------------------------------------
Attachment: aggregator.tar
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: Mark Little
Attachments: 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
7:14 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Jaroslaw Kijanowski updated JBESB-1201:
---------------------------------------
Attachment: (was: aggregator.tar)
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: Mark Little
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
7:16 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Jaroslaw Kijanowski updated JBESB-1201:
---------------------------------------
Attachment: aggregator.tar
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: Mark Little
Attachments: 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
11:21 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Mark Little updated JBESB-1201:
-------------------------------
Fix Version/s: 4.2.1
Assignee: Kurt Stam (was: Mark Little)
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.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
2:42 p.m.
New subject: [JBoss JIRA] Work started: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Work on JBESB-1201 started by Kurt Stam.
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.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
9:38 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Kurt Stam updated JBESB-1201:
-----------------------------
Attachment: aggregator.esb.zip
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
10:07 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1201) Aggregator's timeout doesn't work properly
[ 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
5:41 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12384960 ]
Jaroslaw Kijanowski commented on JBESB-1201:
--------------------------------------------
Have you tried t run the whole QS which I've attached?
DEBUG level is enabled for the aggregator. You should see followig info when a (IMO
timedout) messages arrives at the aggregator:
[java] 23:31:20,298 DEBUG [pool-1-thread-1][Aggregator] Current time=11:31:20 PM
message expiration=11:31:25 PM
[java] 23:31:20,298 DEBUG [pool-1-thread-1][Aggregator] message is alive.
This shouldn't be true, because the splitter has processed the message over 60 seconds
ago (by 6000 milis set for aggregator's timeout), here's the last DEBUG message
from the splitter:
23:30:13,719 DEBUG [pool-1-thread-1][DefaultJMSPropertiesSetter] Setting outgoing
JMSProperty, key : aggregatorTag, value :
[21c85506-15f2-4dbc-bdbc-f5301f13c36d:1:3:1193697012382,
21c85506-15f2-4dbc-bdbc-f5301f13c36d:2:3:1193697012382,
21c85506-15f2-4dbc-bdbc-f5301f13c36d:3:3:1193697012382]
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
4:51 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Jaroslaw Kijanowski reopened JBESB-1201:
----------------------------------------
Hi Kurt,
I'm reopening this since I still can reporoduce it with my attached QS. Can you
confirm that?
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
6:01 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Kevin Conner updated JBESB-1201:
--------------------------------
Fix Version/s: 4.3
(was: 4.2.1)
Will be covered in CP
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.3
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
4:17 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Mark Little updated JBESB-1201:
-------------------------------
Fix Version/s: 4.2.1 CP1
(was: 4.3)
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: Kurt Stam
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
10:43 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Tom Fennelly reassigned JBESB-1201:
-----------------------------------
Assignee: Tom Fennelly (was: Kurt Stam)
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
6:27 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387038 ]
Tom Fennelly commented on JBESB-1201:
-------------------------------------
I tried the QS attached by Jaroslaw and I think it's working. Here's the log I
get...
[java] 12:10:52,060 DEBUG [Thread-3][JmsConnectionPool] Returning session,
poolsize=1, maxsize=20, number of pools=1
[java] 12:10:52,060 DEBUG [Thread-3][SpyDestinationObjectFactory]
SpyDestinationObjectFactory->getObjectInstance()
[java] 12:15:56,138 DEBUG [pool-1-thread-1][ActionProcessingPipeline] pipeline
process for message: header: [ To: JMSEpr [ PortReference < <wsa:Address
jms://localhost
[java] 12:15:56,310 DEBUG [pool-1-thread-1][ActionProcessingPipeline] executing
processor 0 org.jboss.soa.esb.actions.Aggregator@ca3783 header: [ To: JMSEpr [ PortRefe
[java] 12:15:56,310 DEBUG [pool-1-thread-1][Aggregator] Current time=12:15:56 message
expiration=12:15:39
[java] 12:15:56,310 DEBUG [pool-1-thread-1][Aggregator] message expired.
[java] 12:15:56,310 DEBUG [pool-1-thread-1][Aggregator] Ignoring this message since
we are already timedout on this message.
[java] 12:15:56,576 DEBUG [pool-1-thread-1][ActionProcessingPipeline] pipeline
process for message: header: [ To: JMSEpr [ PortReference < <wsa:Address
jms://localhost
[java] 12:15:56,576 DEBUG [pool-1-thread-1][ActionProcessingPipeline] executing
processor 0 org.jboss.soa.esb.actions.Aggregator@ca3783 header: [ To: JMSEpr [ PortRefe
[java] 12:15:56,576 DEBUG [pool-1-thread-1][Aggregator] Current time=12:15:56 message
expiration=12:15:39
[java] 12:15:56,576 DEBUG [pool-1-thread-1][Aggregator] message expired.
[java] 12:15:56,576 DEBUG [pool-1-thread-1][Aggregator] Ignoring this message since
we are already timedout on this message.
[java] 12:15:56,591 DEBUG [pool-1-thread-1][ActionProcessingPipeline] pipeline
process for message: header: [ To: JMSEpr [ PortReference < <wsa:Address
jms://localhost
[java] 12:15:56,591 DEBUG [pool-1-thread-1][ActionProcessingPipeline] executing
processor 0 org.jboss.soa.esb.actions.Aggregator@ca3783 header: [ To: JMSEpr [ PortRefe
[java] 12:15:56,591 DEBUG [pool-1-thread-1][Aggregator] Current time=12:15:56 message
expiration=12:15:39
[java] 12:15:56,591 DEBUG [pool-1-thread-1][Aggregator] message expired.
[java] 12:15:56,591 DEBUG [pool-1-thread-1][Aggregator] Ignoring this message since
we are already timedout on this 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
7:08 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387045 ]
Jaroslaw Kijanowski commented on JBESB-1201:
--------------------------------------------
You've tried aggregator.tar and not aggregator.esb.zip, right? This is exactly the
output I would expect, but I still can reproduce this issue (message is alive).
Let me try another box...
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
7:14 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387050 ]
Tom Fennelly commented on JBESB-1201:
-------------------------------------
Right Jaroslaw, I used the 280kb tar.
By any chance, do you have the different services running on different machines?
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
4:48 a.m.
New subject: [JBoss JIRA] Work started: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Work on JBESB-1201 started by Tom Fennelly.
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
4:48 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387224 ]
Tom Fennelly commented on JBESB-1201:
-------------------------------------
Sorry, forgot to mark this as started - writing tests around this, JBESB-746 and
JBESB-1204
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
6:34 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ 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
6:44 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=comments#action_12387248 ]
Jaroslaw Kijanowski commented on JBESB-1201:
--------------------------------------------
Wouldn't this explain both issues, 1201 and 1204?
1201 - messages don't get timed out (timestamp overwritten)
1204 - messages aren't collected (aggregation info overritten)
If yes, why did your messages timed out?
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
8:18 a.m.
New subject: [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
4:52 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-1201) Aggregator's timeout doesn't work properly
[ http://jira.jboss.com/jira/browse/JBESB-1201?page=all ]
Tom Fennelly closed JBESB-1201.
-------------------------------
Resolution: Done
done
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
6210
days inactive
6245
days old
21 comments
5 participants
participants (5)
-
Jaroslaw Kijanowski (JIRA) -
Kevin Conner (JIRA)
-
Kurt Stam (JIRA)
-
Mark Little (JIRA)
-
Tom Fennelly (JIRA)