[
https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-24006:
-------------------------------------
Is anyone able to get specific steps to reproduce here? Including versions to use, and
whether I need to designate an override to reproduce, or if that's the workaround?
I'll play with it, but some more clear instructions would definitely help.
Wildfly server adapter does not report error and works
inconsistently
---------------------------------------------------------------------
Key: JBIDE-24006
URL:
https://issues.jboss.org/browse/JBIDE-24006
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.3.Final
Reporter: Jeff MAURY
Assignee: Rob Stryker
Labels: server, server_adapter, wildfly
Fix For: 4.4.4.AM2
If Wildfly uses 9999 as the management port, then no error is reported but the adapter
does not work.
Here is an except we've got from the customer:
{noformat}
I have an important update on this. I think it's mostly good news.
I debugged the issue via a virtual session with the person that develops the WildFly
plugin for NetBeans. What we found out is that the management port I was using, 9999,
conflicts with Netty. For context, I had to specify a port override since 9990 commonly
conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and
9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything
basically breaks without a real error message indicating the underlying issue. Using 9990
on the other hand clearly indicated a port conflict.
I tried the same thing on Eclipse with exactly the same results.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)