[
https://issues.jboss.org/browse/JBIDE-16742?page=com.atlassian.jira.plugi...
]
Richard Yang commented on JBIDE-16742:
--------------------------------------
OK. Right after I made above post, I searched and saw some post says about the binding
port in wildfly. I changed the the binding port from default -b 0.0.0.0 to -b 127.0.0.1 in
the Wildfly launch configuation's program arguments, then the war is deployed and the
application runs fine.
So, what the difference? Should this be documented and why the binding port has such
significant impact?
I am glad to close this ticket if someone can explain to me.
wildfly server always crashes in eclipse 4.3.1 during deployment
----------------------------------------------------------------
Key: JBIDE-16742
URL:
https://issues.jboss.org/browse/JBIDE-16742
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.1.Final
Environment: windows 7, eclipse 4.3.1, wildfly 8.0.0.Final jboss tools 4.1.1
Reporter: Richard Yang
Attachments: .log, server.log
When Wildfly tries to deploy war, after a while, eclipse pops out error saying
eclipse.exe is not responding and then eclipse exits with javaw.exe not cleaned up.
--
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