Re: [jboss-as7-dev] Port conflict 8080 detection?

On 09/11/2012 04:50 PM, Cheng Fang wrote: > Thanks Neven. > > I just run standalone.sh to start as7, all the socket bindings are defaults. > > JBoss Admin Command-line Interface > JBOSS_HOME: /Users/cfang/711 > JBoss AS release: 7.1.1.Final "Brontes" > JAVA_HOME: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home > java.version: 1.6.0_35 > java.vm.vendor: Apple Inc. > java.vm.version: 20.10-b01-428 > os.name: Mac OS X > os.version: 10.8.1 > > What's interesting is, it seems random which appserver has the port 8080 > when both are running. My firefox displays as7 welcome page on > localhost:8080, while safari shows GlassFish welcome page. What happens if you refresh the browser? I have seen this happen before where the browsers are just displaying cached pages leading to confusion about what is actually running on port 8080. > I would expect some binding errors but I couldn't see any. I tried on > both 7.1.1 and 7.2 alpha1 with the same behavior. > > Cheng > > On 9/11/12 11:22 AM, Neven Cvetkovic wrote: >> Hey Chang, >> >> That's very strange. How are you starting your JBoss AS7? What does it >> say for http connector? What port is it bound to? What IP does it bind to? >> >> Anyhow, you should see something like this in the log files/console - >> if the port is already bound by some other process (on that IP, e.g. >> 127.0.0.1): >> >> 11:15:31,595 ERROR [org.apache.coyote.http11.Http11Protocol] (MSC >> service thread 1-10) Error initializing >> endpoint:java.net.BindException: Address already in use >> /127.0.0.1:8080 <http://127.0.0.1:8080> >> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:983) >> [jbossweb-7.0.13.Final.jar:] >> at >> org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190) >> [jbossweb-7.0.13.Final.jar:] >> at org.apache.catalina.connector.Connector.init(Connector.java:983) >> [jbossweb-7.0.13.Final.jar:] >> at >> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) >> [jboss-as-web-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 <http://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 <http://1.0.2.GA>] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> [classes.jar:1.6.0_33] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> [classes.jar:1.6.0_33] >> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] >> >> 11:15:31,820 ERROR [org.jboss.msc.service.fail] (MSC service thread >> 1-10) MSC00001: Failed to start service jboss.web.connector.http: >> org.jboss.msc.service.StartException in service >> jboss.web.connector.http: JBAS018007: Error starting web connector >> at >> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271) >> at >> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) >> [jboss-msc-1.0.2.GA.jar:1.0.2.GA <http://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 <http://1.0.2.GA>] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> [classes.jar:1.6.0_33] >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> [classes.jar:1.6.0_33] >> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33] >> Caused by: LifecycleException: Protocol handler initialization >> failed: java.net.BindException: Address already in use /127.0.0.1:8080 >> <http://127.0.0.1:8080> >> at org.apache.catalina.connector.Connector.init(Connector.java:985) >> at >> org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) >> ... 5 more >> .... >> 11:15:33,950 INFO [org.jboss.as.controller] (Controller Boot Thread) >> JBAS014774: Service status report >> JBAS014777: Services which failed to start: service >> jboss.web.connector.http: org.jboss.msc.service.StartException in >> service jboss.web.connector.http: JBAS018007: Error starting web connector >> ... >> 11:15:35,487 INFO [org.jboss.as <http://org.jboss.as>] (MSC service >> thread 1-10) JBAS015951: Admin console listening on http://127.0.0.1:9990 >> 11:15:35,487 ERROR [org.jboss.as <http://org.jboss.as>] (MSC service >> thread 1-10) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with >> errors) in 31877ms - Started 173 of 251 services (1 services failed or >> missing dependencies, 76 services are passive or on-demand) >> ... >> >> >> If you don't have any errors, you should see something like this: >> ... >> 11:18:55,607 INFO [org.apache.coyote.http11.Http11Protocol] (MSC >> service thread 1-13) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080 >> ... >> 11:18:56,356 INFO [org.jboss.as <http://org.jboss.as>] (Controller >> Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 >> 11:18:56,357 INFO [org.jboss.as <http://org.jboss.as>] (Controller >> Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in >> 4052ms - Started 133 of 208 services (74 services are passive or >> on-demand) >> ... >> >> >> >> Hope that helps. >> >> Cheers! >> Neven >> >> >> >> On Tue, Sep 11, 2012 at 11:12 AM, Cheng Fang <cfang(a)redhat.com >> <mailto:cfang@redhat.com>> wrote: >> >> I don't see any either on console or server.log. The other >> servers are >> Tomcat or GlassFish, both run on 8080 by default. >> >> Cheng >> >> On 9/11/12 10:49 AM, Brian Stansberry wrote: >> > There were no complaints in the logs? >> > >> > On 9/11/12 9:37 AM, Cheng Fang wrote: >> >> I already have other servers running on port 8080, and then >> forgetfully >> >> starting AS7 standalone server, and it started successfully >> without any >> >> complaints. The main root page localhost:8080 stills displays the >> >> content from the other server, but localhost:9990 does display as7 >> >> management console. >> >> >> >> Is there a port conflict detection, or is it designed this way? >> I think >> >> it would be helpful to fail fast once a port conflict is detected. >> >> >> >> Cheng >> >> _______________________________________________ >> >> jboss-as7-dev mailing list >> >> jboss-as7-dev(a)lists.jboss.org >> <mailto:jboss-as7-dev@lists.jboss.org> >> >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> >> > >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev >> >> > > > > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev > _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev