Patch YMED causes Java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer

(Doc ID 1289099.1)

Last updated on AUGUST 03, 2017

Applies to:

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

Symptoms

This ClastCastException occurs after applying the patch YMED:

Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Integer
at weblogic.rmi.internal.ObjectIO.writeObject(ObjectIO.java:43)
at weblogic.rjvm.BasicOutboundRequest.marshalArgs(BasicOutboundRequest.java:86)
at weblogic.rmi.internal.BasicRemoteRef.sendOneway(BasicRemoteRef.java:270)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:215)
at weblogic.transaction.internal.CoordinatorImpl_1030_WLStub.startPrepare(Unknown Source)
at weblogic.transaction.internal.ServerSCInfo$StartPrepareAction.run(ServerSCInfo.java:1350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.transaction.internal.SecureAction.runAction(SecureAction.java:71)

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