Products | Versions |
---|---|
TIBCO BusinessConnect Palette | 6.X |
After deploying a BW 6 project with the BC palette embedded, the following error occurs:
The error stack looks like:
<<<
07:41:44.875 INFO [Thread-17] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300019: BW Application [ARCSM_FileExchange.application:1.0] is impaired.
07:41:44.984 INFO [Framework Event Dispatcher: Equinox Container: 902e1ba1-d41b-0018-1988-8f03c1721ac4] com.tibco.thor.frwk.Application - Started by BusinessStudio, ignoring .enabled settings.
07:41:47.735 INFO [Job_Executor0] com.tibco.thor.frwk.Application - TIBCO-THOR-FRWK-300021: All Application dependencies are resolved for Application [ARCSM_FileExchange.application:1.0]
07:41:57.443 ERROR [CM Configuration Updater (Update: pid={http://ns.tibco.com/bw/palette/bcsr}BCConnection.0cca80d5-46a8-4965-afb4-64a76e91f139)] c.t.b.s.b.r.BcConnectionSharedRecourceFactory - TIBCO-BW-SR-BC-500034: Initialize JMS Connection Error: arcsm_fileexchange.BCConnection - com.tibco.bw.sharedresource.bc.runtime.BcConnectionSharedRecourceException: TIBCO-BW-SR-BC-500031: TIBCO-BW-SR-BC-500022: Find JMS Destination AX.BC.BC-XXX.RESPONDER.INTERCHANGE Error - Name not found: 'AX.BC.BC-XXX.RESPONDER.INTERCHANGE'
07:42:03.312 ERROR [B2BJmsTransport Restore Thread] c.t.b.s.b.r.BcConnectionSharedRecourceFactory - TIBCO-BW-SR-BC-500027: Reconnecting Failed: arcsm_fileexchange.BCConnection - tibjmsnaming://cw-tibco:7224 cause by: TIBCO-BW-SR-BC-500031: TIBCO-BW-SR-BC-500022: Find JMS Destination AX.BC.BC-XXX.RESPONDER.INTERCHANGE Error - Name not found: 'AX.BC.BC-XXX.RESPONDER.INTERCHANGE'
07:42:07.137 DEBUG [Job_Executor0] c.t.b.p.g.runtime.TimerEventSource - TIBCO-BW-PALETTE-GENERALACTIVITIES-200001: init() called. Activity [Timer], Process [arcsm_fileexchange.Send_837P_Request], Deployment Unit [ARCSM_FileExchange.application:1.0].
07:42:07.151 DEBUG [Job_Executor0] c.t.b.p.g.runtime.TimerEventSource - TIBCO-BW-PALETTE-GENERALACTIVITIES-200001: Runonce Trigger with key [42f0522f-e723-4b4a-b79c-4f8424fda6ca] is created
>>>
This error occurs because the EMS queues do not exist on the EMS server.