[
https://issues.apache.org/jira/browse/GERONIMO-5283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985598#action_12985598
]
Shawn Jiang commented on GERONIMO-5283:
---------------------------------------
to avoid the start up error is easy. we could just skip war when writing the
config.xml.
But after doing so, geronimo would not start the wab automatically without the
osgi persistence files.
> Server restart fails after a hard stop
> --------------------------------------
>
> Key: GERONIMO-5283
> URL: https://issues.apache.org/jira/browse/GERONIMO-5283
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Reporter: Kevan Miller
> Attachments: cache.JPG
>
>
> Installed the Blog sample, ran it successfully. Stopped the server (kill -9
> or reboot your system ;-)
> I get the following:
> karaf@root> Booting Geronimo Kernel (in Java 1.6.0_17)...
> Starting Geronimo Application Server v3.0-SNAPSHOT
> [************************************* ] 94% 21s Starting
> org.apache.ger...2010-05-04 09:46:28,589 ERROR [DatabaseInitializationGBean]
> Table/View 'AUTHOR' already exists in Schema 'APP'.
> [************************************* ] 94% 21s Starting
> org.apache.ger...2010-05-04 09:46:28,910 ERROR [DatabaseInitializationGBean]
> Table/View 'HOLDINGEJB' already exists in Schema 'APP'.
> [*************************************** ] 98% 22s Startup failed
>
> org.apache.geronimo.kernel.config.InvalidConfigException: Could not locate
> configs to start:
> [default/org.apache.aries.samples.blog.web/1272912147190/wab]
> at
> org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(EmbeddedDaemon.java:154)
> at
> org.apache.geronimo.system.main.EmbeddedDaemon.execute(EmbeddedDaemon.java:81)
> at org.apache.geronimo.main.Bootstrapper.execute(Bootstrapper.java:65)
> at
> org.apache.geronimo.cli.AbstractCLI.executeMain(AbstractCLI.java:65)
> at org.apache.geronimo.cli.daemon.DaemonCLI.main(DaemonCLI.java:32)
> [*************************************** ] 98% 69s Startup failed
>
> Note that the server process does not actually end. This is a problem, also.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
