java.lang.ClassCastException: weblogic.management.context.JMXContextImpl cannot be cast to weblogic.management.context.JMXContext (Doc ID 2072619.1)

Last updated on AUGUST 03, 2017

Applies to:

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

Symptoms

A class conflict occurs in WebLogic JMX after upgrading to WebLogic 12.1.3.0.2/jdk_1.7.0_72 upon migrating the environment from WebLogic 10.3.5/jdk_1.6.0_35 to WebLogic 12.1.3.0.2/jdk_170_72. Customer is receiving the following messages once reaching RUNNING state:

#### <bridge_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
Kernel>> <> <>
#### <bridge_1> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <>
<> <> ity.auth.Subject;)
java.lang.ClassCastException: weblogic.management.context.JMXContextImpl cannot be cast to weblogic.management.context.JMXContext.
java.lang.ClassCastException: weblogic.management.context.JMXContextImpl cannot be cast to weblogic.management.context.JMXContext
  at weblogic.management.context.JMXContextAccessImpl.getJMXContext(JMXContextAccessImpl.java:40)
  at weblogic.management.context.JMXContextHelper.getJMXContext(JMXContextHelper.java:32)

Changes

 

Cause

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 hundreds of Community platforms