The JBossTS 4.9.0 approach for obtaining a process id via a socket assumes that different AS instances running on the same machine use different ServiceBindingManager port sets. This is an incorrect assumption and prevents multiple AS's bound to different IP addresses from starting.

This JIRA is to add a temporary workaround to allow JBossTS to use a range of ports instead of a fixed port. See forum thread. I'll file a separate JIRA to implement a better fix.

In the AS/EAP 5 series JBossTS used a hard coded ephemeral port for this. So a port range is not a regression; it's actually a bit more locked down. But still, not ideal.