Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to start JBoss from within Eclipse

Tags:

eclipse

jboss

I am unable to start JBoss server 5.1.0.GA version from eclipse Indigo.

Eclipse shows me message box saying 'Server JBoss v5.0 at localhost was unable to start within 500 seconds. If the server requires more time, try increasing the timeout in the server editor.' but in the console window I can see that JBoss has been actually started.

here is some part of log which I can see in console window of eclipse :

    SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
    SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface

15:14:20,212 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
15:14:20,212 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
15:14:20,222 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

    SecureManagementView/remote - EJB3.x Default Remote Business Interface
    SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface

15:14:20,252 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
15:14:20,262 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
15:14:20,272 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

    SecureProfileService/remote - EJB3.x Default Remote Business Interface
    SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface

15:14:20,362 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console
15:14:20,412 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
15:14:23,486 INFO  [TomcatDeployment] deploy, ctxPath=/BannedListSearch
15:14:27,532 INFO  [TomcatDeployment] deploy, ctxPath=/IWorkWebApp
15:14:27,813 INFO  [TomcatDeployment] deploy, ctxPath=/
15:14:29,155 INFO  [TomcatDeployment] deploy, ctxPath=/TestWebProject
15:14:30,036 INFO  [TomcatDeployment] deploy, ctxPath=/displaytag-examples-1.2
15:14:30,136 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console
15:14:30,276 INFO  [TomcatDeployment] deploy, ctxPath=/HelloWebService
15:14:30,407 ERROR [EngineConfigurationFactoryServlet] Unable to find config file.  Creating new servlet engine config file: /WEB-INF/server-config.wsdd
15:14:30,687 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8081
15:14:30,707 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
15:14:30,707 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 48s:110ms

I have increased start Timeout of server to 500 seconds then also I am getting same error. I have not changed anything else.

I am able to start JBoss from command prompt successfully but same server is not getting started from eclipse.

Please help me to start the JBoss server.

like image 364
Shekhar Avatar asked Aug 11 '11 09:08

Shekhar


1 Answers

Sound to me like the http port you are configured in JBoss is different to the port you have in the Eclipse configuration for JBoss.

Eclipse uses the port configuration to listen to JBoss' port so that it can determine that JBoss has actually started. If they differ, Eclipse thinks JBoss has never started although it actually has according to the log console. Make the ports match and it will probably work.

Updated: According to your log, JBoss is using port 8081 for HTTP:

Starting Coyote HTTP/1.1 on http-127.0.0.1-8081

Now you have to tell Eclipse to listen to that port so that it can figure out whether JBoss has started (default is 8080 and therefore Eclipse will never be aware of it!). Go to your servers view, double click on your JBoss server, and the configuration screen will come up:

enter image description here

You have to edit the HTTP port (in the 'Port' box) and set it to 8081 so that it matches your server's.

like image 92
Gonzalo Garcia Lasurtegui Avatar answered Nov 15 '22 21:11

Gonzalo Garcia Lasurtegui