OM tasks not reused when Siebel exception occurs using JCA/Siebel Resource Adapter.
Last updated on MARCH 01, 2018
Applies to:Siebel Financial Services CRM - Version 18.104.22.168 SIA  and later
Information in this document applies to any platform.
***Checked for relevance on 11-JAN-20111***
A customer has implemented a Java application on IBM Websphere 6 J2EE application server that interacts with Siebel using the java classes created by the Siebel Code Generator for the JCA/Siebel Resource Adapter. The credentials are supplied using Container-Managed Sign-on.
If the Siebel business service fails with an exception, the OM task keeps running with a Status of “Waiting for command”. For example, this occurs if the Java application tries to set a field to a value that is not included in the field’s picklist. It continues in this state until it times-out after the default 45 minutes.
If the application invokes the business service again, a new OM task is started and the previous OM task is not used again. If the business service is invoked and fails a number of times, the number of running tasks is reaching Maximum Tasks and, therefore, no more tasks can be invoked until a running task times-out.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms