IBM Support

PM58660: OPENJPA DOESN'T FIND CUSTOM MAPPINGS WITH AN APPLICABLE CLASS LOADER.

Fixes are available

8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Description:
    
    When an attempt is made to instantiate a custom mapping class,
    the following exception is thrown:
    
    Caused by: <openjpa-2.1.2-SNAPSHOT-r422266:1179900 fatal user
    error> org.apache.openjpa.util.MetaDataException: Field
    "aaa.bbb.entities.MyEntity.name" declared custom mapping
    strategy "aaa.bbb.AValueHandler", but this strategy cannot be
    instantiated.
    
     at
    org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:27
    
     at
    org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:23
      at
    org.apache.openjpa.meta.JavaTypes.classForName(JavaTypes.java:20
      at
    org.apache.openjpa.jdbc.meta.MappingRepository.namedStrategy
    (MappingRepository.java:580)
     ... 96 more
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: A MetaDataException occurs declaring    *
    *                      that a custom mapping strategy cannot   *
    *                      be instantiated by OpenJPA.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The ValueHandlers for custom mappings (such as ClassStrategy,
    DiscriminatorStrategy, etc) tries to load the class using the
    OSGi ClassLoader, and not the application's ClassLoader.
    Because custom classes do not reside in that level of the
    ClassLoader hierarchy, the lookup fails and is reported as a
    MetaDataException.
    

Problem conclusion

  • The strategy to locate a Class type requested by the
    MappingRepository has been enhanced to leverage the configured
    ClassResolver.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.25, 8.0.0.4, and 8.5.0.1.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM58660

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-21

  • Closed date

    2012-05-11

  • Last modified date

    2012-05-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM63960

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP

  • R800 PSY

       UP

  • R850 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 8.0

Reference #: PM58660

Modified date: 11 May 2012