[ 
https://issues.apache.org/jira/browse/OPENJPA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rick Curtis closed OPENJPA-640.
-------------------------------

    Resolution: Fixed

This issue should be fixed in 2.0.0 and trunk with the changes that Jeremy made 
for OPENJPA-1410. 

If the issue still exists on one of those releases, please re-open.

> ClassNotFoundException for InstrumentationFactory upon startup
> --------------------------------------------------------------
>
>                 Key: OPENJPA-640
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-640
>             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
>            Assignee: Rick Curtis
>            Priority: Minor
>             Fix For: 2.0.0-beta3
>
>
> 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/%[email protected]%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.)

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

Reply via email to