JMS Exceptions seen from attesttask during large attestation runs (Doc ID 1417904.1)

Last updated on MARCH 08, 2017

Applies to:

Identity Manager - Version 11.1.1.3.6 to 11.1.2.2.9 [Release 11g]
Information in this document applies to any platform.
**Checked For Relevance 16-June-2016**

Goal

When calling OIM API "com.thortech.xl.attestation.AttestationEngine.attestTask" to submit responses of 23942 attestation tasks, there's a JMS Exception thrown by OIM Server.

We get JMS related errors such as:

<Oct 13, 2011 8:35:56 PM CDT> <Error> <XELLERATE.DATABASE> <BEA-000000> <Class/Method: DirectDB/getConnection encounter some problems: Error while retrieving database connection.Please check for the follwoing
Database srever is running.
Datasource configuration settings are correct.
java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction has timed out when making request to XAResource 'WLStore_oim_test_OIMJMSFileStore_auto_1'.
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1609)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1496)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at oracle.iam.platform.utils.vo.OIMDataSource.getConnection(OIMDataSource.java:57)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:217)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:148)
...
Caused by: weblogic.transaction.TimedOutException: Transaction has timed out when making request to XAResource 'WLStore_oim_test_OIMJMSFileStore_auto_1'.
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1607)
... 46 more
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1515)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:439)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at oracle.iam.platform.utils.vo.OIMDataSource.getConnection(OIMDataSource.java:57)
at com.thortech.xl.util.DirectDB.getConnection(DirectDB.java:217)


AND


<Oct 13, 2011 8:31:44 PM CDT> <Error> <XELLERATE.JMS> <BEA-000000> <Error: Uncategorized exception occured during JMS processing; nested exception is weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction in AttestationWorkflowOfflineMessageProducer/sendMessage.
org.springframework.jms.UncategorizedJmsException: Uncategorized exception occured during JMS processing; nested exception is weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at org.springframework.jms.support.JmsUtils.convertJmsAccessException(JmsUtils.java:308)
at org.springframework.jms.support.JmsAccessor.convertJmsAccessException(JmsAccessor.java:168)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:474)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:539)
at oracle.iam.platform.async.messaging.MessageSenderImpl.send(MessageSenderImpl.java:75)
at oracle.iam.platform.async.messaging.TaskRouter.route(TaskRouter.java:78)
at oracle.iam.platform.async.messaging.MessagingExecutionService.submit(MessagingExecutionService.java:43)
at oracle.iam.platform.async.impl.AsyncServiceImpl.submit(AsyncServiceImpl.java:74)
at com.thortech.xl.schedule.jms.messageproducer.AttestationWorkflowOfflineMessageProducer.sendMessageImpl(AttestationWorkflowOfflineMessageProducer.java:48)
at com.thortech.xl.schedule.jms.messageproducer.MessageProducer.sendMessage(MessageProducer.java:52)
at com.thortech.xl.attestation.AttestationEngine.submitWorkFlowTaskToOfflineQueue(AttestationEngine.java:2266)
at com.thortech.xl.attestation.AttestationEngine.attestTask(AttestationEngine.java:470)
...
Caused By: weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:53)
at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1284)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:796)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:597)
at org.springframework.jms.core.JmsTemplate.doSend(JmsTemplate.java:574)
at org.springframework.jms.core.JmsTemplate$3.doInJms(JmsTemplate.java:541)
at org.springframework.jms.core.JmsTemplate.execute(JmsTemplate.java:471)
at org.springframework.jms.core.JmsTemplate.send(JmsTemplate.java:539)
at oracle.iam.platform.async.messaging.MessageSenderImpl.send(MessageSenderImpl.java:75)
at oracle.iam.platform.async.messaging.TaskRouter.route(TaskRouter.java:78)
at oracle.iam.platform.async.messaging.MessagingExecutionService.submit(MessagingExecutionService.java:43)
at oracle.iam.platform.async.impl.AsyncServiceImpl.submit(AsyncServiceImpl.java:74)
at com.thortech.xl.schedule.jms.messageproducer.AttestationWorkflowOfflineMessageProducer.sendMessageImpl(AttestationWorkflowOfflineMessageProducer.java:48)
at com.thortech.xl.schedule.jms.messageproducer.MessageProducer.sendMessage(MessageProducer.java:52)
at com.thortech.xl.attestation.AttestationEngine.submitWorkFlowTaskToOfflineQueue(AttestationEngine.java:2266)
at com.thortech.xl.attestation.AttestationEngine.attestTask(AttestationEngine.java:470)
at com.thortech.xl.schedule.jms.messagetype.AttestationTaskMessage.execute(AttestationTaskMessage.java:52)
at oracle.iam.platform.async.impl.TaskExecutor.executeManagedTask(TaskExecutor.java:121)


When using a custom task using the attestTask method for submitting responses for large attestation runs, how can this issue be resolved or avoided?


Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms