My Oracle Support Banner

Upgrade to WebLogic 12.2.1.x Cause JNDI Lookup to Fail in Jax-WS SOAP Handler Class as User Role from EJB Not Pulled (Doc ID 2485877.1)

Last updated on FEBRUARY 14, 2024

Applies to:

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

Symptoms

 After upgrading from WebLogic from 12.1.3 to 12.2.1.3, JNDI lookup failing in jax-ws SOAP handler class.

User and Roles not being pulled up during lookup from a webservice

Custom application code the is doing a InitialContext.lookup. The lookup does not happen with URL over t3 connection but only with JNDI name "<CONNECTIONFACTORYNAME>"

Application log show the below error when calling webservice through handlers:

 

On WLS 12.1.3

From Admin Console, if we check the Deployments "<ejbapp> " show the Roles list. Example:

Role Conditions :

Group : jndiuser or @ejbWSUser@

Or

User : jndiuser or @ejbWSUser@

 

On WLS 12.2.1.3

We do NOT see these Role Conditions on EJB Deployments.

 

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.