[
https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-21100:
-------------------------------------
As discussed in the forums, The web port seems accurately detected to be 8080, and your
pollers are all set to check the web port. The mechanism used to check the web port is a
very simple url connection... ex:
{code}
URL pingUrl = new URL("http://" + host + ":" + 8080);
conn = pingUrl.openConnection();
((HttpURLConnection)conn).getResponseCode();
{code}
If an exception is thrown, the server is deemed to not be up yet. If the code completes
normally, it is decided that the server is up and responsive.
I am unable to replicate this at this time.
start process of WildFly-8.2.0-Final never finish (Starting,
Synchronized)
---------------------------------------------------------------------------
Key: JBIDE-21100
URL:
https://issues.jboss.org/browse/JBIDE-21100
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Environment: start process of WildFly-8.2.0-Final never finish (Starting,
Synchronized)
Reporter: carl zhang
Assignee: Rob Stryker
please refer to
https://developer.jboss.org/thread/265726?start=0&tstart=0
refer to the picture of 28-Oct-2015 9:46 AM (layer 3)
In the left panel: WildFly 8.x is configured to connect to localhost
WildFly 8.x(1) is configured to connect to remote host
(Linux)
The localhost cannot finish start process. WildFly 8.x(1) (remote) can.
What ports, or temp files, or anything else are checked when changing from starting to
started state?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)