ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange TimeoutControl node performance issue

Post new topic  Reply to topic
 Strange TimeoutControl node performance issue « View previous topic :: View next topic » 
Author Message
SomeBloke
PostPosted: Thu Feb 05, 2009 8:06 am    Post subject: Strange TimeoutControl node performance issue Reply with quote

Newbie

Joined: 05 Feb 2009
Posts: 6
Hello all

I'm experiencing very poor performance from a TimeoutControl node. From the time the previous node passes in the message till the following node after the timeout control processes the message is >500ms. I believe I am passing the correct TimeoutRequest format because the TimeoutNotification does in fact work.

I'm setting InputLocalEnvironment.TimeoutRequest to:
Code:

<TimeoutRequest>
     <Action>SET</Action>
     <Identifier>test</Identifier>
     <StartTime>NOW</StartTime>
     <Interval>5</Interval>
     <Count>1</Count>
</TimeoutRequest>


The TimeoutNotification node with corresponding UniqueId is triggered after 5 seconds. I just don't understand why TimeoutControl takes 500ms to process this message, it can't possible take that long to write a local non-persistant message to a queue can it?

Am I failing to grasp something basic here? Hoping someone can shed some light.

P.S. Anything else relvant I can think of:
broker Timeout Q depth is currently 0
after i remove TimeoutControl node total time is reduced back to original <10ms
Back to top
View user's profile Send private message
AkankshA
PostPosted: Thu Feb 05, 2009 8:47 pm    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
I guess its waiting for 5 sec to propagate the first message initially.. i.e. taken from Interval value... i.e. broker takes it as send a message after every 5 seconds of the start time.... and hence its not sending the message at 0


If you want the message to be propagated initially(and only once) then give as below

<TimeoutRequest>
<Action>SET</Action>
<Identifier>test</Identifier>
<StartTime>NOW</StartTime>
</TimeoutRequest>

let me know if i overlooked something
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
SomeBloke
PostPosted: Fri Feb 06, 2009 7:45 am    Post subject: Reply with quote

Newbie

Joined: 05 Feb 2009
Posts: 6
AkankshA wrote:
I guess its waiting for 5 sec to propagate the first message initially.. i.e. taken from Interval value... i.e. broker takes it as send a message after every 5 seconds of the start time.... and hence its not sending the message at 0


If you want the message to be propagated initially(and only once) then give as below

<TimeoutRequest>
<Action>SET</Action>
<Identifier>test</Identifier>
<StartTime>NOW</StartTime>
</TimeoutRequest>

let me know if i overlooked something


I do not want the message propogated initially, maybe I didn't make myself clear.

Simple test flow I've made to illustrate the problem goes like this:
Flow1: HttpIn -> JavaComputNode(Create TimeoutRequest) -> TimeoutControl -> Trace -> HttpReply
Flow2: TimeoutNotification -> Trace

I would like the TimeoutControl node to start 5second timer, and immediatley continue onto the Trace and HttpReply nodes. It currently takes around 500ms to start said timer before passing control to the trace node. This makes no sense to me, how would this behavior be expected? The interval of 5 is specified in seconds not ms anyway, so it does not appear it is waiting the interval time either.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Strange TimeoutControl node performance issue
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.