Hide Forgot
Start an AS 4 with binding to 1 address on an interface, take it into inventory. Later when everything is green, shut down the AS, bind it to a different IP (with -b) and start it again. See that it stays red and no new AS is discovered. Then go to its connection properties on the inventory tab and change its IP to the new one. The server should green again. Now check for downed resources and find its connectors (8080 / 8009) being down and two new connectors for the same ports but different IP showing up. The connectors should detect the IP change by looking at the grand parent (=AS) port and change the accrodingly, and not create new resources.
Same applies to the AS5 plugin
ips, how would you go about fixing this?
*** Bug 606641 has been marked as a duplicate of this bug. ***
The default JBossWeb server.xml file contains the following: <Connector protocol="HTTP/1.1" port="${jboss.web.http.port}" address="${jboss.bind.address}" connectionTimeout="20000" redirectPort="${jboss.web.https.port}" /> so by default the connector address is the same as the app server's bind address, but this is not necessarily always the case. The connector's address is part of the connector Resource's Resource key, and even once we've added support for Resource key upgrades, I don't think we should change this. If users want to avoid such issues, they could probably bind the app server to a hostname, rather than an IP address.