My Oracle Support Banner

JMS Server Fails to Start During Start of the WebLogic Server (Doc ID 2451657.1)

Last updated on JUNE 20, 2024

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.

Symptoms

Getting the following error on JMS server when starting the WebLogic Server:

 

The jms server configuration is as follows:

<jms-server>

<name>JmsServerName_auto_1</name>

<target>ServerName</target>

<persistent-store>JmsFileStoreName_auto_1</persistent-store>

<store-enabled>false</store-enabled>

<allows-persistent-downgrade>true</allows-persistent-downgrade>

<paging-directory>/path/to/directory/JmsServerNamePaging</paging-directory>

</jms-server>

 

The below km doc has been followed to remove the <DOMAIN_HOME>/servers/SERVERNAME/tmp, <DOMAIN_HOME>/servers/SERVERNAME/cache and <DOMAIN_HOME>/servers/SERVERNAME/data/store directories but the issue still persists.

[JMSStore:Corruption] Null Pointer Exception When Starting OSB JMS Server (Doc ID 1519352.1)

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
References


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