Using JMS Adapater You Receive "Cannot create consumer on imported (store-and-forward) destination because it is not allowed to receive messages from an imported destination" (Doc ID 1359113.1)

Last updated on JANUARY 09, 2015

Applies to:

Oracle SOA Platform - Version 11.1.1.1.0 and later
Information in this document applies to any platform.

Symptoms

You have an installation of Oracle Application Server 10g or Fusion Middleware 11g where you are using the to run BPEL processes and have implemented a BPEL process that uses the JMS Adapter to poll for messages from a JMS Queue that has been exposed via a WebLogic Store and Forward (SAF) Service.

At run-time, each time the adapter attempts to read from the Queue to poll for an available message, the JMS Adapter encounters the following error:

JCA: ORABPEL-12135
ERRJMS_ERR_CR_QUEUE_CONS.
Error while creating Queue consumer: [Caused by: Cannot create consumer on imported (store-and-forward) destination because it is not allowed to receive messages from an imported destination].
Please examine the log file to determine the problem

Which is based on the following underlying exception:

Caused by: javax.jms.JMSException: Cannot create consumer on imported (store-and-forward) destination because it is not allowed to receive messages from an imported destination
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
at weblogic.jms.frontend.FEConsumer.<init>(FEConsumer.java:259)
at weblogic.jms.frontend.FESession$2.run(FESession.java:989)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.jms.frontend.FESession.consumerCreate(FESession.java:985)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2931)
at weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.java:961)
at weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServerRef.java:276)
at weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(DispatcherServerRef.java:141)
at weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherServerRef.java:34)
at weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServerRef.java:111)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

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