java.lang.ClassNotFoundException: org.apache.openjpa.util.CacheMap in a jetty spring environment

• Key: OPENJPA-256
• Type: Bug
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Bernd Bohmann
• Fix Version/s: 1.0.0

Description

Get a ClassNotFoundException: org.apache.openjpa.util.CacheMap.

I think the java.util.Map in Line 1405

queryCompilationCachePlugin.instantiate(Map.class, this);

of OpenJPAConfigurationImpl cause the error.

The classloader in this enviroment is a sun.misc.Launcher$AppClassLoader for java.util.Map not a WebAppClassLoader.

Changing the Map.class to CacheMap.class solves the problem (the right ClassLoader is used)

Comments

[Patrick Linskey]

How is OpenJPA configured in your environment? How are you bootstrapping it?

[Bernd Bohmann]

OpenJPA is configured by spring and part of the webapp.
The classes are enhanced at build time.

You can see the complete example at:

http://svn.apache.org/repos/asf/myfaces/tobago/trunk/example/addressbook/

the 9.6-incubating version works but any newer version shows this error.

If you want to play with it you can use this version

http://svn.apache.org/repos/asf/myfaces/tobago/tags/tobago-1.0.11/example/addressbook/

this is using a released version of tobago. You don't need to build the whole project :-).

Please change the property openjpa.version to a newer version in the pom and start the application with

mvn jetty:run-exploded and open a browser with the url http://localhost:8080

[Marc Prud'hommeaux]

The QueryCompilationCacheValue class differs from most plugins in that th
e plugin type is the standard java interface Map.class (rather than an openjpa-s
pecific interface), which means that the ClassLoader used to load the implementa
tion will be the system class loader; this presents a problem if OpenJPA is not
in the system classpath, so work around the problem by catching the IllegalArgum
entException (which is what we wrap the ClassNotFoundException in) and try again.

This is fixed as of revision 562011. The only workaround of earlier versions of OpenJPA is to set the "openjpa.QueryCompilationCache" property to "none" (thereby disabling the query compilation cache).

In my case

Configurations.newInstance wraps the Exception with a ParseException.

I will attach a patch with also catch the ParseException.

[Bernd Bohmann]

patch attached

[Marc Prud'hommeaux]

Bumping to release 1.0.1 since 1.0.0 is being released.

[Patrick Linskey]

Applied the patch, but sadly not until after the 1.0.0 deadline.

[Patrick Linskey]

Looks like we're doing another 1.0.0 retry, so this is now in.