ClassNotFoundException for InstrumentationFactory upon startup

• Key: OPENJPA-640
• Type: Bug
• Status: Open
• Priority: Minor
• Assignee: Unassigned
• Reporter: Mingfai Ma
• Component/s: kernel
• Affects Version/s: 1.0.2, 1.1.0, 1.2.0

Description

This problem exists for a long time and it affects more than other people as well. Refer to an old thread in the mail list.
http://mail-archives.apache.org/mod_mbox/openjpa-users/200801.mbox/[e-mail]%3E

java.lang.ClassNotFoundException: org.apache.openjpa.enhance.InstrumentationFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:280)
at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(InstrumentationImpl.java:348)

Previously, I had an old trick to patch the org.apache.openjpa.enhance.InstrumentationFactory.jar to include the InstrumentationFactory but it doesn't work now.

Remarks: the problem is merely about displaying a piece of stacktrace but there is no actual impact to the OpenJPA function. (that's why I marked the priority as minor.)

Comments

[Mingfai Ma]

added remarks

[Adam Hardy]

I'd like to bring this one to the front because of two things:

(1) when debugging, the thrown exceptions stop the debugger every time I submit a request to the webserver. Not much fun when everything runs so slowly anyway.

(2) support staff get very jittery about stacktraces in the logs and don't really understand that there isn't actually something wrong.

[Kurt T Stam]

We're getting it on the jUDDI project too:

http://ci.apache.org/builders/juddi-trunk-openjpa/builds/6/steps/compile/logs/stdio

scroll down toward the bottom. It worries me that something is wrong. Is it ok to release jUDDI with this stack trace?