You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Forrest Xia (JIRA)" <ji...@apache.org> on 2012/10/10 16:03:06 UTC

[jira] [Updated] (GERONIMO-6087) See if we can improve "Main not found" errors (and other startup issues)

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

Forrest Xia updated GERONIMO-6087:
----------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.0.1
    
> See if we can improve "Main not found" errors (and other startup issues)
> ------------------------------------------------------------------------
>
>                 Key: GERONIMO-6087
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6087
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Kevan Miller
>             Fix For: 3.0.1
>
>
> In some cases a startup error will prevent the server from starting. Yet the only message the user sees is "Main not found" (or no message at all).
> I've seen this happen when trying to profile the server using YourKit. You must add com.yourkit to org.osgi.framework.bootdelegation in etc/config.properties in order for the server to start. If you don't the only error you see is "Main not found"
> Someone also reported that a non-writable java.io.tmpdir directory can lead to a "Main not found" error. For me, on Mac OS, looks like my server startup spins in a hot loop:
> {quote}
> "main" prio=5 tid=102801800 nid=0x100501000 runnable [1004ff000]
>    java.lang.Thread.State: RUNNABLE
> 	at java.io.UnixFileSystem.canonicalize0(Native Method)
> 	at java.io.UnixFileSystem.canonicalize(UnixFileSystem.java:157)
> 	at java.io.File.getCanonicalPath(File.java:559)
> 	at java.io.File.getCanonicalFile(File.java:583)
> 	at java.io.File.mkdirs(File.java:1189)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.prepareTempDir(DirectoryWatcher.java:548)
> 	at org.apache.felix.fileinstall.internal.DirectoryWatcher.<init>(DirectoryWatcher.java:137)
> 	at org.apache.felix.fileinstall.internal.FileInstall.updated(FileInstall.java:222)
> 	at org.apache.felix.fileinstall.internal.FileInstall.start(FileInstall.java:124)
> 	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)
> 	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:1130)
> 	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)
> 	- locked <7ea24ea68> (a java.lang.Object)
> 	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.launch(FrameworkLauncher.java:179)
> 	at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:47)
> 	at org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
> 	at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32)
> {quote}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira