4 Replies Latest reply on Jun 30, 2014 7:24 AM by tomjenkinson

Error starting blacktie-admin-services.ear

philippelaguitton Jun 29, 2014 5:15 PM

Hi,

Using JDK 1.7.0_60, wildfly 8.1.0-Final and Blacktie 5.0.2-Final I have this error :

23:32:43,671 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015973: Starting subdeployment (runtime-name: "blacktie-admin-services-5.0.2.Final.jar")

23:32:43,938 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010406: Registered connection factory java:/JmsXA

23:32:44,237 INFO [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started

23:32:44,243 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra

23:32:44,253 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]

23:32:44,255 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

23:32:44,692 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.2.Final.ear.blacktie-admin-services-5.0.2.Final.jar" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.

23:32:44,862 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.blacktie-admin-services-ear-5.0.2.Final.ear" is using a private module ("org.jboss.jts:main") which may be changed or removed in future versions without notice.

23:32:44,936 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment blacktie-admin-services-ear-5.0.2.Final.ear

23:32:45,796 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.1.0.Final

23:32:46,443 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment blacktie-admin-services-5.0.2.Final.jar

23:32:46,461 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named QueueReaperBean in deployment unit subdeployment "blacktie-admin-services-5.0.2.Final.jar" of deployment "blacktie-admin-services-ear-5.0.2.Final.ear" are as follows:

java:global/blacktie-admin-services-ear-5.0.2.Final/blacktie-admin-services-5.0.2.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean

java:app/blacktie-admin-services-5.0.2.Final/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean

java:module/QueueReaperBean!org.jboss.narayana.blacktie.administration.QueueReaperBean

java:global/blacktie-admin-services-ear-5.0.2.Final/blacktie-admin-services-5.0.2.Final/QueueReaperBean

java:app/blacktie-admin-services-5.0.2.Final/QueueReaperBean

java:module/QueueReaperBean

23:32:46,656 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: blacktie-admin-services-ear-5.0.2.Final.ear

23:32:46,800 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.1.2 (Final)

23:32:46,908 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment blacktie-admin-services-ear-5.0.2.Final.ear

23:32:48,261 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 68) HQ221003: trying to deploy queue jms.queue.BTR_BTStompAdmin

23:32:48,370 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 68) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTStompAdmin

23:32:48,387 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 66) HQ221003: trying to deploy queue jms.queue.BTR_BTDomainAdmin

23:32:48,432 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 66) JBAS011601: Bound messaging object to jndi name /queue/BTR_BTDomainAdmin

23:32:48,589 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) JBAS014142: Started message driven bean 'BlacktieStompAdministrationService' with 'hornetq-ra.rar' resource adapter

23:32:48,590 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) JBAS014142: Started message driven bean 'BlacktieAdminServiceXATMI' with 'hornetq-ra.rar' resource adapter

23:32:48,653 INFO [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (MSC service thread 1-2) onConstruct load btconfig.xml

23:32:50,317 INFO [org.jboss.narayana.blacktie.administration.BlacktieAdminService] (MSC service thread 1-2) Admin Server Started

23:32:50,320 ERROR [org.jboss.as.weld] (MSC service thread 1-2) JBAS016001: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager

at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187) [wildfly-naming-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231) [wildfly-naming-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188) [wildfly-naming-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184) [wildfly-naming-8.1.0.Final.jar:8.1.0.Final]

at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_60]

at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)

at org.jboss.as.service.AbstractService.invokeLifecycleMethod(AbstractService.java:77) [wildfly-sar-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.as.service.StartStopService.start(StartStopService.java:56) [wildfly-sar-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]

at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]

23:32:50,355 ERROR [org.jboss.as.weld] (MSC service thread 1-4) JBAS016001: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager

at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)

at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)

at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)

at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)

at javax.naming.InitialContext.lookup(InitialContext.java:411) [rt.jar:1.7.0_60]

at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)

at org.jboss.as.jmx.MBeanRegistrationService.start(MBeanRegistrationService.java:106) [wildfly-jmx-8.1.0.Final.jar:8.1.0.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_60]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_60]

at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_60]

23:32:51,282 WARN [org.jboss.weld.Validator] (MSC service thread 1-1) WELD-001471: Interceptor method start defined on class org.jboss.narayana.blacktie.administration.QueueReaperBean is not defined according to the specification. It should not throw java.lang.Exception, which is a checked exception.

23:32:52,163 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (ServerService Thread Pool -- 66) QueueReaper Started

23:32:52,287 INFO [org.jboss.narayana.blacktie.administration.QueueReaperBean] (ServerService Thread Pool -- 66) QueueReaper create timer with 30000ms

23:32:53,752 INFO [org.jboss.as.server] (ServerService Thread Pool -- 33) JBAS018559: Deployed "blacktie-admin-services-ear-5.0.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.0.2.Final.ear")

23:32:53,890 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.5.139:9990/management

23:32:53,894 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.5.139:9990

23:32:53,903 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 31899ms - Started 413 of 480 services (124 services are lazy, passive or on-demand)

This error appears on fc18 and on windows

Thanks for your help

Regards

Philippe

server.log.zip 107.1 KB
standalone-blacktie.xml 27.2 KB

1. Re: Error starting blacktie-admin-services.ear

tomjenkinson Jun 30, 2014 4:07 AM (in response to philippelaguitton)

Hi Philippe,

I haven't seen the error message before sorry!

I notice that the server says it has started and the admin service says it is deployed:

23:32:53,752 INFO [org.jboss.as.server] (ServerService Thread Pool -- 33) JBAS018559: Deployed "blacktie-admin-services-ear-5.0.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.0.2.Final.ear")
23:32:53,890 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://192.168.5.139:9990/management
23:32:53,894 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://192.168.5.139:9990
23:32:53,903 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.1.0.Final "Kenny" started in 31899ms - Started 413 of 480 services (124 services are lazy, passive or on-demand)

Does the fooapp quickstart work? It may be unrelated to BlackTie the error. Maybe you could temporarily try with WildFly 8.0.0.Final instead as a workaround?

Tom
Actions
2. Re: Error starting blacktie-admin-services.ear

zhfeng Jun 30, 2014 4:47 AM (in response to philippelaguitton)

Hi Philippe,

It looks like the errors are related to the WildFly.

Amos
Actions
3. Re: Error starting blacktie-admin-services.ear

philippelaguitton Jun 30, 2014 7:01 AM (in response to philippelaguitton)

Hi,

No error with Wildly 8.0.0 Final and foapp quickstart works
I tried with Wildfly 9.0.0 Alpha1 and got the same error

Thanks for your help

Philippe
Actions
4. Re: Error starting blacktie-admin-services.ear

tomjenkinson Jun 30, 2014 7:24 AM (in response to philippelaguitton)

Hi Philippe,

I can now see the same error in CI too actually but it didn't actually affect the running of the samples hence why we didn't detect any issue. For now I would say you should be safe with 8.1.0 even with that error message as it certainly doesn't seem to have affected any of our tests/quickstarts behavior.

We will take a look at the error message as part of [JBTM-2198] Update BlackTie build process to work with latest version of WildFly build process - JBoss Issue Tracker we aren't tackling that one just yet because the WildFly build system is in a state of change at the moment so we are going to wait for it to settle. We have are currently testing against Commits · jbosstm/jboss-as · GitHub which is from June 16 so relatively current.

Thanks for the report,
Tom
Actions

Go to original post