1. Home
  2. Support
Article - CS102292

Troubleshooting publish stack in Post_Release node of Release To Manufacturing Workflow and no response file is generated on Windchill Enterprise Systems Integration

Modified: 23-May-2023   


Applies To

  • Windchill Enterprise Systems Integration 9.1 to 12.1

Description

  • All publish stack on Post_Release node of Release To Manufacturing (RTM) workflow

  • No response file is generated

  • It prompts following error in (Background) method server log

tasks.com.ptc.windchill.esi.export.ExportToJMSQueue  - Error while executing the Create-Object webject.
  • More information will be logged in (Background) method server log as following if following ESIlogger is enabled in <WT_HOME>\codebase\WEB-INF\log4jMethodServer.properties
    • Before Windchill ESI 10.1, log4j.logger.com.ptc.windchill.esi.utl.ESILogger=DEBUG
    • Since Windchill ESI 10.1, log4j.logger.tasks.com.ptc.windchill.esi.export.ExportToJMSQueue=DEBUG
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: Error while executing the Create-Object webject.
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: --  Caught Exception --  
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: -- Exception Stack Trace --
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: (com.infoengine.util.IEResource/115) com.infoengine.exception.fatal.IEFatalServiceException: Lookup of Administered object with uri "com.ptc.windchill.esi.DataResponse.XXX.XXX" returned null.
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.messaging.MsgService.lookupAdminObject(MsgService.java:1359)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.messaging.MsgService.lookupQueue(MsgService.java:1375)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.messaging.MsgService.getQueueListener(MsgService.java:1437)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.messaging.MsgService._createObject(MsgService.java:2427)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.messaging.MsgService.createObject(MsgService.java:2363)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.webject.msg.CreateObject.invoke(CreateObject.java:23)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.procunit.webject.WebjectProcessor.invokeWebject(WebjectProcessor.java:624)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.procunit.webject.WebjectProcessor.processTask(WebjectProcessor.java:210)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.SAK.Webject.invoke(Webject.java:491)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.compiledTasks.file.apphome.ptc.Windchill_10$2e0.Windchill.tasks.com.ptc.windchill.esi.export.exporttojmsqueue$2exml.invoke(exporttojmsqueue$2exml.java:230)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.SAK.Task.invoke(Task.java:1799)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.infoengine.SAK.Task.invoke(Task.java:1710)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at com.ptc.windchill.esi.txn.ESIResponseSender.run(ESIResponseSender.java:147)
ERROR : com.ptc.windchill.esi.utl.ESILogger  Info*Engine task in ExportToJMSQueue.xml: at wt.session.SessionThread.run(SessionThread.java:169)
(com.infoengine.util.IEResource/115) com.infoengine.exception.fatal.IEFatalServiceException: Lookup of Administered object with uri "com.ptc.windchill.esi.DataResponse.XXX.XXX" returned null.
    at com.infoengine.messaging.MsgService.lookupAdminObject(MsgService.java:1359)
    at com.infoengine.messaging.MsgService.lookupQueue(MsgService.java:1375)
    at com.infoengine.messaging.MsgService.getQueueListener(MsgService.java:1437)
    at com.infoengine.messaging.MsgService._createObject(MsgService.java:2427)

  • The publish jobs stack in JMSReceiver_Response_ESIRespone if run publish in tester mode of TIBCO Designer

  • It contains following error in JMSReceiver_Response_ESIRespone output log

Job-XXX Error in [ProcessDefinitions/DataProcessing/Start_JMSReceive_CallMap_CBO_PD.process/JMSRepeatUntilTrue_ESIResponse/JMSReceiver_Response_ESIResponse]
Activity timed out

  • While publish is running, on TIBCO server, navigate Start > All Programs > TIBCO > TIBCO Home > TIBCO EMS X.X > Start EMS Administration tool > type connect > input TIBCO Administrator username and password

    • Type show queues

  • com.ptc.Windchill.esi.DataRequest (9.1), com.ptc.Windchill.esi.DataResponse.xxx.xxx and com.ptc.Windchill.esi.Result  queues have Rcvrs 0
  • DataResponse queue have issue

  • Type show connections

    • it does not list a connection initiated by <WCESIUser> (e.g. WCESI) (JMS user ID) from Windchill Host

  • How to check EMS/JMS queue configuration on TIBCO side

  • How to check EMS/JMS queues configuration or subscription on Windchill side

  • How to have only background method server subscribe EMS/JMS queues on Windchill side

  • How to manually create EMS/JMS queues on TIBCO side

  • How to manually subscribe EMS/JMS queues on Windchill side

  • How to troubleshoot EMS/JMS queue EMS/JMS configuration on both TIBCO and Windchill sides

This is a printer-friendly version of Article 102292 and may be out of date. For the latest version click CS102292