[JBoss JIRA] Created: (JBCACHE-715) Invalidation fails with region based marshalling enabled
by Brian Stansberry (JIRA)
Invalidation fails with region based marshalling enabled
--------------------------------------------------------
Key: JBCACHE-715
URL: http://jira.jboss.com/jira/browse/JBCACHE-715
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.4.0, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0
Reporter: Brian Stansberry
Assigned To: Manik Surtani
Fix For: 1.4.0.SP1
Invalidation requires making a remote _evict command. This fails with region-based marshalling enabled because TreeCacheMarshaller140 doesn't know how to extract the Fqn from the evict methods.
A simple fix is to include the evict methods in MethodDeclarations.crud_methods. If for some reason that's no good, the methods can be specially handled in TreeCacheMarshaller140.extractFqnAsString()
--
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
18 years, 2 months
[JBoss JIRA] Created: (JBAS-3439) DelegatingPolicy: another preload required for jrockit
by Ralph Apel (JIRA)
DelegatingPolicy: another preload required for jrockit
------------------------------------------------------
Key: JBAS-3439
URL: http://jira.jboss.com/jira/browse/JBAS-3439
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ClassLoading
Affects Versions: JBossAS-4.0.4.GA
Environment: # java -version
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
BEA JRockit(R) (build R26.4.0-63-63688-1.5.0_06-20060626-2259-linux-ia32, )
Reporter: Ralph Apel
Assigned To: Scott M Stark
org.jboss.security.jacc.DelegatingPolicy already contains certain special actions in its constructor to preload certain classes (see this constructor's extensive comments).
For DelegatingPolicy to work with jrockit and not have all jacc+securitymgr tests failing with
java.lang.NoClassDefFoundError: org/jboss/security/jacc/ContextPolicy
ContextPolicy must also be preloaded within the constructor (just like PolicyContext.class is already).
--
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
18 years, 2 months
[JBoss JIRA] Created: (JBCACHE-709) Out of memory problem
by Sudhakar Pandey (JIRA)
Out of memory problem
---------------------
Key: JBCACHE-709
URL: http://jira.jboss.com/jira/browse/JBCACHE-709
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.2.4SP2
Environment: Windows NT, Ecliplse IDE and Pentium 4 processor.
Reporter: Sudhakar Pandey
Assigned To: Manik Surtani
Priority: Critical
Problem:
~~~~~~~
While running the following testcase after entering 66666 records my system program is getting hang.
Following is the description of program:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am putting some String object in TreeCache, accessing it and then removing it from the cache. I am doing this in a infinite loop.
Following is the eviction policy:
~~~~~~~~~~~~~~~~~~~~~~~
<attribute name="EvictionPolicyConfig">
<config>
<attribute name="wakeUpIntervalSeconds">72000</attribute>
<!-- Cache wide default -->
<region name="/_default_">
<attribute name="maxNodes">500</attribute>
<attribute name="timeToLiveSeconds">180</attribute>
<!-- Maximum time an object is kept in cache regardless of idle time -->
<attribute name="maxAgeSeconds">7200</attribute>
</region>
<!-- yodlee wide default -->
<region name="/com/yodlee">
<attribute name="maxNodes">500</attribute>
<attribute name="timeToLiveSeconds">180</attribute>
<!-- Maximum time an object is kept in cache regardless of idle time -->
<attribute name="maxAgeSeconds">7200</attribute>
</region>
</config>
</attribute>
*IMPORTENT*: If I reduce the 'wakeUpIntervalSeconds' then there is no leak. However, I can reduce this time coz it eats up lots of CPU.
I have attached the Tree Cache Configuration xml file also.
Program:
~~~~~~~
public void testTreeCache(){
TreeCache treeCache;
try {
treeCache = new TreeCache();
treeCache.setCacheMode(TreeCache.LOCAL);
// configure TreeCache
PropertyConfigurator config = new PropertyConfigurator();
config.configure(treeCache, "com/yodlee/core/system/services/cacheservice/TreeCache.xml");
treeCache.startService();
String identifier = "Test/MemoryLeak/";
String key = "key";
String value = "JBoss Cache is a product designed to cache frequently accessed Java objects in order to dramatically improve the performance of e-business applications. By eliminating unnecessary database access, JBoss Cache decreases network traffic and increases the scalability of applications.";
for(int i=0;;i++)
{
System.out.println("Putting key=" + (key +i));
treeCache.put(identifier, key +i, value);
System.out.println(treeCache.get(identifier, key + i));
System.out.println("Removing key=" + (key+i));
treeCache.remove(identifier, key + i);
}
//treeCache.stopService();
} catch (Exception e) {
MessageController.log(JBossCacheServiceImpl.class.getName(), 1,
ExceptionHelper.getExceptionStackTrace(e),
MessageController.FATAL);
throw new CoreException(ExceptionHelper.getExceptionStackTrace(e));
}
}
--
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
18 years, 2 months