|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Elapse Time at call BITSTREAM parser |
« View previous topic :: View next topic » |
Author |
Message
|
servi |
Posted: Mon Dec 21, 2009 1:37 am Post subject: Elapse Time at call BITSTREAM parser |
|
|
 Novice
Joined: 19 Mar 2008 Posts: 22 Location: Madrid, España
|
Hi,
Since we have installed the FixPack 5 in our WebSphere Message Broker v6, a delay time apeears procesing lines with the BITSTREAM sentence.
Analyzing debug traces we can reproduce the problem on all our Message broker v6.1.0.5, but doesn´t appears on v6.1.0.2.
The next sentence takes on v6.1.0.5 more than 700 ms:
2009-12-17 17:16:31.020036 7792 UserTrace BIP2537I: Nodo 'BACKEND.EXTERNOS_MQIda.Subflujo MQ ida1.XML -> BLOB': Ejecutando la sentencia ''CREATE LASTCHILD OF OutputRoot DOMAIN 'BLOB' PARSE(BITSTREAM(OutputRoot.MRM), OutputRoot.MQMD.Encoding, OutputRoot.MQMD.CodedCharSetId);'' en ('BACKENDS.ComHost_XMLaBLOB.main', '33.4').
2009-12-17 17:16:31.722726 7792 UserTrace BIP5494I: El árbol lógico se está comparando en este momento con el modelo de mensaje.
While in the Broker v6.1.0.2 the execution was inmediantly (less than 1ms):
2009-12-17 17:32:49.770137 1068 UserTrace BIP2537I: Node 'BACKEND.EXTERNOS_MQIda.Subflujo MQ ida1.XML -> BLOB': Executing statement ''CREATE LASTCHILD OF OutputRoot DOMAIN 'BLOB' PARSE(BITSTREAM(OutputRoot.MRM), OutputRoot.MQMD.Encoding, OutputRoot.MQMD.CodedCharSetId);'' at ('BACKENDS.ComHost_XMLaBLOB.main', '33.4').
2009-12-17 17:32:49.770256 1068 UserTrace BIP5494I: The logical tree is now being matched to the message model.
We have change from the deprecated BITSTREAM to the ASBITSTREAM funcion, and the delay hasn't appear. ¿Anyone has detected this time delay?
Regards, |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|