My Oracle Support Banner

OC4J Fails to startup with "ERROR Failed to set the internal configuration of the OC4J JMS Server" (Doc ID 372412.1)

Last updated on JULY 20, 2018

Applies to:

Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]
Information in this document applies to any platform.

Symptoms

You are running Oracle Containers For J2EE (OC4J) version 10.1.3 on a system configured whose IP address is dynamic rather than static or can change (for example a laptop running DHCP or where Virtual Private Network (VPN) software can cause a change at the network level).

OC4J has been running successfully for some time but suddenly one of the OC4J instances may fail to start and raise the following error:

This problem applies to both the "standalone" and "Application Server" installation types for OC4J and can affect any defined OC4J instance (use the home, OC4J_that is using the OC4J "lightweight" JMS implementation

Changes

Either:

  1. A change has taken place at the network level since you last started this OC4J instance.

    Possibilities include (but are not limited to) the following examples:

    • your server goes down abruptly and after a restart the IP address has changed
      (by getting a new DHCP address for instance)
    • you initiate a new VPN connection (which will change the IP address of your machine)
  2. You have started a second OC4J instance and have it's configuration incorrectly pointing to the *same* persistence store directory as a different OC4J instance

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!


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