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 » Timeout Time cannot be in the past

Post new topic  Reply to topic
 Timeout Time cannot be in the past « View previous topic :: View next topic » 
Author Message
Sourya
PostPosted: Thu Jan 29, 2015 3:01 am    Post subject: Timeout Time cannot be in the past Reply with quote

Newbie

Joined: 29 Jan 2015
Posts: 5

Hello,

In a message flow there are two Timeout Notification nodes.
One is Automatic and the other is in Controlled mode.

The Automatic one is set to run every 60 secs. The Controlled one is set to run "NOW" with count = 1 and interval = 1.

Below is the Timeout message for the controlled node.

Action = SET;
Identifier = XXX;
StartDate = TODAY;
StartTime = NOW;
Interval = 1;
Count = 1;
IgnoreMissed = TRUE;
AllowOverwrite = TRUE;

The message flow works perfectly for 5 mins. After that it throws the error "Timeout Time cannot be in the past".

Strangely the StartTime is always taking the value of the time at deployment time and hence after 5 mins (which I guess is internal to the broker), it throws the error "Timeout Time cannot be in the past".

Can you please help me with a solution such that this error does not occur.
Back to top
View user's profile Send private message
nelson
PostPosted: Thu Jan 29, 2015 6:28 am    Post subject: Reply with quote

Partisan

Joined: 02 Oct 2012
Posts: 313

Hi Sourya,

From the Knowledge Center:

Quote:
"The start time can be calculated by adding an interval to the current time. If a delay occurs between the node that calculates the start time and the TimeoutControl node, the start time in the message will have passed by the time it reaches the TimeoutControl node. If the start time is more than approximately five minutes in the past, a warning is issued and the TimeoutControl node rejects the timeout request. If the start time is less than five minutes in the past, the node processes the request as if it were immediate. Therefore, ensure that the start time in the timeout request message is now or a time in the future."


You should check that delay..
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 » Timeout Time cannot be in the past
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.