felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dieter Wimberger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-535) Starting Felix with YouKit Profiler causes java.lang.NoClassDefFoundError
Date Sun, 13 Apr 2008 19:25:04 GMT

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

Dieter Wimberger closed FELIX-535.
----------------------------------

    Resolution: Fixed

Works.

YourKit requires:
org.osgi.framework.bootdelegation=com.yourkit.* 


> Starting Felix with YouKit Profiler causes java.lang.NoClassDefFoundError
> -------------------------------------------------------------------------
>
>                 Key: FELIX-535
>                 URL: https://issues.apache.org/jira/browse/FELIX-535
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: felix-1.0.3
>         Environment: java version "1.5.0_13"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_13-b05-237)
> Java HotSpot(TM) Client VM (build 1.5.0_13-119, mixed mode, sharing)
> [YourKit Java Profiler 7.0.5] Using JVMTI (1.5.0_13-119;Apple Inc.;mixed mode, sharing;Mac
OS X;32 bit JVM)
> java version "1.6.0_03"
> Java(TM) SE Runtime Environment (build 1.6.0_03-b05)
> Java HotSpot(TM) Server VM (build 1.6.0_03-b05, mixed mode)
> [YourKit Java Profiler 7.0.12] Using JVMTI (1.6.0_03-b05;Sun Microsystems Inc.;mixed
mode, sharing;Linux;32 bit JVM)
>            Reporter: Dieter Wimberger
>
> I have been trying to profile Felix with the YourKit Profiler using -agentlib:yjpagent.
> Each loaded bundle will throw a:
> java.lang.NoClassDefFoundError: com/yourkit/runtime/Callback
> 	at org.apache.felix.shell.impl.Activator.<init>(Activator.java)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> 	at java.lang.Class.newInstance0(Class.java:350)
> 	at java.lang.Class.newInstance(Class.java:303)
> 	at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:3486)
> 	at org.apache.felix.framework.Felix._startBundle(Felix.java:1580)
> 	at org.apache.felix.framework.Felix.startBundle(Felix.java:1519)
> 	at org.apache.felix.framework.Felix.setFrameworkStartLevel(Felix.java:1104)
> 	at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:258)
> 	at java.lang.Thread.run(Thread.java:613)
> This happens on a fresh download, with the standard configuration (bundle repository
removed only). i.e.:
> felix.auto.start.1= \
>  file:install/base/org.apache.felix.shell-1.0.0.jar \
>  file:install/base/org.apache.felix.shell.tui-1.0.0.jar 
> YourKit seems to think that the problem is caused by the application doing strange classloading,
so I decided to report this here.
> Regards,
> Dieter

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


Mime
View raw message