Order Creation Through Oms_ws_requests Queue Within The Same Cartridge Is Not Working
(Doc ID 2391152.1)
Last updated on MARCH 27, 2019
Applies to:Oracle Communications Order and Service Management - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Order Creation through oms_ws_requests queue within the same cartridge is not working.
As part of the same cartridge i.e. My_SOM_Solution, we have 2 different orders: My_LSR_Cancel_Orders, My_SOM_Orchestration_Order.
My_Orchestration_Order gets created by the My_COM_Orchestration_Order (which is part of a different cartridge) through the oms_ws_requests queue and this creation is successful. However, when creating My_SOM_Orchestration_Order is trying to create order of type My_LSR_Cancel_Orders by putting the message into the same oms_ws_requests queue, we are getting the following error message in the logs and the message is not reaching the queue:
[2018-03-23T08:42:11.227+00:00] [OsmServer1] [ERROR]  [oracle.communications.ordermanagement.cluster.ws.OSMWebServiceRequestDispatcherProxyMDB] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oms-internal] [ecid: edd5302c-6ea0-4380-b501-56b9d330fc5b-00000008,0:619:3204] [APP: oms] [partition-name: DOMAIN] [tenant-name: GLOBAL] Unable to submit web service request[[
javax.jms.JMSException: [JMSPool:169822]Unable to use a wrapped JMS session in the transaction because two-phase commit is not available.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document