]
Martin Weiler moved SOA-3397 to JBESB-3686:
-------------------------------------------
Project: JBoss ESB (was: JBoss Enterprise SOA Platform)
Key: JBESB-3686 (was: SOA-3397)
Affects Version/s: 4.10
4.9 CP1
(was: 5.1.0 GA)
Component/s: Rosetta
(was: JBossESB)
alertLengthThreshold does not work for http-gateway
---------------------------------------------------
Key: JBESB-3686
URL:
https://issues.jboss.org/browse/JBESB-3686
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Rosetta
Affects Versions: 4.10, 4.9 CP1
Reporter: Martin Weiler
We added 'alertTimeThreshold' and 'alertLengthThreshold' properties to a
service which only has a http-gateway listener. We see WARN messages if the time threshold
is surpassed, but none for the lenght threshold.
Diagnostics:
The problem with the alertLengthThreshold is that this only works if the message contains
a property 'Environment.MESSAGE_BYTE_SIZE', see the ActionStatusBean constructor:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_...
This property is set in either the Util.serialize(Message) or Util.deserialize() method:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/tags/JBESB_4_9_CP1_ER8_...
But while one of these methods is called when other gateways are used (eg. with JMS
through the org.jboss.internal.soa.esb.couriers.helpers.JmsComposer), this is apparently
not the case with http-gateway.
Todo:
Improve the algorithm in ActionStatusBean which calculates the message bytes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: