[JBoss JIRA] Created: (JGRP-1180) OutOfMemoryError
by Peter Kormos (JIRA)
OutOfMemoryError
----------------
Key: JGRP-1180
URL: https://jira.jboss.org/jira/browse/JGRP-1180
Project: JGroups
Issue Type: Bug
Affects Versions: 2.8
Environment: 2.8.0.GA
Reporter: Peter Kormos
Assignee: Bela Ban
Hi Guys,
I wrote a simple program.
public testbed() throws Exception
{
JChannel channel = new JChannel();
channel.connect("channelName");
for (int i = 0; i < 100000000; i++)
{
Message msg = new Message(
null,
null,
"Test");
channel.send(msg);
// Thread.sleep(10);
if (i % 1000 == 0)
System.out.print(".");
}
}
When I run it with
java -Xmx8m -XX:+HeapDumpOnOutOfMemoryError -cp .;jgroups-all.jar testbed
not always, but quite often it dies with OutOfMemoryError
When I look at the heap dump with jhat, for "Instance Counts" it tells me
22036 instances of class org.jgroups.Message
22036 instances of class org.jgroups.protocols.pbcast.NakAckHeader
22036 instances of class org.jgroups.util.Headers
21316 instances of class org.jgroups.Event
21314 instances of class org.jgroups.util.Queue$Element
304 instances of class org.jgroups.util.UUID
Why are there so many message objects stuck in memory?
java org.jgroups.Version prints
Version: 2.8.0.GA
CVS: $Id: Version.java,v 1.81 2009/12/01 10:31:13 belaban Exp $
I'm using Windows Xp with 1.6 JDK
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBAS-4383) Allow a different JSF implementation to be packaged in the WAR
by Stan Silvert (JIRA)
Allow a different JSF implementation to be packaged in the WAR
--------------------------------------------------------------
Key: JBAS-4383
URL: http://jira.jboss.com/jira/browse/JBAS-4383
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JavaServerFaces
Affects Versions: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta2
Reporter: Stan Silvert
Assigned To: Stan Silvert
Fix For: JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta3, JBossAS-5.0.0.GA
Prior to JEE5, most developers would bundle a JSF implementation such as MyFaces with the WAR. With AS 4.2 and 5.0, you should instead rely on the JSF implementation that ships with the container.
However, for these legacy applications that rely on a particular implementation, we can disable the built-in JSF implementation as long as you stick with the default classloader settings. To disable the built-in JSF, you will add this to your web.xml:
<context-param>
<param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
<param-value>true</param-value>
</context-param>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months