-
1. Re: The issue with starting JBoss AS 7.1.1 Final server(eclipse)
rob.stryker Jan 9, 2015 1:44 PM (in response to virtus)You must wait longer before hurrying off to the browser. You must wait until the console tells you the server is started, not starting.
02:41:38,234 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3208ms - Started 133 of 208 services (74 services are passive or on-demand)
-
2. Re: The issue with starting JBoss AS 7.1.1 Final server(eclipse)
dgolovin Jan 9, 2015 1:51 PM (in response to virtus)You quote only first three lines of console output. Check if you have something like
10:37:51,605 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-9) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
in console.
Then I would check if there any port conflicts reported or try local address 127.0.0.1:8080.
-
3. Re: The issue with starting JBoss AS 7.1.1 Final server(eclipse)
virtus Jan 9, 2015 9:56 PM (in response to dgolovin)Thanks. Actually there was two problems.
1. A JBoss AS 7.1 can not work with a JRE8. Although there is writing "Java SE 6 or later (we recommend that you use the latest update available)" in the documentation.
2. I had a JAVA_OPTS variable with the "-Dcom.sun.management.jmxremote.port=1099 was unexpected at this time" configured value.
My console output was
D:\App\jboss-as-7.1.1.Final\bin>standalone.bat
Calling "D:\App\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
=-Dcom.sun.management.jmxremote.port=1099 was unexpected at this time.
I removed this variable.