0 Replies Latest reply on Sep 11, 2014 8:19 PM by Todd Heaps

    Wildfly 8.1 remote debug - Address already in use

    Todd Heaps Newbie

      I've been developing on Wildfly 8.1 for a few weeks now and have been able to succesfully migrate a sizable JEE application from JBoss 5.1.  I am now trying to get a test server working but I'm running into the error below whenever I try to start with the java option for remote debugging (-agentlib:jdwp=transport=dt_socket,address=1044,server=y,suspend=n):


      17:50:20,232 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final

      17:50:20,384 INFO  [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'

      [Host Controller] ERROR: transport error 202: bind failed: Address already in use

      [Host Controller] ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)

      [Host Controller] JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]

      [Host Controller] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)


      Note that this server has been running JBoss 5.1.0.GA with this identical remote debugging option enabled (same port) without problems.  I have verified that port 1044 is not in use prior to starting Wildfly, but have noticed that as soon as I start Wildfly, port 1044, as would be expected, shows as being use by the new java process.  Nothing else within the Wildfly configuration is using that port from what I can tell.


      ***In fact, it doesn't appear to matter what port I specify for remote debugging.  Every port attempted shows up as being in use with the above error as soon as I start Wildfly.***


      This server is running CentOS 6.4, Java (JDK) version is 1.7.0_55.  Being that this is such a simple thing, I assume I'm missing something really obvious, but I can't seem to figure it out.


      Any help would be greatly appreciated.