geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhi Xie <daxie...@gmail.com>
Subject Re: LifecycleException on startup after server crash
Date Tue, 03 Feb 2015 09:25:24 GMT
I have met the sample issue before. As you said it could be resolved by
deleting the artifact in server's repository. But if you want to get the
root cause, I suggest to get the debug log when you meet the issue again.
We can find more information. As I know it is a classloading and dependency
problem in the most of these issue.

2015-01-27 22:15 GMT+08:00 Kevin Huntly <kmhuntly@gmail.com>:

> I don't know if anyone has responded yet... when it crashes and then the
> ear fails, what causes the crash? Any exceptions?
>
> It looks to me like Geronimo may have a bad cache following the event and
> that's what's causing the break, but I'm not sure. I've seen it happen on
> websphere, although with obviously different messages. Tomcat also gives me
> problems like this, where if there is an issue it will simply delete the
> entire war file and any related contents.
>
> ________________________________________________
>
> Kevin Huntly
> 79 Aurora Drive
> Cheektowaga, NY 14215
> Email: kmhuntly@gmail.com
> Cell: (716) 341-5669
> LinkedIn: http://www.linkedin.com/in/kevinhuntly
> ________________________________________________
>
> -----BEGIN GEEK CODE BLOCK-----
> Version: 1.0
> GCS/IT d+ s a C++ UL+++$ P+(++) L+++ E---
> W+++ N+ o K(+) w--- O- M-- V-- PS+ PE Y(+)
> PGP++(+++) t+ 5-- X-- R+ tv+ b++  DI++ D++
> G++ e(+) h--- r+++ y+++*
> ------END GEEK CODE BLOCK------
> On Jan 23, 2015 3:57 AM, "Genc, Ă–mer" <Oemer.Genc@iais.fraunhofer.de>
> wrote:
>
>>  Hey there,
>>
>>
>>
>> i am having problems with deploying my artifacts on geronimo server after
>> the server crashed.
>>
>> I am using Geronimo 3.0.1. When starting with a fresh geronimo
>> installation, my ear can be deployed and works correctly.
>>
>> However, if the module is already deployed on the server and the server
>> crashes, the server has problems starting up again.
>>
>> The reason for this is my ear. On startup the server fails with the
>> following exception, while trying to load my ear:
>>
>>
>>
>> *org.apache.geronimo.kernel.config.LifecycleException*: load of
>> TEST/com.name.ear/1.0/ear failed
>>
>>        at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(
>> *SimpleConfigurationManager.java:316*)
>>
>>        at org.apache.geronimo.system.main.EmbeddedDaemon.doStartup(
>> *EmbeddedDaemon.java:234*)
>>
>>        at org.apache.geronimo.system.main.EmbeddedDaemon.execute(
>> *EmbeddedDaemon.java:94*)
>>
>>        at org.apache.geronimo.system.osgi.BootActivator$1.execute(
>> *BootActivator.java:107*)
>>
>>        at org.apache.geronimo.main.Bootstrapper.start(
>> *Bootstrapper.java:88*)
>>
>>        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: *org.osgi.framework.BundleException*: The bundle "
>> TEST.com.name.ear_1.0.0 [378]" could not be resolved. Reason: Missing
>> Constraint: Import-Package: org.osgi.service.prefs; version="[1.1.1,1.1.1]"
>>
>>        at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(
>> *AbstractBundle.java:1327*)
>>
>>        at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(
>> *AbstractBundle.java:1311*)
>>
>>        at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(
>> *BundleHost.java:323*)
>>
>>        at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(
>> *AbstractBundle.java:299*)
>>
>>        at
>> org.apache.geronimo.kernel.config.SimpleConfigurationManager.loadConfiguration(
>> *SimpleConfigurationManager.java:311*)
>>
>>        ... 7 more
>>
>>
>>
>> Restarting the server does not solve the problem. The only way to solve
>> this is to manually delete the artifact from the repository using the
>> command line or the file system.
>>
>> However, this is a no-op for me. Can anyone give me an advice, where to
>> look and why the server has problems loading my ear on startup?
>>
>>
>>
>> Thanks in advance,
>>
>> Oemer
>>
>


-- 
Best Regards
Gary

Mime
View raw message