5:31 a.m.
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly"
To view the discussion, visit: https://community.jboss.org/message/741711#741711
--------------------------------------------------------------
Moved to our IDE forum.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741711#741711]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:35 a.m.
Peter Fajemisin [https://community.jboss.org/people/pf135_fajemsin] created the
discussion
"Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly"
To view the discussion, visit: https://community.jboss.org/message/741712#741712
--------------------------------------------------------------
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.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741712#741712]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:40 a.m.
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly"
To view the discussion, visit: https://community.jboss.org/message/741713#741713
--------------------------------------------------------------
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.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741713#741713]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:10 a.m.
Peter Fajemisin [https://community.jboss.org/people/pf135_fajemsin] created the
discussion
"Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly"
To view the discussion, visit: https://community.jboss.org/message/741718#741718
--------------------------------------------------------------
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
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741718#741718]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
6:16 a.m.
jaikiran pai [https://community.jboss.org/people/jaikiran] created the discussion
"Re: JBoss AS 7.2.0.Alpha1-SNAPSHOT not starting up properly"
To view the discussion, visit: https://community.jboss.org/message/741719#741719
--------------------------------------------------------------
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.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/741719#741719]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4497
days inactive
4497
days old
4 comments
2 participants
participants (2)
-
jaikiran pai -
Peter Fajemisin