My Oracle Support Banner

Multiple JVMs On Same OC4J Container Fail On File-Based JMS Queue Creation (Doc ID 1368638.1)

Last updated on JULY 30, 2018

Applies to:

Oracle Containers for J2EE - Version: 10.1.3.4.0 and later   [Release: AS10gR3 and later ]
Information in this document applies to any platform.

Symptoms


Using Oracle Application Server (OAS) 10.1.3.4 , trying to increase the number of processes in OC4J containers for scaling.

After increasing the number of process for the OC4J container (numprocs=1 in opmn.xml), when deploying an application using file-based JMS queues, the application shows as down, and log.xml file shows the following error:


<MSG_TEXT>[mdb-test] An error occured deploying EJB module: java.lang.InstantiationException: No javax.jms.Destination found at the specified destination-location (jms/myQueue) for MessageDrivenBean mdbAuditoria</MSG_TEXT>
<SUPPL_DETAIL><![CDATA[java.lang.InstantiationException: No javax.jms.Destination found at the specified destination-location (jms/myQueue) for MessageDrivenBean mdbAuditoria


The deployment succeeds with no errors when only 1 JVM is defined for the container.

Changes

JVM processes were increased (numprocs in opmn.xml is set to 2).

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
  Changes
  Cause
  Solution

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.