Red Hat Bugzilla – Bug 613069
EAP or SOA-P 5 when started without -c is defined with wrong config, and when started without -b is defined with wrong bind address
Last modified: 2015-02-01 18:26:27 EST
See https://jira.jboss.org/browse/JOPR-419 for details
I have started EAP5.0 GA and EAP 5.1 without params and both were discovered with server name Default and bind address 127.0.0.1.
Tested also on SOA-5 and I can not reproduce the bug.
QA Closing -- I am also not seeing this occur. I start it with no params and it gets properly discovered as Default profile, bind 127.0.0.1