Unable To Create an Application AND Jobs in the Command Center (Doc ID 1059633.1)

Last updated on MARCH 02, 2017

Applies to:

Oracle Self Service E-Billing Business Edition - Version 6.0.0.1 and later
Information in this document applies to any platform.

Symptoms

Could not create a new job in the application. Also, the job created in the application doesn't run when executed from the command center. A number of error messages are visible in the log files. For example:

1. The error message about the missing AppProfiles directory is redundant as according to engineering

Tue Feb 02 17:14:50 IST 2010 INCHNTDLNGOSS6/172.20.212.251 N/A com.edocs.services.application.AppMgr [ See Correpsonding error in adminserverlog.txt]
- com.edocs.services.application.InvalidAppException
- com.edocs.services.application.InvalidAppException
- javax.ejb.EJBException: Failed to create directory: /opt/app/eBilling/AppProfiles/test23/

[ANS] There is no the AppProfiles directory as it is no longer needed, and in fact in the 6.0.3 but maybe even 6.0.2 we have removed this directory. If no change request exists for removing this error message I will raise one with engineering.

2. As for the messages regarding the unresolved JNDI references to ejb’s associated with indexing engineering states these are redundant.

Wed Jan 13 16:44:37 IST 2010 MON0001 com.edocs.services.monitor
- Exception occurred while looking up EJB: javax.naming.NameNotFoundException: Unable to resolve 'edx.ejb.AutoIndexVolAccept'. Resolved 'edx.ejb'; remaining name 'AutoIndexVolAccept'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1138)

[ANS] I looked at release notes [Release Notes, Oracle Self-Service E-Billing 6.0 (Doc ID 550831.1)] and there is already a change request logged for this problem. 12-1LLWU8V.


3. This error has a similar match to this reported in the Oracle Technical Notes http://forums.oracle.com/forums/thread.jspa?messageID=3046710
By increasing the trans-timeout-seconds value in weblogic-ejb-jar.xml the problem with the GXA transaction was resolved.
I had a look at the documentation, but it doesn't provide sufficient details.

http://e-docs.bea.com/wls/docs100/ejb/DDreference-ejb-jar.html#wp1434102

For example it doesn't describe how I can disable this behaviour. I am guessing that maybe setting it to 0 would do this. Also what is the value of max or should I use a literal max.
I suspect (hope) that the root cause is embedded in an exception linked to the original exception that your app could have printed out.

The default transaction timeout is 30 seconds. You can find a little more tx information in our MDB developer doc, table 7-2 (http://edocs.bea.com/wls/docs100/ejb/message_beans.html).
I do not recommend making the tx timeout infinite - a timeout useful for helping the app server (and the app!) detect and recover from failures.

Could not send message in JMSQueueAppender [JMS].
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:1065)
at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:688)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:461)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:343)
at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:966)

4. This message I found this match http://forums.oracle.com/forums/thread.jspa?messageID=3024097

After setting higher values for -Xmx in the Weblogic server start scripts, the Exceptions disappeared.

Caused by: weblogic.jms.common.JMSException: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.jms.backend.BEDestinationImpl.sendIssueMessage(BEDestinationImpl.java:1879)
at weblogic.jms.backend.BEDestinationImpl.send(BEDestinationImpl.java:2062)
at weblogic.jms.backend.BEDestinationImpl.wrappedSend(BEDestinationImpl.java:2005)
at weblogic.jms.backend.BEDestinationImpl.invoke(BEDestinationImpl.java:1501)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:759)
... 45 more
Caused by: weblogic.messaging.kernel.KernelException: Error enlisting GXA transaction
at weblogic.messaging.kernel.internal.KernelImpl.getGXATransaction(KernelImpl.java:538)
at weblogic.messaging.kernel.internal.QueueImpl.send(QueueImpl.java:307)
at weblogic.jms.backend.BEDestinationImpl.sendIssueMessage(BEDestinationImpl.java:1832)
... 49 more
Caused by: weblogic.store.gxa.GXAException: Transaction already rolled back, or the transaction manager has timed out this resource.
at weblogic.store.gxa.internal.GXAResourceImpl.enlist(GXAResourceImpl.java:523)
at weblogic.messaging.kernel.internal.KernelImpl.getGXATransaction(KernelImpl.java:536)
... 51 more

Cause

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