[master 6002385] fixes this. The fix was to call setReadTimeout(1000) on the HTTP URL connection. It appears that for a non-responding URL, in the Sun JDK, the call to connect() would fail and so our setConnectTimeout(3000) sufficed, but, in the JRockit JDK, the call to connect() would succeed and then the call to getResponseCode() would hang because no read timeout was specified.
To test this, start an Agent with JRockit 1.6 and inventory an Apache server. Bring one or more of the Apache vhosts down then run the "discovery -f" and "avail" commands from the Agent prompt and make sure neither command hangs. Do the same with Agent on the Sun JVM to make sure it works there too.
not explicitly supported. not going to verify this at this time.