8 Replies Latest reply on Jun 14, 2012 7:16 AM by jaikiran

JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

pf135_fajemsin Jun 14, 2012 6:12 AM

Hi,

I am trying to run a simple WAR application on jboss as7.2.0-alpha 1, it seems to deploy the WAR archive, but then stops at the line saying

10:44:43,638 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 44886ms - Started 197 of 280 services (81 services are passive or on-demand)

Approx. 5 minutes after, I get a server startup failure saying "Server JBoss 7.0 Alpha Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor.". Within the 5 minutes, I try to navigate to the web application but keep getting a 404.

There is no more log to show what is wrong.

Any help please?

Thanks

Peter

Log is shown below:

WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.

10:54:42,452 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA

10:54:43,606 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA

10:54:43,806 INFO [org.jboss.as] JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting

10:54:48,390 INFO [org.jboss.as.server.deployment.scanner] JBAS015003: Found EJBExerciseWAR.war in deployment directory. To trigger deployment create a file called EJBExerciseWAR.war.dodeploy

10:54:48,452 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

10:54:48,485 INFO [org.xnio] XNIO Version 3.0.4.GA

10:54:48,516 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA

10:54:48,540 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA

10:54:48,664 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

10:54:48,669 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

10:54:48,682 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem

10:54:48,690 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

10:54:48,693 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

10:54:48,698 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

10:54:48,855 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013171: Activating Security Subsystem

10:54:49,846 INFO [org.jboss.as.connector.logging] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final)

10:54:49,944 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

10:54:49,954 INFO [org.jboss.as.security] (MSC service thread 1-8) JBAS013170: Current PicketBox version=4.0.9.Final

10:54:50,078 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]

10:54:52,186 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

10:54:52,902 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.1.0.Beta1

10:54:53,428 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)

10:54:53,951 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

10:54:53,957 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:/OracleDS]

10:54:54,634 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-5) Starting Coyote HTTP/1.1 on http-/127.0.0.1:8080

10:54:55,337 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/pfajemisin/development/apps/jboss-as-7.2.0.Alpha1-SNAPSHOT/standalone/deployments

10:54:55,341 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "EJBExerciseWAR.war"

10:54:55,342 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on 127.0.0.1:9999

10:54:55,342 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:4447

10:54:57,286 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for hotelPU

10:54:57,564 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named BookingManagerBean in deployment unit deployment "EJBExerciseWAR.war" are as follows:

java:global/EJBExerciseWAR/BookingManagerBean!com.peterfajemisin.BookingManager

java:app/EJBExerciseWAR/BookingManagerBean!com.peterfajemisin.BookingManager

java:module/BookingManagerBean!com.peterfajemisin.BookingManager

java:global/EJBExerciseWAR/BookingManagerBean

java:app/EJBExerciseWAR/BookingManagerBean

java:module/BookingManagerBean

10:54:57,847 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)

10:54:57,888 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.EJBExerciseWAR.war:main" from Service Module Loader

10:54:57,898 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011402: Starting Persistence Unit Service 'EJBExerciseWAR.war#hotelPU'

10:54:58,318 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

10:54:58,324 INFO [org.hibernate.Version] (ServerService Thread Pool -- 50) HHH000412: Hibernate Core {4.1.4.Final}

10:54:58,325 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000206: hibernate.properties not found

10:54:58,327 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000021: Bytecode provider name : javassist

10:54:58,396 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [

name: hotelPU

...]

10:54:58,414 INFO [org.hibernate.ejb.Ejb3Configuration] (ServerService Thread Pool -- 50) HHH000360: Unable to resolve mapping file [orm.xml]

10:54:59,126 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (ServerService Thread Pool -- 50) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

10:55:00,050 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect

10:55:00,132 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (ServerService Thread Pool -- 50) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory

10:55:00,143 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory

10:55:00,270 INFO [org.hibernate.validator.util.Version] (ServerService Thread Pool -- 50) Hibernate Validator 4.2.0.Final

10:55:01,190 INFO [org.apache.wicket.util.file.WebXmlFile] (MSC service thread 1-1) web.xml: url mapping found for filter with name wicket.exercise: [/exercise/*]

10:55:01,270 INFO [org.apache.wicket.Application] (MSC service thread 1-1) [wicket.exercise] init: Wicket core library initializer

10:55:01,272 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()]

10:55:01,273 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IBehaviorListener, method=public abstract void org.apache.wicket.behavior.IBehaviorListener.onRequest()]

10:55:01,273 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IFormSubmitListener, method=public abstract void org.apache.wicket.markup.html.form.IFormSubmitListener.onFormSubmitted()]

10:55:01,273 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=ILinkListener, method=public abstract void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]

10:55:01,274 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=ILinkListener, method=public abstract void org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]

10:55:01,274 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IOnChangeListener, method=public abstract void org.apache.wicket.markup.html.form.IOnChangeListener.onSelectionChanged()]

10:55:01,274 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IRedirectListener, method=public abstract void org.apache.wicket.IRedirectListener.onRedirect()]

10:55:01,275 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IRedirectListener, method=public abstract void org.apache.wicket.IRedirectListener.onRedirect()]

10:55:01,275 INFO [org.apache.wicket.RequestListenerInterface] (MSC service thread 1-1) registered listener interface [RequestListenerInterface name=IResourceListener, method=public abstract void org.apache.wicket.IResourceListener.onResourceRequested()]

10:55:01,275 INFO [org.apache.wicket.Application] (MSC service thread 1-1) [wicket.exercise] init: Wicket extensions initializer

10:55:01,291 INFO [org.apache.wicket.protocol.http.WebApplication] (MSC service thread 1-1) [wicket.exercise] Started Wicket version 1.5.6 in DEVELOPMENT mode

10:55:01,291 ERROR [stderr] (MSC service thread 1-1) ********************************************************************

10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** WARNING: Wicket is running in DEVELOPMENT mode. ***

10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** ^^^^^^^^^^^ ***

10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** Do NOT deploy to your live server(s) without changing this. ***

10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** See Application#getConfigurationType() for more information. ***

10:55:01,292 ERROR [stderr] (MSC service thread 1-1) ********************************************************************

10:55:01,341 INFO [org.jboss.web] (MSC service thread 1-1) JBAS018210: Registering web context: /EJBExercise

10:55:01,356 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "EJBExerciseWAR.war"

10:55:01,413 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

10:55:01,413 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

10:55:01,414 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" started in 20434ms - Started 197 of 280 services (81 services are passive or on-demand)

server.log.zip 28.2 KB

1. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

jaikiran Jun 14, 2012 6:00 AM (in response to pf135_fajemsin)

Are you using an IDE? Which one?
Actions
2. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

pf135_fajemsin Jun 14, 2012 6:01 AM (in response to jaikiran)

Eclipse indigo
Actions
3. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

pf135_fajemsin Jun 14, 2012 6:13 AM (in response to pf135_fajemsin)

I have attached a more verbose log, after turning on DEBUG logging. There are some errors on startup, but I am not sure how to resolve them, any help will be much appreciated.
Actions
4. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

jaikiran Jun 14, 2012 6:31 AM (in response to pf135_fajemsin)

Moved to our IDE forum.
Actions
5. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

pf135_fajemsin Jun 14, 2012 6:35 AM (in response to jaikiran)

Hi jaikiran,

I don't think this is IDE related, if I start jboss from the command line, I get the same error. I think it's more of a configuration issue.
Actions
6. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

jaikiran Jun 14, 2012 6:40 AM (in response to pf135_fajemsin)

The error you mentioned:
Approx. 5 minutes after, I get a server startup failure saying "Server JBoss 7.0 Alpha Server was unable to start within 450 seconds. If the server requires more time, try increasing the timeout in the server editor."
is an IDE message.

The logs that you posted don't contain any error messages and they show that the server has started successfully.

Are you talking about these few lines:

10:55:01,291 ERROR [stderr] (MSC service thread 1-1) ********************************************************************
10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** WARNING: Wicket is running in DEVELOPMENT mode. ***
10:55:01,291 ERROR [stderr] (MSC service thread 1-1) *** ^^^^^^^^^^^ ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** Do NOT deploy to your live server(s) without changing this. ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) *** See Application#getConfigurationType() for more information. ***
10:55:01,292 ERROR [stderr] (MSC service thread 1-1) ********************************************************************
If yes, then those really aren't ERRORs. The Wicket code seems to be using System.err to log those messages which is why it's being logged at ERROR level. That messages is asking you to set some configuration within your wicket application to disable the development mode, in production.
1 of 1 people found this helpful
Actions
7. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

pf135_fajemsin Jun 14, 2012 7:10 AM (in response to jaikiran)

I am talking about this errors:

11:22:57,613 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-4) Unable to lookup: java:/TransactionManager: javax.naming.NameNotFoundException: Error looking up TransactionManager, service service jboss.naming.context.java.TransactionManager is not started

    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:178) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:119) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:214) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at javax.naming.InitialContext.lookup(InitialContext.java:392) [rt.jar:1.6.0_27]

    at org.jboss.tm.TransactionManagerLocator.tryJNDI(TransactionManagerLocator.java:150) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:131) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]

11:22:57,645 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-4) Unable to instantiate legacy transaction manager: java.lang.ClassNotFoundException: org.jboss.tm.TxManager from [Module "org.jboss.jboss-transaction-spi:main" from local module loader @7ab7b3f9 (roots: /home/pfajemisin/development/apps/jboss-as-7.2.0.Alpha1-SNAPSHOT/modules)]

    at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423)

    at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)

    at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120)

    at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_27]

    at java.lang.Class.forName(Class.java:169) [rt.jar:1.6.0_27]

    at org.jboss.tm.TransactionManagerLocator.usePrivateAPI(TransactionManagerLocator.java:172) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.TransactionManagerLocator.locate(TransactionManagerLocator.java:133) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.TransactionManagerLocator.locateTransactionManager(TransactionManagerLocator.java:94) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<init>(ServerVMClientUserTransaction.java:93) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.<clinit>(ServerVMClientUserTransaction.java:60) [jboss-transaction-spi-7.0.0.Final.jar:7.0.0.Final]

    at org.jboss.as.txn.service.ArjunaTransactionManagerService.start(ArjunaTransactionManagerService.java:115) [jboss-as-transactions-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_27]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_27]

    at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_27]

I understand that this error is not important.

I have just re-tested by starting from the command line and waiting for up to 8 minutes and the server did not automatically shutdown, so you are right,it is IDE related.

Thanks

Peter
Actions
8. Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly

jaikiran Jun 14, 2012 7:16 AM (in response to pf135_fajemsin)

Peter Fajemisin wrote:

I am talking about this errors:

11:22:57,613 DEBUG [org.jboss.tm.TransactionManagerLocator] (MSC service thread 1-4) Unable to lookup: java:/TransactionManager: javax.naming.NameNotFoundException: Error looking up TransactionManager, service service jboss.naming.context.java.TransactionManager is not started

at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:126) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:74) [jboss-as-naming-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
...

Oh, those are actually DEBUG messages and you can ignore those. I do admit that those exception stacktraces perhaps shouldn't have been printed for DEBUG messages, but certain project do print out those.
Actions

Go to original post