Every deployment of a non-scaled EAP 6.1 gear takes ~3 minutes. I see these lines in the log that seems to indicate the cause: November 14 14:29:03 INFO oo_spawn buffer(11/) Starting jbosseap cartridge November 14 14:29:28 INFO oo_spawn buffer(11/) Found 127.1.244.1:8080 listening port November 14 14:29:28 INFO oo_spawn buffer(11/) Found 127.1.244.1:9999 listening port November 14 14:30:58 INFO oo_spawn buffer(11/) CLIENT_MESSAGE: Could not connect to JBoss management interface, skipping deployment verification Using curl -v http://127.1.244.1:8080 and curl -v http://127.1.244.1:9990/ on the node itself provides the expected result. Setting selinux to permissive still results in the same errors, so I don't think that selinux is restricting the network calls from the node itself either. Hitting the external url in the browser works as well.
This is now looking like a firewall issue with my local node (specific to the iptables configuration in our environment). I'm still investigating, but I think this might be closable soon...
This was due to a dns server taking a long time to respond in our environment. And that was due to an iptables restriction. I do not believe that there is a bug here. Closing.