Jboss server in eclipse is not starting withing 400 seconds

[Harshani Wickramarathna]

Hi,
My Jboss server is not starting in eclipse. It throws the following error and stops.
error: Server JBoss v4.2 at localhost was unable to start within 400 seconds. If the server requires more time, try increasing the timeout in the server editor.
[color=red]

I'm using jboss-4.2.2.GA and eclipse3.4 ganymede. My Os is Windows XP

Thanks and regards,
Harshani

[Peter Johnson]

1) Did you change the ports that JBoss AS is using?
2) Have you secured the JMX invoker?
(Eclipse uses the JNDI and JMX ports to communicate with JBoss AS to determine if it has started.)

3) If you run JBoss AS manually, does it start correctly?
4) Did JBoss AS actually start within Eclipse? You can test this by opening a browser and entering http://localhost:8080 (assuming you didn't change the http port)

[Sakthi Ramasamy]

If it is in eclipse, in the bottom left corner you find the small icon when clicked expands, select servers option,

1. right click JBoss server
2. you can notice timeout in seconds there
3. Increase it

Restart the server, and i am sure this time you wont get that error.

[Peter Johnson]

Restart the server, and i am sure this time you wont get that error.

I rather doubt that. Unless Harshani is deploying several very complex apps, or is running an a very underpowered machine, 400 seconds should be more than enough time for JBoss AS to start up, so increasing the start time limit will only delay the display of the error message.

(When did 'quote' break???)

[Jaikiran Pai]

Peter Johnson wrote:

Restart the server, and i am sure this time you wont get that error.

...
(When did 'quote' break???)

"Disable BB Code in this message" checkbox appears to be set on, in Sakthi's and your reply :)

[Peter Johnson]

Jaikiran Pai wrote:"Disable BB Code in this message" checkbox appears to be set on, in Sakthi's and your reply :)

Ah, I probably inherited the setting from Sakthi; it's fixed now. Thanks!

[Vijeth Konanavar Bhadrappa]

Hi,

I am using Jboss_4_2_0_GA and Eclpise 3.4. I am problem related to Starting of Jboss through Eclipse. When i start Jboss through Eclipse, server starts up and runs fine.

09:51:02,280 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
09:51:02,295 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
09:51:02,311 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 35s:356ms

But in the Progress view(of eclipse), it will showing "Starting Jboss..". I kept the value as 85000 for Jboss Startup time. When i stop jboss, a alert mesage will prompt as "Jboss failed to start".

Please help me in solving this. How do eclipse will come to know that status of Jboss as started or starting?

[Peter Johnson]

Please answer the first three questions I asked Harshani (you already answered question 4).

Also answer these:

5) Did you install JBoss Tools?
6) How did you create the JBoss AS server within Eclipse? Specifically, on the Define A New Server dialog, which entry did you select? Was it "JBoss | JBos v4.2" or some other entry?

By the way, you really should have asked this is a new topic rather than appending to this one.

[Vijeth Konanavar Bhadrappa]

Hi Peter Johnson, thank you for your help.

While creating Jboss AS i had wrongly selected Jboss v4.0 whereas i should have Jboss v4.2. Now i changed it to Jboss v4.2 and started it. It is showing "Started" and working fine now.

But please can you help in understanding how Eclipse will come to know about the status of Jboss server? "Started/Stopped/Running".

[Peter Johnson]

Vijeth Konanavar Bhadrappa wrote:But please can you help in understanding how Eclipse will come to know about the status of Jboss server? "Started/Stopped/Running".

See my parenthetical comment under question 2 in my earlier post.

[Shilpi Mangal]

Hi,

I am also facing the issue mentioned here. I have changed the Jboss AS to version 4.2 as advised. But it did not solve the problem. On seeing the console, I can see that server is actually started.

My answers :
1) Did you change the ports that JBoss AS is using? NO
2) Have you secured the JMX invoker? NO ( I am not very clear about this but I did not make any such changes).

Below is the start up log:

   
[code]  
19:28:54,265 INFO  [Server] Starting JBoss (MX MicroKernel)...
19:28:54,265 INFO  [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)
19:28:54,265 INFO  [Server] Home Dir: C:\Installed\jboss\jboss-4.2.2.GA
19:28:54,265 INFO  [Server] Home URL: file:/C:/Installed/jboss/jboss-4.2.2.GA/
19:28:54,265 INFO  [Server] Patch URL: null
19:28:54,265 INFO  [Server] Server Name: default
19:28:54,265 INFO  [Server] Server Home Dir: C:\Installed\jboss\jboss-4.2.2.GA\server\default
19:28:54,265 INFO  [Server] Server Home URL: file:/C:/Installed/jboss/jboss-4.2.2.GA/server/default/
19:28:54,265 INFO  [Server] Server Log Dir: C:\Installed\jboss\jboss-4.2.2.GA\server\default\log
19:28:54,265 INFO  [Server] Server Temp Dir: C:\Installed\jboss\jboss-4.2.2.GA\server\default\tmp
19:28:54,265 INFO  [Server] Root Deployment Filename: jboss-service.xml
19:28:54,546 INFO  [ServerInfo] Java version: 1.6.0_11,Sun Microsystems Inc.
19:28:54,546 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 11.0-b16,Sun Microsystems Inc.
19:28:54,546 INFO  [ServerInfo] OS-System: Windows Vista 6.0,x86
19:28:54,905 INFO  [Server] Core system initialized
19:28:56,871 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
19:28:56,871 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
19:28:57,399 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
19:28:57,399 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
19:28:57,555 INFO  [TransactionManagerService] Starting recovery manager
19:28:57,664 INFO  [TransactionManagerService] Recovery manager started
19:28:57,664 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
19:28:59,895 INFO  [EJB3Deployer] Starting java:comp multiplexer
19:29:00,161 INFO  [STDOUT] no object for null
19:29:00,177 INFO  [STDOUT] no object for null
19:29:00,193 INFO  [STDOUT] no object for null
19:29:00,208 INFO  [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
19:29:00,224 INFO  [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
19:29:02,033 INFO  [NativeServerConfig] JBoss Web Services - Native
19:29:02,033 INFO  [NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)
19:29:02,986 INFO  [Embedded] Catalina naming disabled
19:29:03,142 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre6/bin/client;C:/Program Files/Java/jre6/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\IDM Computer Solutions\UltraEdit-32;C:\Installed\ant\bin\;C:\Program Files\Java\jdk1.5.0_12\bin;C:\Program Files\QuickTime\QTSystem\
19:29:03,205 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
19:29:03,205 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
19:29:03,205 INFO  [Catalina] Initialization processed in 223 ms
19:29:03,205 INFO  [StandardService] Starting service jboss.web
19:29:03,205 INFO  [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
19:29:03,252 INFO  [Catalina] Server startup in 43 ms
19:29:03,361 INFO  [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
19:29:04,063 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
19:29:04,204 INFO  [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
19:29:04,314 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
19:29:04,938 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
19:29:05,359 INFO  [MailService] Mail Service bound to java:/Mail
19:29:05,516 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
19:29:05,563 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
19:29:05,594 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
19:29:05,625 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
19:29:05,688 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
19:29:05,719 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
19:29:05,766 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
19:29:05,781 INFO  [QuartzResourceAdapter] start quartz!!!
19:29:05,859 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
19:29:05,875 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
19:29:05,891 INFO  [RAMJobStore] RAMJobStore initialized.
19:29:05,891 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
19:29:05,891 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
19:29:05,891 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
19:29:06,905 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
19:29:07,141 INFO  [A] Bound to JNDI name: queue/A
19:29:07,141 INFO  [B] Bound to JNDI name: queue/B
19:29:07,141 INFO  [C] Bound to JNDI name: queue/C
19:29:07,141 INFO  [D] Bound to JNDI name: queue/D
19:29:07,141 INFO  [ex] Bound to JNDI name: queue/ex
19:29:07,156 INFO  [testTopic] Bound to JNDI name: topic/testTopic
19:29:07,156 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
19:29:07,156 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
19:29:07,156 INFO  [testQueue] Bound to JNDI name: queue/testQueue
19:29:07,219 INFO  [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
19:29:07,234 INFO  [DLQ] Bound to JNDI name: queue/DLQ
19:29:07,343 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
19:29:07,375 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
19:29:07,577 INFO  [DefaultEndpointRegistry] register: jboss.ws:context=testWs2,endpoint=HelloWS
19:29:07,733 INFO  [TomcatDeployer] deploy, ctxPath=/testWs2, warUrl=.../tmp/deploy/tmp1226745621001346445testWs2-exp.war/
19:29:09,293 INFO  [WSDLFilePublisher] WSDL published to: file:/C:/Installed/jboss/jboss-4.2.2.GA/server/default/data/wsdl/testWs2.war/HelloWorldService5788355962877460711.wsdl
19:29:09,404 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
19:29:09,419 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
19:29:09,435 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 15s:170ms

Thanks.

[Peter Johnson]

Shilpi, welcome to Java Ranch!

1) Which version of Eclipse are you using?
2) Have you installed JBoss Tools?
3) What selections did you make in the New Server dialog?

I really recommend installing JBoss Tools and using th "JBoss Community | JBoss 4.2.x" selection for creating the server.