[
http://jira.amdatu.org/jira/browse/AMDATU-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10743#comment-10743
]
Ivo Ladage - van Doorn commented on AMDATU-262:
-----------------------------------------------
Just having said that, it seems that 478 is hanging;
http://bamboo.amdatu.org/bamboo/download/AMDATU-TRUNK-JOB1/build_logs/AMDATU-TRUNK-JOB1-478.log
It hangs in the UserAdminRESTTest, but just before actually starting the test:
build 21-Jan-2011 15:56:24 INFO: Started jetty 6.1.x at port 8080
[org.apache.felix.http.jetty]
build 21-Jan-2011 15:56:24 INFO: ServiceEvent UNREGISTERING
[org.amdatu.authorization.login.service]
The problem seems that for some reason the LoginService is stopped while the
test depends on the availability of this service. But why is this service
stopped? Later on the LoginService is started again:
build 21-Jan-2011 15:56:25 INFO: HTTP Context initialized for bundle 18
('authorization') [org.amdatu.authorization.login.service]
build 21-Jan-2011 15:56:25 INFO: ServiceEvent REGISTERED
[org.amdatu.authorization.login.service]
build 21-Jan-2011 15:56:25 INFO:
org.amdatu.authorization.login.service.service.LoginServiceImpl service
initialized [org.amdatu.authorization.login.service]
It seems that all of this is triggered by the httpservice going down and up.
> Bamboo builds keep getting hung on same issue
> ---------------------------------------------
>
> Key: AMDATU-262
> URL: http://jira.amdatu.org/jira/browse/AMDATU-262
> Project: Amdatu
> Issue Type: Bug
> Components: Integration Tests
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Priority: Blocker
>
> On a regular basis the bamboo builds hang on the fact that pax is shutting
> down a container that has not yet fully started. The workaround is adding
> service deps in the test that fails, but it woul dbe nice to have a
> structural solution. Thangs that come to mind:
> 1) Ad a fixed "do no shutdown before x ms"in the itest base
> 2) Add a general service dep that only registers after full framework startup
> Typical stack related to issue looks like:
> INFO: ServiceEvent REGISTERED [org.amdatu.semanticweb.sesame]
> 13-Jan-2011 15:09:52
> 13-Jan-2011 15:09:52 INFO: BundleEvent STOPPED [org.apache.felix.framework]
> 13-Jan-2011 15:09:52 Stopping Sesame application bundle...
> 13-Jan-2011 15:09:52 INFO: BundleEvent STOPPED [osgi.core]
> 13-Jan-2011 15:09:52 WARNING: Invocation of 'init' failed.
> [org.amdatu.semanticweb.sesame]
> 13-Jan-2011 15:09:52 Can only register services while bundle is active or
> activating.
> 13-Jan-2011 15:09:52 java.lang.IllegalStateException: Can only register
> services while bundle is active or activating.
> 13-Jan-2011 15:09:52 at
> org.apache.felix.framework.Felix.registerService(Felix.java:2832)
> 13-Jan-2011 15:09:52 at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:251)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
