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 Notification Controlled Mode - doesnt generate notif

Post new topic  Reply to topic Goto page 1, 2  Next
 Timeout Notification Controlled Mode - doesnt generate notif « View previous topic :: View next topic » 
Author Message
leopucci
PostPosted: Tue Dec 26, 2017 3:32 am    Post subject: Timeout Notification Controlled Mode - doesnt generate notif Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
Dears,

For some reason i am struggling with the combination of Timeout Control + Timeout Notification.

I am being able to set and cancel, using timeout control. (i have tested with wrong id´s to make sure about it).

So now i can set and cancel the timeout notification id´s, but after 30s, the timeout notification was supposed to generate a notification on the flow. That does not happen!

Anybody knows why? here is my code:

To generate the event:
Code:

DECLARE JUMP INTERVAL;
      DECLARE START TIME;
      SET JUMP = INTERVAL '60' SECOND;
      SET START = CURRENT_TIME + JUMP;
      SET OutputLocalEnvironment.TimeoutRequest.Action='SET';
      SET OutputLocalEnvironment.TimeoutRequest.Identifier= 'IDENTIFIER'
      SET OutputLocalEnvironment.TimeoutRequest.StartDate = 'TODAY';
      SET OutputLocalEnvironment.TimeoutRequest.StartTime=START;
      SET OutputLocalEnvironment.TimeoutRequest.IgnoreMissed = FALSE;
      SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = TRUE;
      SET OutputLocalEnvironment.TimeoutRequest.Count = 1;      
      


To cancel the event:
Code:

SET OutputLocalEnvironment.TimeoutRequest.Action = 'CANCEL';
SET OutputLocalEnvironment.TimeoutRequest.Identifier= 'IDENTIFIER'



Do i have to enable some initial configuration on the IIB before using controlled timer?
I already have a timer working, but in automatic mode, not controlled. The problem happens to the Controlled only.


Any clue?

Thanks!
Pucci
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Dec 26, 2017 5:26 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
I believe you should be using something like CURRENT_GMTTIMESTAMP instead of CURRENT_TIME...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
leopucci
PostPosted: Tue Dec 26, 2017 7:13 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
fjb_saper wrote:
I believe you should be using something like CURRENT_GMTTIMESTAMP instead of CURRENT_TIME...


Hi Saper, thanks for your help.

It does not seems to be the case.

Even using gmttimestamp it did not worked.

Code:

   Identifier:CHARACTER:IDENTIFIER
   StartDate:CHARACTER:TODAY
   StartTime:TIME:java.util.GregorianCalendar[time=-62167420083582,areFieldsSet=false,areAllFieldsSet=false,lenient=true,
zone=sun.util.calendar.ZoneInfo[id="America/Sao_Paulo",offset=-10800000,dstSavings=3600000,useDaylight=true,transitions=129,
lastRule=java.util.SimpleTimeZone[id=America/Sao_Paulo,offset=-10800000,dstSavings=3600000,useDaylight=true,
startYear=0,startMode=3,startMonth=9,startDay=15,startDayOfWeek=1,startTime=0,startTimeMode=0,endMode=3,endMonth=1,
endDay=15,endDayOfWeek=1,endTime=0,endTimeMode=0]],
firstDayOfWeek=1,minimalDaysInFirstWeek=1,ERA=0,YEAR=2,MONTH=11,WEEK_OF_YEAR=?,WEEK_OF_MONTH=?,
DAY_OF_MONTH=31,DAY_OF_YEAR=?,DAY_OF_WEEK=?,DAY_OF_WEEK_IN_MONTH=?,AM_PM=1,HOUR=1,HOUR_OF_DAY=13,
MINUTE=11,SECOND=56,MILLISECOND=418,ZONE_OFFSET=?,DST_OFFSET=?]
   IgnoreMissed:BOOLEAN:false
   AllowOverwrite:BOOLEAN:true
   Count:INTEGER:1



Any other hint?

Thanks pucci
Back to top
View user's profile Send private message
rekarm01
PostPosted: Tue Dec 26, 2017 12:14 pm    Post subject: Re: Timeout Notification Controlled Mode - doesnt generate n Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415
leopucci wrote:
Code:
-- ...
DECLARE START TIME;
-- ...
SET OutputLocalEnvironment.TimeoutRequest.StartTime=START;
-- ...


StartTime needs a CHARACTER string, not a TIME value.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Dec 26, 2017 1:18 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
So your start-date is a char field but your time field is a GregorianCalendar?

What is wrong with this picture? It should be an MbTime field at best and is probably another character field...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
leopucci
PostPosted: Tue Dec 26, 2017 1:46 pm    Post subject: Re: Timeout Notification Controlled Mode - doesnt generate n Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
rekarm01 wrote:
leopucci wrote:
Code:
-- ...
DECLARE START TIME;
-- ...
SET OutputLocalEnvironment.TimeoutRequest.StartTime=START;
-- ...


StartTime needs a CHARACTER string, not a TIME value.


Thanks for your suggestion rekarm01, but even casting the field to this character, it did not worked
Code:

   Action:CHARACTER:SET
   Identifier:CHARACTER:IDENTIFIER
   StartDate:CHARACTER:TODAY
   StartTime:CHARACTER:19:46:46
   IgnoreMissed:BOOLEAN:false
   AllowOverwrite:BOOLEAN:true
   Count:INTEGER:1
Back to top
View user's profile Send private message
rekarm01
PostPosted: Tue Dec 26, 2017 2:56 pm    Post subject: Re: Timeout Notification Controlled Mode - doesnt generate n Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 1415
leopucci wrote:
even casting the field to this character, it did not worked
Code:

   -- ...
   IgnoreMissed:BOOLEAN:false
   AllowOverwrite:BOOLEAN:true
   Count:INTEGER:1

Everything needs to be a CHARACTER string. And in order. Count is optional; it defaults to '1'.
Back to top
View user's profile Send private message
mpong
PostPosted: Tue Dec 26, 2017 4:13 pm    Post subject: Reply with quote

Disciple

Joined: 22 Jan 2010
Posts: 164
Try out the below:

DECLARE JUMP INTERVAL;
SET JUMP = INTERVAL '60' SECOND;
DECLARE OUTPUTTIMESTAMP TIMESTAMP CURRENT_TIMESTAMP;
SET OUTPUTTIMESTAMP=OUTPUTTIMESTAMP+JUMP ;


SET OutputLocalEnvironment.TimeoutRequest.Action='SET';
SET OutputLocalEnvironment.TimeoutRequest.Identifier= 'IDENTIFIER'
SET OutputLocalEnvironment.TimeoutRequest.StartDate = CAST(OUTPUTTIMESTAMP AS DATE);
SET OutputLocalEnvironment.TimeoutRequest.StartTime = CAST(OUTPUTTIMESTAMP AS TIME);
SET OutputLocalEnvironment.TimeoutRequest.Count = 1;
SET OutputLocalEnvironment.TimeoutRequest.IgnoreMissed = FALSE;
SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = FALSE;
Back to top
View user's profile Send private message
leopucci
PostPosted: Wed Dec 27, 2017 3:37 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
mpong wrote:
Try out the below:

DECLARE JUMP INTERVAL;
SET JUMP = INTERVAL '60' SECOND;
DECLARE OUTPUTTIMESTAMP TIMESTAMP CURRENT_TIMESTAMP;
SET OUTPUTTIMESTAMP=OUTPUTTIMESTAMP+JUMP ;


SET OutputLocalEnvironment.TimeoutRequest.Action='SET';
SET OutputLocalEnvironment.TimeoutRequest.Identifier= 'IDENTIFIER'
SET OutputLocalEnvironment.TimeoutRequest.StartDate = CAST(OUTPUTTIMESTAMP AS DATE);
SET OutputLocalEnvironment.TimeoutRequest.StartTime = CAST(OUTPUTTIMESTAMP AS TIME);
SET OutputLocalEnvironment.TimeoutRequest.Count = 1;
SET OutputLocalEnvironment.TimeoutRequest.IgnoreMissed = FALSE;
SET OutputLocalEnvironment.TimeoutRequest.AllowOverwrite = FALSE;




Did not worked. On the boxes, i just have to create an identifier right?
On the field unique identifier.
They are the same on timeoutcontrolnode and timeout notification node.
On the notification node i have changed to controlled.

I was thinking.. this node that initiate the flow is a automatic timeout nofitication node. then on esql i create a request and send to the timeout control (with another unique identifier).
I think that this is ok right?

It is strange... because i can set the timeout... and then i can cancel...
If i try with a diferent identifier that was not set, it throws an error. So it is being set.

Any other clues?
Thanks again
Pucci




Code:

Action:CHARACTER:SET
   Identifier:CHARACTER:IDENTIFIER
   StartDate:DATE:java.util.GregorianCalendar[time=1514340000000,areFieldsSet=true,
areAllFieldsSet=false,lenient=true,zone=sun.util.calendar.ZoneInfo[
id="America/Sao_Paulo",offset=-10800000,dstSavings=3600000,useDaylight=true,
transitions=129,lastRule=java.util.
SimpleTimeZone[id=America/Sao_Paulo,offset=-10800000,dstSavings=3600000,useDaylight=true,startYear=0,
startMode=3,
startMonth=9,startDay=15,startDayOfWeek=1,startTime=0,startTimeMode=0,endMode=3,
endMonth=1,
endDay=15,endDayOfWeek=1,endTime=0,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,
ERA=?,YEAR=2017,MONTH=11,
WEEK_OF_YEAR=?,WEEK_OF_MONTH=?,DAY_OF_MONTH=27,DAY_OF_YEAR=?,DAY_OF_WEEK=?,DAY_OF_WEEK_IN_MONTH=?,AM_PM=0,
HOUR=0,HOUR_OF_DAY=0,MINUTE=0,SECOND=0,MILLISECOND=?,ZONE_OFFSET=?,DST_OFFSET=?]
   StartTime:TIME:java.util.GregorianCalendar[time=-62167432936173,areFieldsSet=false,areAllFieldsSet=false,lenient=true,
zone=sun.util.calendar.ZoneInfo[id="America/Sao_Paulo",offset=-10800000,dstSavings=3600000,useDaylight=true,transitions=129,
lastRule=java.util.SimpleTimeZone[id=America/Sao_Paulo,offset=-10800000,dstSavings=3600000,
useDaylight=true,startYear=0,startMode=3,
startMonth=9,startDay=15,startDayOfWeek=1,startTime=0,startTimeMode=0,endMode=3,
endMonth=1,endDay=15,endDayOfWeek=1,endTime=0,endTimeMode=0]],firstDayOfWeek=1,minimalDaysInFirstWeek=1,
ERA=0,YEAR=2,MONTH=11,WEEK_OF_YEAR=?,WEEK_OF_MONTH=?,DAY_OF_MONTH=31,DAY_OF_YEAR=?,DAY_OF_WEEK=?,
DAY_OF_WEEK_IN_MONTH=?,AM_PM=0,HOUR=9,HOUR_OF_DAY=9,MINUTE=37,SECOND=43,MILLISECOND=827,ZONE_OFFSET=?,DST_OFFSET=?]
   Count:INTEGER:1
   IgnoreMissed:BOOLEAN:false
   AllowOverwrite:BOOLEAN:false
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Dec 27, 2017 4:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
Yes you are setting the wrong field type.
Check what the field type is on a field that is already set... (like when you update)
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
leopucci
PostPosted: Wed Dec 27, 2017 5:00 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
fjb_saper wrote:
Yes you are setting the wrong field type.
Check what the field type is on a field that is already set... (like when you update)



This is the automatic generated request.
I will try to make the same sintax, let´s see

Code:

TimeoutRequest
   Action:CHARACTER:SET
   Identifier:CHARACTER:GENPROBE
   StartDate:CHARACTER:2017-12-27
   StartTime:CHARACTER:09:33:23.716999
   Count:INTEGER:130
   Interval:INTEGER:40
   IgnoreMissed:BOOLEAN:true
   AllowOverwrite:BOOLEAN:true
Back to top
View user's profile Send private message
leopucci
PostPosted: Wed Dec 27, 2017 5:50 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
fjb_saper wrote:
Yes you are setting the wrong field type.
Check what the field type is on a field that is already set... (like when you update)


Saper,

Check this weirdness!

Code:

TimeoutRequest
   Action:CHARACTER:SET
   Identifier:CHARACTER:BRASONDA
   StartDate:CHARACTER:2017-12-27
   StartTime:CHARACTER:11:42:42.301998
   Count:INTEGER:6
   Interval:INTEGER:40
   IgnoreMissed:BOOLEAN:true
   AllowOverwrite:BOOLEAN:true


So now I am generating the request, but the timeout control node is having trouble to set it, generating an exception.

Code:



ExceptionList
   RecoverableException
         File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\MessageServices\ImbDataFlowNode.cpp
         Line:INTEGER:1251
         Function:CHARACTER:ImbDataFlowNode::createExceptionList
         Type:CHARACTER:ComIbmTimeoutNotificationNode
         Name:CHARACTER:TimeoutTest#FCMComposite_1_1
         Label:CHARACTER:TimeoutTest.Generate_Probe
         Catalog:CHARACTER:BIPmsgs
         Severity:INTEGER:3
         Number:INTEGER:2230
         Text:CHARACTER:Node throwing exception
         Insert
               Type:INTEGER:14
               Text:CHARACTER:TimeoutTest.Generate_Probe
         RecoverableException
               File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\TimeoutControl\ImbTimeoutControlNode.cpp
               Line:INTEGER:1120
               Function:CHARACTER:ImbTimeoutControlNode::evaluate
               Type:CHARACTER:ComIbmTimeoutControlNode
               Name:CHARACTER:TimeoutTest#FCMComposite_1_5
               Label:CHARACTER:TimeoutTest.Control_Generate_Probe
               Catalog:CHARACTER:BIPmsgs
               Severity:INTEGER:3
               Number:INTEGER:2230
               Text:CHARACTER:rethrowing
               Insert
                     Type:INTEGER:14
                     Text:CHARACTER:TimeoutTest_Generate_Probe
               CastException
                     File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\CommonServices\ImbDateTime.cpp
                     Line:INTEGER:3290
                     Function:CHARACTER:ImbDate::ImbDate
                     Type:CHARACTER:
                     Name:CHARACTER:
                     Label:CHARACTER:
                     Catalog:CHARACTER:BIPmsgs
                     Severity:INTEGER:3
                     Number:INTEGER:2327
                     Text:CHARACTER:Invalid date
                     Insert
                           Type:INTEGER:2
                           Text:CHARACTER:-1
                     Insert
                           Type:INTEGER:5
                           Text:CHARACTER:S22007
                     Insert
                           Type:INTEGER:2
                           Text:CHARACTER:2017
                     Insert
                           Type:INTEGER:2
                           Text:CHARACTER:47
                     Insert
                           Type:INTEGER:2
                           Text:CHARACTER:27



As you can see, the date field got 47 instead of 12 but if you check the TimeoutRequest, the date is 2017-12-27.
Back to top
View user's profile Send private message
leopucci
PostPosted: Wed Dec 27, 2017 5:53 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
I think that i found a bug.

It is generating the date with strange chars..
Count sometimes goes nuts also..

TimeoutRequest
Action:CHARACTER:SET
Identifier:CHARACTER:BRA000005
StartDate:CHARACTER:2017-53-27
StartTime:CHARACTER:11:53:45
Count:INTEGER:1
IgnoreMissed:BOOLEAN:false
AllowOverwrite:BOOLEAN:false
Back to top
View user's profile Send private message
leopucci
PostPosted: Wed Dec 27, 2017 6:12 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
Check how the flow is implemented https://ibb.co/fFvh6b

[/img][/url]
Back to top
View user's profile Send private message
leopucci
PostPosted: Wed Dec 27, 2017 7:02 am    Post subject: Reply with quote

Apprentice

Joined: 09 Nov 2017
Posts: 28
Dããã

Forget to use MM instead of mm on date

Shame on me.. lol
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Timeout Notification Controlled Mode - doesnt generate notif
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.