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

Task Engine Error in MWS logs

  • 1.  Task Engine Error in MWS logs

    Posted Thu September 14, 2017 06:17 AM

    Hello Experts,

    I am getting below error in my MWS log consistently. Any pointers?

    Version 9.12,
    Fix Level Fix 6
    Task Engine Fix level Fix 6

    2017-09-14 11:16:04 AST (M.w.o.m.Mapi]:INFO) [TE Task Monitoring Service] - MAPI: EVENT_QUEUE_FLUSH_SIZE_PROP = 1000
    2017-09-14 11:16:04 AST (M.w.o.j.JMSJNDIUtil]:FATAL) [TE Task Monitoring Service] - Error configuring JMS server!
    2017-09-14 11:16:04 AST (M.w.o.m.Mapi]:ERROR) [TE Task Monitoring Service] - MapiCommunicator object not created. JMS connection configuration is invalid or the JMS provider (broker) is down.
    2017-09-14 11:16:04 AST (Framework:FATAL) [TE Task Monitoring Service] - java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
    java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
    at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:49)
    at com.webMethods.common.mapi.jms.MapiCommunicator.(MapiCommunicator.java:97)
    at com.webMethods.optimize.management.Mapi.init(Mapi.java:220)
    at com.webMethods.optimize.management.Mapi.(Mapi.java:74)
    at com.webMethods.portal.service.task.impl.TaskMonitoringService.getMapi(TaskMonitoringService.java:494)
    at com.webMethods.portal.service.task.impl.TaskMonitoringService.run(TaskMonitoringService.java:468)
    at java.lang.Thread.run(Thread.java:748)
    Caused by: java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
    at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.initializeForClient(JMSJNDIUtil.java:118)
    at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:45)
    … 6 more
    Caused by: java.lang.RuntimeException: JMS Provider admin objects initialization error!
    at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.refresh(NirvanaJMSConfig.java:351)
    at com.webMethods.optimize.jndiUtil.JMSConfigFactory.refresh(JMSConfigFactory.java:58)
    at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.initializeForClient(JMSJNDIUtil.java:115)
    … 7 more
    Caused by: java.lang.RuntimeException: topic/conf_request does not exist in Universal Messaging Realm.
    at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.initTopics(NirvanaJMSConfig.java:172)
    at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.refresh(NirvanaJMSConfig.java:347)
    … 9 more


    #webMethods-BPMS
    #MWS-CAF-Task-Engine
    #webMethods


  • 2.  RE: Task Engine Error in MWS logs

    Posted Thu September 14, 2017 09:58 AM

    Hi Farid,

    looks like you are using Optimize and your Optimize Environment is not configured correctly.

    Regards,
    Holger


    #webMethods
    #webMethods-BPMS
    #MWS-CAF-Task-Engine