-
1. Re: jnp url configuration wirh rhq agent
lkrejci Feb 29, 2012 5:19 AM (in response to akashk)RHQ agent reads the JNP URL from $JBOSS_EAP_HOME/server/<ACTIVE_CONFIGURATION>/data/jnp-service.url. Note that this is not a configuration file but a file JBoss EAP creates while starting up. This was done to ease the problem of finding the correct values in the AS configuration files for the management software like RHQ.
So in another words, I'm sorry that I don't know the answer to your question, but this is more of a question for JBoss AS guys.
-
2. Re: jnp url configuration wirh rhq agent
lkrejci Feb 29, 2012 5:23 AM (in response to lkrejci)Btw. this might be related... https://community.jboss.org/thread/152432
-
3. Re: jnp url configuration wirh rhq agent
ips Feb 29, 2012 2:33 PM (in response to lkrejci)I think we could workaround the JBAS bug in cases where the IPv6 address can be converted to an IPv4 address, e.g.:
String jnpHost = jnpUri.getHost(); String normalizedJnpHost = jnpHost; InetAddress ipAddress = IntetAddress.getByName(jnpHost); if (ipAddress instanceof Inet6Address) { Inet6Address ipv6Address = (Inet6Address)ipAddress; if (ipv6Address.isIPv4CompatibleAddress()) { if (ipv6Address.isLoopbackAddress()) { normalizedJnpHost = "127.0.0.1"; } else { byte[] ipv6Bytes = ipv6Address.getAddress(); byte[] ipv4Bytes = Arrays.copyOfRange(ipv6Bytes, 12, 16); InetAddress ipv4Address = InetAddress.getByAddress(ipv4Bytes); normalizedJnpHost = ipv4Address.toString(); } } } String normalizedJnpUri = "jnp://" + normalizedJnpHost + ":" + jnpUri.getPort();
I'll create a BZ for this.
-
4. Re: jnp url configuration wirh rhq agent
pilhuhn May 22, 2012 2:47 PM (in response to akashk)There seems to be a general issue with the JVM and handling IPv4 / IPv6 connections.
Sun bug parade has an open bug that says a JVM can not do both at a time.
Some fiddling around recently showed that there is an issue, but it turned out after more fiddling that in fact the JVM can do both simultaneously and that the Sun bug may be invalid.
It turned out for me that the preferIPv4 flag was the bad guy. See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=822218 and https://fedorahosted.org/pipermail/rhq-devel/2012-May/001812.html