We had the same problem. Our workaround is to start the jboss with the specific interface address instead of 0.0.0.0
-b 192.168.1.2 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228449#4228449 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228449 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
