[JBoss JIRA] (JGRP-1413) Pass bundled messages up together as MSG_BUNDLE event
by Bela Ban (JIRA)
Bela Ban created JGRP-1413:
------------------------------
Summary: Pass bundled messages up together as MSG_BUNDLE event
Key: JGRP-1413
URL: https://issues.jboss.org/browse/JGRP-1413
Project: JGroups
Issue Type: Enhancement
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.1
When we receive a message bundle, e.g. 10 (multicast or unicast) messages at the transport (if bundling is enabled), then we currently pass each message up separately:
List<Message> list;
for(Message msg: list)
up_prot.up(new Event(Event.MSG, msg));
NAKACK then adds every message and calls removeMany() after that. Both the addition and the removal acquire locks, plus, most of the time - removeMany() will only remove 1 message !
It would be better to send the message bundle (in the example above, consisting of 10 messages) up as *one* event, e.g:
List<Message> list;
up_prot.up(new Event(Event.MSG_BUNDLE, list));
NAKACK, NAKACK2, UNICAST and UNICAST2 would have to handle this new event type.
For example, NAKACK2 would call a (new) method RingBuffer.addAndRemoveMany(), which adds all 10 messages and removes N messages using the same lock, ie. lock acquisition would be done only once !
Above the reliable retransmission protocols (currently NAKACK, NAKACK2, UNICAST and UNICAST2), messages would be passed up one-by-one. Later, we might look into whether it makes sense to pass up message bundles *above* the reliable retransmission protocols...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3732) sun.net.www.http.KeepAliveCache preventing classloader from being garbage collected
by Philippe Guinot (JIRA)
Philippe Guinot created AS7-3732:
------------------------------------
Summary: sun.net.www.http.KeepAliveCache preventing classloader from being garbage collected
Key: AS7-3732
URL: https://issues.jboss.org/browse/AS7-3732
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.CR1b
Environment: AS 7 running on JDK 1.6.0_30, Windows 7
Reporter: Philippe Guinot
Assignee: Remy Maucherat
This is related to Tomcat issue 49230: https://issues.apache.org/bugzilla/show_bug.cgi?id=49230
{quote}When a servlet creates a URLConnection, internally this is done us-ing
sun.net.www.http.HttpClient. To have the ability to keep connections alive and
close them after a certain time they are placed inside a cache. A static
reference is kept to this cache (sun.net.www.http.KeepAliveCache).{quote}
This cache contains a non-final reference to a Thread which keeps a reference to the Application's ClassLoader, hence a Class Loader leak.
The Tomcat patch won't work because the reference to the Thread is non-final and so a new thread maybe created during the application's lifecycle, far after the startup.
I don't have any solution to this issue, I'm afraid. The only workaround I've found is to run this code during the shutdown of my application. This is very ugly though:
{code}
final KeepAliveCache keepAliveCache = new HttpClient() {
public KeepAliveCache getKeepAliveCache() {
return kac;
}
}.getKeepAliveCache();
final Field f = KeepAliveCache.class.getDeclaredField("keepAliveTimer");
f.setAccessible(true);
f.set(keepAliveCache, null);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3449) IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3449?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek commented on AS7-3449:
-------------------------------------
I've tried this proposed config change and it seems on DR12 it resolves this issue - DR12 booted correctly (= without exception, still some bad default binding found). So for now I think this my primary observation is resolved, further investigation/testing will be done in 3rd party interaction round.
> IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
> -----------------------------------------------------------------------------
>
> Key: AS7-3449
> URL: https://issues.jboss.org/browse/AS7-3449
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.CR1b
> Environment: Linux
> Reporter: Pavel Janousek
> Assignee: Pavel Janousek
> Priority: Blocker
>
> I unpacked DR5 build ZIP only, didn't touch configuration and try to run as usual:
> {code}
> cd <bin dir of EAP>
> ./standalone.sh
> {code}
> Got this result:
> {code}
> [root@fedora15-vrt1 bin]# ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/pjanouse/tmp/jboss-eap-6.0.0.Alpha2
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:55:46,040 INFO [org.jboss.modules] JBoss Modules version 1.0.3.GA
> 16:55:47,253 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
> 16:55:47,362 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) starting
> 16:55:48,163 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) stopped in 3ms
> 16:55:48,156 ERROR [org.jboss.as.controller.AbstractControllerService] Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:139) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:168) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:197) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:133) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 1 more
> Caused by: java.lang.RuntimeException: Unable to determine a default name based on the local host name
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:188) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:263) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:82) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 4 more
> Caused by: java.net.UnknownHostException: fedora15-vrt1: fedora15-vrt1
> at java.net.InetAddress.getLocalHost(InetAddress.java:1426) [:1.6.0_22]
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:186) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 10 more
> [root@fedora15-vrt1 bin]#
> {code}
> The root of this issue is that *fedora15-vrt1* can't be translated to IPv4 IP address, but only to IPv6 address:
> {code}
> [root@fedora15-vrt1 bin]# ping fedora15-vrt1
> ping: unknown host fedora15-vrt1
> [root@fedora15-vrt1 bin]# ping6 fedora15-vrt1
> PING fedora15-vrt1(vrt1-ip6) 56 data bytes
> 64 bytes from vrt1-ip6: icmp_seq=1 ttl=64 time=0.067 ms
> 64 bytes from vrt1-ip6: icmp_seq=2 ttl=64 time=0.105 ms
> ^C
> --- fedora15-vrt1 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.067/0.086/0.105/0.019 ms
> [root@fedora15-vrt1 bin]#
> {code}
> because I really config /etc/hosts like:
> {code}
> [root@fedora15-vrt1 bin]# cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> ::1 localhost6.localdomain6 localhost6
> 10.0.2.15 both
> ::ffff:10.0.2.15 both
> 1:0:0:1::10 vrt1-ip6 fedora15-vrt1
> 1:0:0:1::11 vrt2-ip6
> [root@fedora15-vrt1 bin]#
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months
[JBoss JIRA] (AS7-3449) IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
by Pavel Janousek (JIRA)
[ https://issues.jboss.org/browse/AS7-3449?page=com.atlassian.jira.plugin.s... ]
Pavel Janousek closed AS7-3449.
-------------------------------
Resolution: Done
Primary observation resolved, so closing...
> IPv6: Unable to start EAP when hostname isn't available in IPv4 address space
> -----------------------------------------------------------------------------
>
> Key: AS7-3449
> URL: https://issues.jboss.org/browse/AS7-3449
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.CR1b
> Environment: Linux
> Reporter: Pavel Janousek
> Assignee: Pavel Janousek
> Priority: Blocker
>
> I unpacked DR5 build ZIP only, didn't touch configuration and try to run as usual:
> {code}
> cd <bin dir of EAP>
> ./standalone.sh
> {code}
> Got this result:
> {code}
> [root@fedora15-vrt1 bin]# ./standalone.sh
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /home/pjanouse/tmp/jboss-eap-6.0.0.Alpha2
> JAVA: java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:55:46,040 INFO [org.jboss.modules] JBoss Modules version 1.0.3.GA
> 16:55:47,253 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA
> 16:55:47,362 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) starting
> 16:55:48,163 INFO [org.jboss.as] JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.Alpha1-redhat-1) stopped in 3ms
> 16:55:48,156 ERROR [org.jboss.as.controller.AbstractControllerService] Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:139) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at java.lang.Thread.run(Thread.java:679) [:1.6.0_22]
> Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:168) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.server.ServerService.boot(ServerService.java:197) [jboss-as-server-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:133) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 1 more
> Caused by: java.lang.RuntimeException: Unable to determine a default name based on the local host name
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:188) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:263) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:82) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59) [staxmapper-1.0.0.Final-redhat-1.jar:1.0.0.Final-redhat-1]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:117) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 4 more
> Caused by: java.net.UnknownHostException: fedora15-vrt1: fedora15-vrt1
> at java.net.InetAddress.getLocalHost(InetAddress.java:1426) [:1.6.0_22]
> at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:186) [jboss-as-controller-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
> ... 10 more
> [root@fedora15-vrt1 bin]#
> {code}
> The root of this issue is that *fedora15-vrt1* can't be translated to IPv4 IP address, but only to IPv6 address:
> {code}
> [root@fedora15-vrt1 bin]# ping fedora15-vrt1
> ping: unknown host fedora15-vrt1
> [root@fedora15-vrt1 bin]# ping6 fedora15-vrt1
> PING fedora15-vrt1(vrt1-ip6) 56 data bytes
> 64 bytes from vrt1-ip6: icmp_seq=1 ttl=64 time=0.067 ms
> 64 bytes from vrt1-ip6: icmp_seq=2 ttl=64 time=0.105 ms
> ^C
> --- fedora15-vrt1 ping statistics ---
> 2 packets transmitted, 2 received, 0% packet loss, time 999ms
> rtt min/avg/max/mdev = 0.067/0.086/0.105/0.019 ms
> [root@fedora15-vrt1 bin]#
> {code}
> because I really config /etc/hosts like:
> {code}
> [root@fedora15-vrt1 bin]# cat /etc/hosts
> 127.0.0.1 localhost.localdomain localhost
> ::1 localhost6.localdomain6 localhost6
> 10.0.2.15 both
> ::ffff:10.0.2.15 both
> 1:0:0:1::10 vrt1-ip6 fedora15-vrt1
> 1:0:0:1::11 vrt2-ip6
> [root@fedora15-vrt1 bin]#
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months