My Oracle Support Banner

Error "Failed to set the internal configuration of the OC4J JMS Server with" After Defining Virtual Hostname (Doc ID 398973.1)

Last updated on APRIL 22, 2019

Applies to:

Oracle Fusion Middleware - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms

In a Unix system, a virtual IP/Hostname (vip1) has been created. This was done to have two nodes in the cluster: node1 and node2, both attached to one NetApp Filer (netapp1) disk storage device where all of Oracle software, databases, OC4J Application, and configuration files exist.

When the vip1 virtual hostname was introduced on node1, everything still worked fine. Interchangeably these URLS could be used: (http://nod1.<DOMAIN>.<PORT>,
http://vip1.<DOMAIN>.<PORT>).

After switching the virtual hostname over to node2 node (editing key config files opmn.xml and httpd.conf), changing the hostname references from node1 to vip1.) and after turning off all oracle on node1 node, then proceeding to turn the oracle components on, one by on, on node2 node, the following results are observed:

  1. RDBMS - worked perfect
  2. HTTP_server - works (both URL's node2, vip1)
  3. OC4J home - DOES NOT WORK. generating the following errors:
    06/11/07 08:17:33 *** (SEVERE) Failed to set the internal configuration of the
    OC4J JMS Server with:
    XMLJMSServerConfig[file:<ORACLE_HOME>/j2ee/home/config/jms.xml]
    06/11/07 08:17:37 WARNING: Application.setConfig Application: default is in
    failed state as initialization failedjava.lang.InstantiationException: Error
    initializing ejb-modules: Resource exception(OracleASjms) for MessageDrivenBean
    event during endpoint activation: failure looking up
    ConnectionFactoryJndiName:jms/XAQueueConnectionFactory:
    javax.resource.spi.ResourceAdapterInternalException: Looking up
    jms/XAQueueConnectionFactory: javax.naming.NameNotFoundException:
    jms/XAQueueConnectionFactory not found
    Nov 7, 2006 8:17:37 AM com.evermind.server.Application setConfig
    WARNING: Application: default is in failed state as initialization
    failedjava.lang.InstantiationException: Error initializing ejb-modules:
    Resource exception(OracleASjms) for MessageDrivenBean event during endpoint
    activation: failure looking up
    ConnectionFactoryJndiName:jms/XAQueueConnectionFactory:

Changes

 

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.