-
1. Re: Problem port already in use
vbchin2 Feb 12, 2014 5:48 PM (in response to varaltale)Screen shots or snippets of log entries would help in looking into this further.
-
2. Re: Problem port already in use
varaltale Feb 13, 2014 2:00 AM (in response to vbchin2)07:58:49,058 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Indirizzo già in uso /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:210) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
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.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
Caused by: java.net.BindException: Indirizzo già in uso
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_21]
at sun.nio.ch.Net.bind(Net.java:344) [rt.jar:1.7.0_21]
at sun.nio.ch.Net.bind(Net.java:336) [rt.jar:1.7.0_21]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:199) [rt.jar:1.7.0_21]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_21]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:145)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:177) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
07:58:49,089 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory /appsrv/jboss/jboss-as-7.1.1.Final/standalone/deployments
07:58:49,098 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found AllenaVitaWeb.war in deployment directory. To trigger deployment create a file called AllenaVitaWeb.war.dodeploy
07:58:49,200 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/OracleDS]
07:58:50,110 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.remoting.server.management: org.jboss.msc.service.StartException in service jboss.remoting.server.management: JBAS017112: Indirizzo già in uso /127.0.0.1:9999
service jboss.remoting.server.remoting-connector: org.jboss.msc.service.StartException in service jboss.remoting.server.remoting-connector: JBAS017112: Indirizzo già in uso /192.168.41.206:4447
service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Indirizzo già in uso /127.0.0.1:9990
07:58:50,147 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
07:58:50,148 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 4837ms - Started 126 of 208 services (7 services failed or missing dependencies, 74 services are passive or on-demand)
-
3. Re: Problem port already in use
wdfink Feb 13, 2014 4:59 AM (in response to varaltale)sounds to me that you try to start a second instance.
Could you describe what you do?
If you start one instance you only need to drop the new war file into the standalone/deployments folder (and replace the existing one) this will stop the old deployed app and start the new one. All without touching the server itself