-
1. Re: Localhost:9090 not worked for JBoss
wdfink Sep 25, 2015 4:57 AM (in response to alaaarfaj)Not sure whether the guide change anything, but the default ports are 8080 for public web and 9990 for the management console.
Could you check this ports?
Also you can look into the server.log file to see which ip/port the services bind
-
2. Re: Localhost:9090 not worked for JBoss
alaaarfaj Sep 26, 2015 4:27 AM (in response to wdfink)in the guide they mension that the recomended port for jboss http connection is 9090
-
3. Re: Localhost:9090 not worked for JBoss
alaaarfaj Sep 26, 2015 5:47 PM (in response to wdfink)I check many ports. As mentioned in the guide, I need to change only the http port to 9090 in standalone file. I try many ports: 8080, 9090, 9990, 8008 and more. each time i get web page can't be displayed!
-
4. Re: Localhost:9090 not worked for JBoss
wdfink Sep 28, 2015 3:15 PM (in response to alaaarfaj)Which guide? The wiki you mentioned above?
I'm not the Windows expert here
What should be available on port 9090? The applicaiton http traffic?
What do you change in the standalone.xml and how the start command look like?
Also you might attach the logfile
-
5. Re: Localhost:9090 not worked for JBoss
alaaarfaj Sep 29, 2015 10:10 AM (in response to wdfink)yes, in the wiki
take a look:
The i2b2 recommends you use the default port of 9090 for your http connection and 9009 for your AJP 1.3. If these ports are unavailable because another application is using them then you will need to edit the standalone.xml file to reconfigure them. This file is located in the following directory:
YOUR_JBOSS_HOME_DIR\standalone\configuration\standalone.xml
The two items to change in the standalone.xml file are:1. Change the non-SSL HTTP/1.1 Connector to a port that is available in your system. (example shown below)
<
socket-binding
name
=
"http"
port
=
"8080"
/>
2. Change the AJP 1.3 Connector to another port that is available in your system. (example shown below)
<
socket-binding
name
=
"ajp"
port
=
"8008"
/>
Warning:
The i2b2 install scripts are using port 9090 for JBoss. Therefore if you are changing the above ports in your standalone.xml file then you will need to make the same port changes to all the install scripts.
-
6. Re: Localhost:9090 not worked for JBoss
alaaarfaj Sep 29, 2015 12:20 PM (in response to wdfink)and after i change the port configuration, i install the jboss as a service by using command prompt: install service. After that go to administrative tools/ services/ jboss properties and select start automatically. To check if the service start correctly, i type localhost:9090 in the browser but, unfortunately it doesn't works.
-
7. Re: Localhost:9090 not worked for JBoss
alaaarfaj Oct 1, 2015 11:52 PM (in response to wdfink)i think i miss some step. Is there any refresh or restart step after change the port number?
-
8. Re: Localhost:9090 not worked for JBoss
alaaarfaj Oct 2, 2015 6:54 AM (in response to alaaarfaj)I solve my problem.
I used jdk 8 but I found some articles that said jdk 8 not worked with jboss 7. Either use jdk 7 or earlier with jboss 7 or use jdk 8 with wildfly. So, i install jdk 7 and it works.