IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

JMS trigger is not suspended

webMethods Community Member

webMethods Community MemberMon January 09, 2017 05:18 AM

webMethods Community Member

webMethods Community MemberMon May 21, 2018 09:35 AM

  • 1.  JMS trigger is not suspended

    Posted Tue March 24, 2015 06:32 AM

    Hi All,

    JMS trigger is not suspended

    I have set the Trigger property, PFB the snapshot.

    The service is retried for 3 times siuccessfully and logs are wrriten.
    But Trigger needs to be suspended for the above condition but it is enabled.
    Kindly help us on this regard.

    Note: Resource Monitoring service is set in the trigger (isAvailable = True/False). But Resource monitoring also not invoked here.

    Thanks,
    Raj
    test.png


    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: JMS trigger is not suspended

    Posted Thu January 05, 2017 05:11 AM

    Hi,

    Did this issue resolved?
    Can you please let us know the what changes done to resolve this.

    Thanks,
    Monica


    #Integration-Server-and-ESB
    #webMethods


  • 3.  RE: JMS trigger is not suspended

    Posted Sun January 08, 2017 01:56 PM

    Can I have a outline of your trigger flow service. Make sure your flow service follows the service outline described in #41 Building Services that Retry in 9-12_Service_Development_Help.pdf


    #Integration-Server-and-ESB
    #webMethods


  • 4.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 03:19 AM

    Hi Mahesh,

    I have a jms trigger pointing to queue with some filter condition. The subscribing service mentioned in the trigger will do a http call

    Messages are picked and lost if the server is down - i.e. http call returns server down.

    I’m trying to build a retry mechanism for trigger along with resource monitoring service. Attached is the screenshot of trigger properties.
    The service is successfully retrying but trigger is not suspended at the end.
    In the resource monitoring service I’m just setting the isAvailable to ‘false’.

    Please suggest if I’m missing anything. why trigger is not suspending?


    #webMethods
    #Integration-Server-and-ESB


  • 5.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 04:24 AM

    Hello

    Could you please share the logic for your trigger service. I hope you have provided sufficient hint for Integration server to retry for the transient errors. if not, please use, pub.flow:throwExceptionForRetry to mark an exception as ISRunTimeException.

    Note: IS treats all the exception as serviceException.

    Regards
    Sasa


    #webMethods
    #Integration-Server-and-ESB


  • 6.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 04:54 AM


  • 7.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:11 AM

    Hi,
    Change the comparison as retryCount<=maxRetryCount as the count will be 0 for both the values in first run.

    Thanks,
    Sathya


    #webMethods
    #Integration-Server-and-ESB


  • 8.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:18 AM

    Thanks Satya. That worked.


    #webMethods
    #Integration-Server-and-ESB


  • 9.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:20 AM

    I tired this scenario . But , when i try to activate the trigger I get the below error.

    Trigger is locked. Change not permitted

    Any idea


    #webMethods
    #Integration-Server-and-ESB


  • 10.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:25 AM

    Hi,

    Now if i change the value of isAvailable=‘true’ and then tried testing it.
    It retried and trigger got suspended. For isAvailable=‘true’ trigger should not be suspended?
    Is my understanding right?

    Thanks,
    Monica


    #Integration-Server-and-ESB
    #webMethods


  • 11.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:27 AM

    Hi Satya,

    Trigger locking could be because of ACL issue.


    #webMethods
    #Integration-Server-and-ESB


  • 12.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:35 AM

    I guess the service is not avaialble again so it got suspended. Are you hardcoding it as true ?


    #Integration-Server-and-ESB
    #webMethods


  • 13.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 05:40 AM

    Hello

    1. The resource monitoring service is custom built and is optional.

    2. The resource monitoring service provides output (isAvailable=true) when the required resources for processing are up and running.

    3. Once the resouce monitoring service provides the necessary hint for the Integration Server to resume(isAvailable=true), IS changes the trigger state from Suspended to Active.

    4. Trigger State ( suspended) happened on account of retry mechanism is temporary.

    5. In cluster environment, suspension of trigger in node has no impact on another node…

    HTH,
    Sasa


    #Integration-Server-and-ESB
    #webMethods


  • 14.  RE: JMS trigger is not suspended

    Posted Mon January 09, 2017 07:26 AM

    Hi,

    I had harcoded ‘isAvailable’. Yes Sasanka you are right, the suspension was temporary which was from retry.
    How to delete the resource monitoring thread.
    I had removed the entry from trigger properties, but still i could see the task running under system tasks and also could see messages on server log.

    Thanks,
    Monica


    #Integration-Server-and-ESB
    #webMethods


  • 15.  RE: JMS trigger is not suspended

    Posted Mon May 21, 2018 09:34 AM

    I tried to implement same logic but getting below error.

    [178]2018-05-21 16:59:06 IST [ISS.0134.0042E] JMS Trigger fOLDER:jms_trigger failed: com.wm.lang.flow.FlowException: [ISC.0049.9009] Missing required property switch at ‘unlabeled BRANCH’


    #Integration-Server-and-ESB
    #webMethods


  • 16.  RE: JMS trigger is not suspended

    Posted Mon May 21, 2018 09:35 AM

    Any help will be appreciated.


    #Integration-Server-and-ESB
    #webMethods


  • 17.  RE: JMS trigger is not suspended

    Posted Mon May 21, 2018 11:23 AM

    Check your BRANCH evaluate label property. Set it to true if you want branch on the expressions. Else set it to false, if you want to branch on switch value.

    Please check Service development guide for details.

    Thanks,
    Yogesh


    #Integration-Server-and-ESB
    #webMethods


  • 18.  RE: JMS trigger is not suspended

    Posted Mon May 21, 2018 11:42 AM

    Now that error is resolved but i cannot see trigger is suspended. This is my resource monitoring service and configured in trigger. In this service i have configured pub.trigger.resourcemonitoringspec that returns true/false. I make a 3rd party service call and timing out and then bringing up to see if trigger is suspending or not.


    #Integration-Server-and-ESB
    #webMethods


  • 19.  RE: JMS trigger is not suspended

    Posted Mon May 21, 2018 11:50 AM

    Also no system task is created in scheduler.


    #Integration-Server-and-ESB
    #webMethods