openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <>
Subject [jira] Commented: (OPENJPA-640) ClassNotFoundException for InstrumentationFactory upon startup
Date Thu, 15 Oct 2009 02:23:31 GMT


Kurt T Stam commented on OPENJPA-640:

We're getting it on the jUDDI project too:

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

> ClassNotFoundException for InstrumentationFactory upon startup
> --------------------------------------------------------------
>                 Key: OPENJPA-640
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.0.2, 1.1.0, 1.2.0
>         Environment: JDK6, 1.2.0-trunk
>            Reporter: Mingfai Ma
>            Priority: Minor
> 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.
> java.lang.ClassNotFoundException: org.apache.openjpa.enhance.InstrumentationFactory
> 	at$
> 	at Method)
> 	at
> 	at java.lang.ClassLoader.loadClass(
> 	at sun.misc.Launcher$AppClassLoader.loadClass(
> 	at java.lang.ClassLoader.loadClass(
> 	at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(
> 	at sun.instrument.InstrumentationImpl.loadClassAndCallAgentmain(
> 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.)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message