My Oracle Support Banner

BI Publisher Enterprise Scheduler Fails To Start All Nodes With Error 'JMSAdminWrapper Failed To Start JMSWrapper' And javax.naming.NameNotFoundException (Doc ID 2026013.1)

Last updated on JULY 24, 2018

Applies to:

BI Publisher (formerly XML Publisher) - Version 11.1.1.7.x and later
Information in this document applies to any platform.

Symptoms

BI Publisher Enterprise scheduler:

In a multinode environment the first node starts fine, however the other 3 nodes receive the following error in Scheduler Diagnostics:


Start Error; JMSAdminWrapper failed to start JMSWrapper, javax.naming.NameNotFoundException: While trying to lookup 'BIP.JMS.CF' didn't find subcontext 'BIP'. Resolved ''; remaining name 'BIP/JMS/CF'

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.