SOA Suite AQ Messaging Generates Error ORA-25228 in the Database Logs (Doc ID 963159.1)

Last updated on MAY 09, 2016

Applies to:

Oracle(R) BPEL Process Manager - Version 10.1.3.1 to 10.1.3.4 [Release AS10gR3]
Information in this document applies to any platform.
***Checked for relevance on 14-Sep-2011***


Symptoms

Using SOA Suite 10.1.3.4 and Asynchronous AQ services returns ORA-25228 error messages in the database and also on the SOA server side indicating that the queue is empty.

Errors seen in the SOA container log files ($ORACLE_HOME/opmn/logs) :

ORA-25228: timeout or end-of-fetch during message dequeue from BPEL.AQ_TEST_29073_T
ORA-06512: at ""SYS.DBMS_AQIN"", line 571
ORA-06512: at line 1

Also timeout errors :

ORABPEL-05002

Message handle error.
An exception occurred while attempting to process the message
"com.collaxa.cube.engine.dispatch.message.domain.PerformRecoveryMessage";
the exception is: Failed to create "java:comp/env/ejb/local/CubeEngineLocalBean" bean;
exception reported is: "javax.naming.NamingException:
  Cannot lookup java:comp/env attributes, not in a valid component
at com.evermind.server.Application.getEnvironmentContext(Application.java:1024)
at com.evermind.server.ApplicationContext.getEnvironmentContext(ApplicationContext.java:361)
at com.evermind.server.ApplicationContext.lookupInJavaContext(ApplicationContext.java:305)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:231)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:196)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at com.collaxa.cube.engine.util.EngineBeanRegistry.lookupEngineLocalBean(EngineBeanRegistry.java:103)
at com.collaxa.cube.engine.util.EngineBeanCache.getEngineLocalBean(EngineBeanCache.java:89)
at com.collaxa.cube.engine.dispatch.message.domain.PerformRecoveryMessageHandler.handle
  (PerformRecoveryMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:141)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:58)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)


ADDM Tool (Automatic Database Diagnostic Monitor) is giving the following message : Wait event SQL Net break/reset to client in wait class Application was consuming significant database time.

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