My Oracle Support Banner

The Global JMS activity is not processing the messages. (Doc ID 1134239.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Business Process Management Suite - Version 10.3.1 and later
Information in this document applies to any platform.
***Checked for relevance on 06-Jul-2012***

Symptoms

When the engine starts, the Global JMS  is not processing the pending messages.
The BPM engine log shows the following exception:


Engine 'BPMEngine' cannot process requests.
.
Original stack trace follows ...
.
fuego.papi.impl.EngineNotAvailableException:
Engine 'BPMEngine' cannot process requests.
at
fuego.ejbengine.EJBProcessBean.beforeMethodExecution(EJBProcessBean.java:244)
at fuego.server.AbstractProcessBean.runGlobalJmsActivity[...]
at fuego.server.execution.GlobalJMSExecutor$1.run(GlobalJMSExecutor.java:123)
at fuego.ejbengine.EJBProcessBean.executeTask(EJBProcessBean.java:149)
at
fuego.server.execution.GlobalJMSExecutor.execute(GlobalJMSExecutor.java:104)
at
fuego.ejbengine.EJBGlobalJMSExecutor.access$400(EJBGlobalJMSExecutor.java:43)
at fuego.ejbengine.EJBGlobalJMSExecutor$JMSExecutorWorker.run[...]
at java.lang.Thread.run(Thread.java:619)
.

Cause

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
Symptoms
Cause
Solution
References

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.