4:14 a.m.
Folks,
with the embedded server I see the ServiceContainer shutting down unexpectedly while
activating the OSGi subsystem. This happens repeatedly (but not always) on lighting.
Any idea what could be the possible cause or in what direction to look?
cheers
--thomas
02:13:37,309 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening on http://127.0.0.1:9990
02:13:37,312 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011006: OSGi
Framework - 2.1.0.CR10
02:13:37,313 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.2.0.Alpha1-SNAPSHOT "Steropes" started in 4866ms - Started 125 of 207 services
(81 services are passive or on-demand)
02:13:38,233 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
02:13:38,241 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001:
Bundle installed: jboss-osgi-logging:1.0.0
02:13:38,232 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001:
Bundle installed: org.apache.felix.log:1.0.0
02:13:38,253 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011001:
Bundle installed: org.apache.felix.configadmin:1.2.8
02:13:38,319 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed
to start service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
org.jboss.msc.service.StartException in service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: Container is down
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:508)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
at
org.jboss.osgi.framework.spi.AbstractIntegrationService.install(AbstractIntegrationService.java:52)
at
org.jboss.osgi.framework.spi.BootstrapBundlesService.install(BootstrapBundlesService.java:52)
at
org.jboss.as.osgi.service.BootstrapBundlesIntegration.installResolveService(BootstrapBundlesIntegration.java:171)
at
org.jboss.osgi.framework.spi.BootstrapBundlesInstall$1.complete(BootstrapBundlesInstall.java:96)
at org.jboss.osgi.framework.spi.ServiceTracker.completeInternal(ServiceTracker.java:284)
at org.jboss.osgi.framework.spi.ServiceTracker.checkAndComplete(ServiceTracker.java:157)
at
org.jboss.osgi.framework.spi.ServiceTracker.serviceCompleteInternal(ServiceTracker.java:276)
at
org.jboss.osgi.framework.spi.ServiceTracker.synchronousListenerServiceStarted(ServiceTracker.java:141)
at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.startCompleted(ServiceTracker.java:350)
at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.start(ServiceTracker.java:331)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
... 3 more
02:13:38,417 INFO [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003075: Coyote
HTTP/1.1 pausing on: http-/127.0.0.1:8080
02:13:38,350 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011005:
Bundle uninstalled: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
10:11 a.m.
MSC will shut down the ServiceContainer via a shutdown hook, but I don't
know why the hook would run with no other suspicious logging.
Looking for uses of ServiceContainer.shutdown(), I see:
The "Controller Boot Thread" spawned by AbstractControllerService will
cal it if a Throwable is thrown during boot. There is logging associated
with that though.
The Future returned by BootstrapImpl will call it if cancelled. I don't
see where it would be cancelled though.
On 1/23/13 4:14 AM, Thomas Diesler wrote:
Folks,
with the embedded server I see the ServiceContainer shutting down
unexpectedly while activating the OSGi subsystem. This happens
repeatedly (but not always) on lighting
<http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/566...;.
Any idea what could be the possible cause or in what direction to look?
cheers
--thomas
02:13:37,309 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening onhttp://127.0.0.1:9990 <http://127.0.0.1:9990/>
02:13:37,312 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011006: OSGi
Framework - 2.1.0.CR10
02:13:37,313 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.2.0.Alpha1-SNAPSHOT "Steropes" started in 4866ms - Started 125 of 207 services
(81 services are passive or on-demand)
02:13:38,233 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
02:13:38,241 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001:
Bundle installed: jboss-osgi-logging:1.0.0
02:13:38,232 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001:
Bundle installed: org.apache.felix.log:1.0.0
02:13:38,253 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011001:
Bundle installed: org.apache.felix.configadmin:1.2.8
02:13:38,319 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed
to start service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
org.jboss.msc.service.StartException in service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
Failed to start service
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.IllegalStateException: Container is down
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:508)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
at
org.jboss.osgi.framework.spi.AbstractIntegrationService.install(AbstractIntegrationService.java:52)
at
org.jboss.osgi.framework.spi.BootstrapBundlesService.install(BootstrapBundlesService.java:52)
at
org.jboss.as.osgi.service.BootstrapBundlesIntegration.installResolveService(BootstrapBundlesIntegration.java:171)
at
org.jboss.osgi.framework.spi.BootstrapBundlesInstall$1.complete(BootstrapBundlesInstall.java:96)
at
org.jboss.osgi.framework.spi.ServiceTracker.completeInternal(ServiceTracker.java:284)
at
org.jboss.osgi.framework.spi.ServiceTracker.checkAndComplete(ServiceTracker.java:157)
at
org.jboss.osgi.framework.spi.ServiceTracker.serviceCompleteInternal(ServiceTracker.java:276)
at
org.jboss.osgi.framework.spi.ServiceTracker.synchronousListenerServiceStarted(ServiceTracker.java:141)
at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.startCompleted(ServiceTracker.java:350)
at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.start(ServiceTracker.java:331)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
... 3 more
02:13:38,417 INFO [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003075:
Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8080
02:13:38,350 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011005:
Bundle uninstalled: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
4:31 p.m.
Maybe some random thing is calling System.exit()?
On 01/23/2013 10:11 AM, Brian Stansberry wrote:
MSC will shut down the ServiceContainer via a shutdown hook, but I
don't
know why the hook would run with no other suspicious logging.
Looking for uses of ServiceContainer.shutdown(), I see:
The "Controller Boot Thread" spawned by AbstractControllerService will
cal it if a Throwable is thrown during boot. There is logging associated
with that though.
The Future returned by BootstrapImpl will call it if cancelled. I don't
see where it would be cancelled though.
On 1/23/13 4:14 AM, Thomas Diesler wrote:
> Folks,
>
> with the embedded server I see the ServiceContainer shutting down
> unexpectedly while activating the OSGi subsystem. This happens
> repeatedly (but not always) on lighting
>
<http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/566...;.
>
>
> Any idea what could be the possible cause or in what direction to look?
>
> cheers
> --thomas
>
> 02:13:37,309 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console
listening onhttp://127.0.0.1:9990 <http://127.0.0.1:9990/>
> 02:13:37,312 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011006:
OSGi Framework - 2.1.0.CR10
> 02:13:37,313 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.2.0.Alpha1-SNAPSHOT "Steropes" started in 4866ms - Started 125 of 207 services
(81 services are passive or on-demand)
> 02:13:38,233 INFO [org.jboss.osgi.framework] (MSC service thread 1-4) JBOSGI011001:
Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
> 02:13:38,241 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001:
Bundle installed: jboss-osgi-logging:1.0.0
> 02:13:38,232 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011001:
Bundle installed: org.apache.felix.log:1.0.0
> 02:13:38,253 INFO [org.jboss.osgi.framework] (MSC service thread 1-6) JBOSGI011001:
Bundle installed: org.apache.felix.configadmin:1.2.8
> 02:13:38,319 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001:
Failed to start service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
org.jboss.msc.service.StartException in service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
Failed to start service
> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
> at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.IllegalStateException: Container is down
> at
org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:508)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
> at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
> at
org.jboss.osgi.framework.spi.AbstractIntegrationService.install(AbstractIntegrationService.java:52)
> at
org.jboss.osgi.framework.spi.BootstrapBundlesService.install(BootstrapBundlesService.java:52)
> at
org.jboss.as.osgi.service.BootstrapBundlesIntegration.installResolveService(BootstrapBundlesIntegration.java:171)
> at
org.jboss.osgi.framework.spi.BootstrapBundlesInstall$1.complete(BootstrapBundlesInstall.java:96)
> at
org.jboss.osgi.framework.spi.ServiceTracker.completeInternal(ServiceTracker.java:284)
> at
org.jboss.osgi.framework.spi.ServiceTracker.checkAndComplete(ServiceTracker.java:157)
> at
org.jboss.osgi.framework.spi.ServiceTracker.serviceCompleteInternal(ServiceTracker.java:276)
> at
org.jboss.osgi.framework.spi.ServiceTracker.synchronousListenerServiceStarted(ServiceTracker.java:141)
> at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.startCompleted(ServiceTracker.java:350)
> at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.start(ServiceTracker.java:331)
> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> ... 3 more
>
> 02:13:38,417 INFO [org.apache.coyote.http11] (MSC service thread 1-5) JBWEB003075:
Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8080
> 02:13:38,350 INFO [org.jboss.osgi.framework] (MSC service thread 1-1) JBOSGI011005:
Bundle uninstalled: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
>
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
>
>
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
--
- DML
4:02 a.m.
It our old friend listener ordering. The SVH is called with a stable container state
before another listener can add a service that is required to continue subsystem boot. The
SVH reports missing services and the activate mgmnt op returns. Its the test that then
shuts down the SC. I worked around this by not relying on the return of the mgmnt op for
completion. Instead the FrameworkFactory waits for the Framework to reach ACTIVE.
On Jan 23, 2013, at 11:31 PM, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
Maybe some random thing is calling System.exit()?
On 01/23/2013 10:11 AM, Brian Stansberry wrote:
> MSC will shut down the ServiceContainer via a shutdown hook, but I don't
> know why the hook would run with no other suspicious logging.
>
> Looking for uses of ServiceContainer.shutdown(), I see:
>
> The "Controller Boot Thread" spawned by AbstractControllerService will
> cal it if a Throwable is thrown during boot. There is logging associated
> with that though.
>
> The Future returned by BootstrapImpl will call it if cancelled. I don't
> see where it would be cancelled though.
>
> On 1/23/13 4:14 AM, Thomas Diesler wrote:
>> Folks,
>>
>> with the embedded server I see the ServiceContainer shutting down
>> unexpectedly while activating the OSGi subsystem. This happens
>> repeatedly (but not always) on lighting
>>
<http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/566...;.
>>
>>
>> Any idea what could be the possible cause or in what direction to look?
>>
>> cheers
>> --thomas
>>
>> 02:13:37,309 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin
console listening onhttp://127.0.0.1:9990 <http://127.0.0.1:9990/>
>> 02:13:37,312 INFO [org.jboss.osgi.framework] (MSC service thread 1-1)
JBOSGI011006: OSGi Framework - 2.1.0.CR10
>> 02:13:37,313 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS
7.2.0.Alpha1-SNAPSHOT "Steropes" started in 4866ms - Started 125 of 207 services
(81 services are passive or on-demand)
>> 02:13:38,233 INFO [org.jboss.osgi.framework] (MSC service thread 1-4)
JBOSGI011001: Bundle installed: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
>> 02:13:38,241 INFO [org.jboss.osgi.framework] (MSC service thread 1-2)
JBOSGI011001: Bundle installed: jboss-osgi-logging:1.0.0
>> 02:13:38,232 INFO [org.jboss.osgi.framework] (MSC service thread 1-1)
JBOSGI011001: Bundle installed: org.apache.felix.log:1.0.0
>> 02:13:38,253 INFO [org.jboss.osgi.framework] (MSC service thread 1-6)
JBOSGI011001: Bundle installed: org.apache.felix.configadmin:1.2.8
>> 02:13:38,319 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6)
MSC00001: Failed to start service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
org.jboss.msc.service.StartException in service
jbosgi.bundle."org.apache.felix.configadmin"."1.2.8".bid13.INSTALLED:
Failed to start service
>> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767)
>> at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>> at java.lang.Thread.run(Thread.java:662)
>> Caused by: java.lang.IllegalStateException: Container is down
>> at
org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:508)
>> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201)
>> at
org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228)
>> at
org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307)
>> at
org.jboss.osgi.framework.spi.AbstractIntegrationService.install(AbstractIntegrationService.java:52)
>> at
org.jboss.osgi.framework.spi.BootstrapBundlesService.install(BootstrapBundlesService.java:52)
>> at
org.jboss.as.osgi.service.BootstrapBundlesIntegration.installResolveService(BootstrapBundlesIntegration.java:171)
>> at
org.jboss.osgi.framework.spi.BootstrapBundlesInstall$1.complete(BootstrapBundlesInstall.java:96)
>> at
org.jboss.osgi.framework.spi.ServiceTracker.completeInternal(ServiceTracker.java:284)
>> at
org.jboss.osgi.framework.spi.ServiceTracker.checkAndComplete(ServiceTracker.java:157)
>> at
org.jboss.osgi.framework.spi.ServiceTracker.serviceCompleteInternal(ServiceTracker.java:276)
>> at
org.jboss.osgi.framework.spi.ServiceTracker.synchronousListenerServiceStarted(ServiceTracker.java:141)
>> at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.startCompleted(ServiceTracker.java:350)
>> at
org.jboss.osgi.framework.spi.ServiceTracker$SynchronousListenerServiceWrapper.start(ServiceTracker.java:331)
>> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
>> at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
>> ... 3 more
>>
>> 02:13:38,417 INFO [org.apache.coyote.http11] (MSC service thread 1-5)
JBWEB003075: Coyote HTTP/1.1 pausing on: http-/127.0.0.1:8080
>> 02:13:38,350 INFO [org.jboss.osgi.framework] (MSC service thread 1-1)
JBOSGI011005: Bundle uninstalled: jboss-as-osgi-configadmin:7.2.0.Alpha1-SNAPSHOT
>>
>>
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>> Thomas Diesler
>> JBoss OSGi Lead
>> JBoss, a division of Red Hat
>> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
4314
days inactive
4320
days old
3 comments
3 participants
participants (3)
-
Brian Stansberry -
David M. Lloyd -
Thomas Diesler