Could you try to add the --clean option while starting the Geronimo server
? It looks like that the issue was caused by OSGi framework cache.



2013/8/23 dkateros <dkate...@gmail.com>

> Back to the work PC (the server is geronimo-tomcat7-javaee6-3.0.1 with a
> couple test datasources set up).
>
> The server boots up fine with the vanilla jar.
>
> With the patched jar a "Main not found" message is printed in geronimo.out
> after a minute or so (saw the other jira).
>
> In the latter case I see an ERROR message in geronimo.log that is not
> printed during normal start/stop with the vanilla jar.
>
> 2013-08-23 11:52:13,383 DEBUG [j2ee-system] FrameworkEvent ERROR
> org.osgi.framework.BundleException: Exception in
> org.apache.geronimo.system.osgi.BootActivator.start() of bundle
> org.apache.geronimo.framework.j2ee-system.
>         at
>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:734)
>         at
>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:683)
>         at
>
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:381)
>         at
>
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
>         at
>
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1131)
>         at
>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
>         at
>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
>         at
>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
>         at
>
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
>         at
>
> org.eclipse.osgi.framework.internal.core.EquinoxLauncher.internalStart(EquinoxLauncher.java:271)
>         at
>
> org.eclipse.osgi.framework.internal.core.EquinoxLauncher.start(EquinoxLauncher.java:241)
>         at org.eclipse.osgi.launch.Equinox.start(Equinox.java:258)
>         at
>
> org.apache.geronimo.main.FrameworkLauncher.launchOSGiFramework(FrameworkLauncher.java:195)
>         at
>
> org.apache.geronimo.main.FrameworkLauncher.launch(FrameworkLauncher.java:175)
>         at
> org.apache.geronimo.main.Bootstrapper.start(Bootstrapper.java:70)
>         at
> org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:61)
>         at
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
>         at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:33)
> Caused by: java.lang.NoClassDefFoundError:
> org/osgi/framework/wiring/BundleWiring
>         at
>
> org.apache.geronimo.gbean.runtime.GBeanInstance.<init>(GBeanInstance.java:252)
>         at
>
> org.apache.geronimo.kernel.basic.BasicKernel.loadGBean(BasicKernel.java:361)
>         at
> org.apache.geronimo.kernel.basic.BasicKernel.boot(BasicKernel.java:613)
>         at
> org.apache.geronimo.system.osgi.BootActivator.start(BootActivator.java:58)
>         at
>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:711)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at
>
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:702)
>         ... 17 more
> Caused by: java.lang.ClassNotFoundException:
> org.osgi.framework.wiring.BundleWiring
>         at
>
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:513)
>         at
>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:429)
>         at
>
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:417)
>         at
>
> org.apache.geronimo.hook.equinox.GeronimoClassLoader.loadClass(GeronimoClassLoader.java:85)
>         at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
>         ... 24 more
>
> In case this is not the culprit (looks like it), I can post the entire
> startup log. Also, if you think that it has to do with the specific server
> installation, I will happily unpack a fresh one, but I thought you might
> want to take a peek.
>
>
>
> --
> View this message in context:
> http://apache-geronimo.328035.n3.nabble.com/Classes-generated-on-runtime-javassist-classloader-issue-tp3987097p3987140.html
> Sent from the Users mailing list archive at Nabble.com.
>



-- 
Ivan

Reply via email to