[JBoss JIRA] Created: (JGRP-587) Lightweight FLUSH for state transfer
by Vladimir Blagojevic (JIRA)
Lightweight FLUSH for state transfer
------------------------------------
Key: JGRP-587
URL: http://jira.jboss.com/jira/browse/JGRP-587
Project: JGroups
Issue Type: Feature Request
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Fix For: 2.7
We should investigate introduction of lightweight FLUSH in Multiplexer. Lightweight FLUSH would introduce stop-the-world model to only specific mux application leaving other mux applications unaffected. For example, if there are three mux applications A,B, and C and we need to FLUSH only application C, lightweight FLUSH would block all message sending for C only while applications A and B are unaffected.
--
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
16 years, 1 month
[JBoss JIRA] Created: (JGRP-520) OOM with RpcDispatcher
by Bela Ban (JIRA)
OOM with RpcDispatcher
----------------------
Key: JGRP-520
URL: http://jira.jboss.com/jira/browse/JGRP-520
Project: JGroups
Issue Type: Bug
Environment: 1.5.0_10-b03;Sun Microsystems Inc.;mixed mode, sharing;Windows;32 bit JVM
Windows Server 2003 Standard x64
Reporter: Bela Ban
Assigned To: Bela Ban
Priority: Critical
Fix For: 2.5
Attachments: SimpleClusterManager.java
[from Patrick Eger]
Attempting to isolate the problem, I ran into a (probably unrelated)
other OutOfMemoryError problem with JGroups 1.5b2. Got an
OutOfMemoryError after ~3 minutes of running the attached
TestJGroups.java, 3 instances in parallel. Also attached is the stack
config and a couple YJP views of the HPROF dump as generated by
-XX:+HeapDumpOnOutOfMemoryError.
The test is looping single-threaded, calling a remote method via
RpcDispatcher every 100 ms which returns a few KB String. Looks like all
the memory is retained instances of org.jgroups.stack.IpAddress
(~1,000,000 for a ~3 minute run (seems like a lot?)), held by
pbcast.NAKACK.sent_msgs. I have the HPROF dump if you need, its about 15
megs zipped so I assumed would not make it through the mail filters.
Is this a real OOME or is it a stack configuration/tuning thing? I have
used the default UDP config, but with increased thread_pool and
oob_thread_pool sizes.
Options
-----------------------------------------
-agentlib:yjpagent
-server
-Xmx64m
-XX:+HeapDumpOnOutOfMemoryError
-Dcom.sun.management.jmxremote
-Dpeer_cluster_manager.XXXTestClusterXXX.jgroups_config=C:\tmp\testcfg.x
ml
--
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
16 years, 1 month
[JBoss JIRA] Created: (JBAS-4307) Tag file: Variables from outer tags are not available in inner tags
by Wolfgang Knauf (JIRA)
Tag file: Variables from outer tags are not available in inner tags
-------------------------------------------------------------------
Key: JBAS-4307
URL: http://jira.jboss.com/jira/browse/JBAS-4307
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Affects Versions: JBossAS-4.2.0.CR1
Reporter: Wolfgang Knauf
Assigned To: Remy Maucherat
I created two tag files ("outer" and "inner"), in the jsp "inner" is a nested tag of "outer".
In the outer tag file I declare a variable and write it to the jspContext. This variable is available in the jsp, but not in "inner.tag".
outer.tag
<%@ variable name-given="test" scope="NESTED" %>
<%
jspContext.setAttribute ("test", "This is a test !", PageContext.PAGE_SCOPE);
%>
Value before doBody: ${test} <br>
<jsp:doBody/>
Value after doBody: ${test} <br>
inner.tag:
Value in inner tag: ${test} <br>
test.jsp:
<?xml version="1.0" encoding="ISO-8859-1" ?>
<%@ page language="java" contentType="text/html; charset=ISO-8859-1" pageEncoding="ISO-8859-1"%>
<%@ taglib prefix="test" tagdir="/WEB-INF/tags" %>
<html>
<body>
<test:outer>
Value in test.jsp: ${test} <br>
<test:inner/>
</test:outer>
</body>
</html>
The output is:
Value before doBody: This is a test !
Value in test.jsp: This is a test !
Value in inner tag:
Value after doBody: This is a test !
The inner tag does not see the attribute.
I don't know whether this is a bug or whether the spec forbids this, but I think it should be possible for the inner tag to see the parent variables.
A usage sample would be some iterator tag which places the current item in a jspContext variable and the inner tags must be able to access the current item (the variable name is an attribute of the inner tag). I could place the current item in the request scope, but this is much too global.
--
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
16 years, 1 month