[jbosstools-issues] [JBoss JIRA] (JBIDE-16480) AS Tool don't detect running instance when starting a server anymore
[
https://issues.jboss.org/browse/JBIDE-16480?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-16480.
---------------------------------
Resolution: Partially Completed
I've tested this with two wildfly servers. It properly detects.
I've also tested this with two eap-6.2.0 servers. It properly detects.
It only fails when starting a wildfly and an eap6.2.
So the issue here seems to be an incompatability between the management communication
protocols of wildfly and eap 6.2. Unfortuantely there's nothing I can do here, so
long as the servers are using management poller. You always have the option of switching
your server to use the web port poller for detection in this type of case.
There's nothing that can be done here as far as I can see, unfortunately.
AS Tool don't detect running instance when starting a server
anymore
--------------------------------------------------------------------
Key: JBIDE-16480
URL: https://issues.jboss.org/browse/JBIDE-16480
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.Alpha2
Reporter: Xavier Coulon
Assignee: Rob Stryker
Fix For: 4.2.0.Beta1
if I had an AS 7.1 server already running (in a previous workbench instance for example),
JBT would pop a dialog asking me to use/connect to the existing instance. Now, I don't
see it anymore and I get errors during server start-up (bind failure - address already in
use) and server is in "started" mode (I guess the tooling managed to connect to
the mgmt port)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira