5:30 a.m.
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
5:32 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=all ]
Sudhakar Pandey updated JBCACHE-709:
------------------------------------
Attachment: TreeCache.xml
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
Attachments: TreeCache.xml
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
6 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12339913 ]
Sudhakar Pandey commented on JBCACHE-709:
-----------------------------------------
The problem does not occurs if we dont configure the TreeCache i.e. comment the following
two lines in above program:
// configure TreeCache
//PropertyConfigurator config = new PropertyConfigurator();
//config.configure(treeCache,
"com/yodlee/core/system/services/cacheservice/TreeCache.xml");
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
Attachments: TreeCache.xml
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
11:17 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12339914 ]
Sudhakar Pandey commented on JBCACHE-709:
-----------------------------------------
This is happening in my production system. We are using JbossCache as standalone cache no
clustering.
Memory leak problem doesn't happens if we do not do the configuration (XML file).
Pleae let me know where I am going wrong.
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
Attachments: TreeCache.xml
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
11:52 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12339924 ]
Ben Wang commented on JBCACHE-709:
----------------------------------
Looks like you are using eviction policy but your wakeUpIntervalSecond is setting at 7200
(2 hour). This obviously is a red flag. If you doing it under load, you should set it to
like 1.
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
Attachments: TreeCache.xml
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
10:14 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340001 ]
Sudhakar Pandey commented on JBCACHE-709:
-----------------------------------------
That is true.
But my question is even after properly removing the cached object and the node from the
TreeCache, why memory leak is happening?
And this does not happen if we do not configure the TreeCache. why?
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
Attachments: TreeCache.xml
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
3:24 a.m.
New subject: [JBoss JIRA] Resolved: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=all ]
Ben Wang resolved JBCACHE-709.
------------------------------
Resolution: Rejected
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
Attachments: TreeCache.xml
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
3:24 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340067 ]
Ben Wang commented on JBCACHE-709:
----------------------------------
If you don't configure, cache will use default values of which eviction is off.
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
Attachments: TreeCache.xml
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
3:38 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340068 ]
Sudhakar Pandey commented on JBCACHE-709:
-----------------------------------------
Thanks Ben for your valuable insights.......
I agree with you that when we do not configure, eviction is off. But when we do configure
and remove the cached objects properly from the cache then why memory usage increases.
I hope I am putting my point properly. Ok here I am giving a simple example:
"Suppose the eviction policy is ON and we put Object X in TreeCache and then removed
the Object X from TreeCache. This means, now there is no object present in the cache and
there is nothing to clean. Then why the memory leak is happening?"
Thanks once again.
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
Attachments: TreeCache.xml
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
3:54 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340069 ]
Ben Wang commented on JBCACHE-709:
----------------------------------
Are you sure it is memory leak instead of just GC not kick in yet? If you are certain, can
you attach a junit test case to illustrate this?
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
Attachments: TreeCache.xml
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
4:18 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=all ]
Sudhakar Pandey updated JBCACHE-709:
------------------------------------
Attachment: TestMemoryLeak.java
Hi Ben,
I have attached the JUnit TestCase. I am calling System.gc() after each 1000 node has been
addead and then subsequently removed from the cache.
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
Attachments: TestMemoryLeak.java, TreeCache.xml
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
8:07 p.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340148 ]
Ben Wang commented on JBCACHE-709:
----------------------------------
Based on your config xml, you are still using eviction and the thread wakeup interval is
7200 seconds. This is not going to work. The reason is that before the eviction thread can
kick in to process event, add/remove are counted as a separate event. So naturally, the
event queue will fill up quickly (before it can process it and determine nothing needs to
be done from the eviction side).
You can change it from 7200 to 1 and test it again.
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
Attachments: TestMemoryLeak.java, TreeCache.xml
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
8:11 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340332 ]
Sudhakar Pandey commented on JBCACHE-709:
-----------------------------------------
Thanks alot Ben
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
Attachments: TestMemoryLeak.java, TreeCache.xml
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
7:30 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=all ]
Manik Surtani updated JBCACHE-709:
----------------------------------
Assignee: Ben Wang (was: Manik Surtani)
Guys, can you please discuss this in the forums - JIRA is not the place for this.
Thanks,
Manik
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: Ben Wang
Priority: Critical
Attachments: TestMemoryLeak.java, TreeCache.xml
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
3:01 a.m.
New subject: [JBoss JIRA] Commented: (JBCACHE-709) Out of memory problem
[ http://jira.jboss.com/jira/browse/JBCACHE-709?page=comments#action_12340813 ]
Ben Wang commented on JBCACHE-709:
----------------------------------
Nothing more to be discussed, IMO. This is a non-bug that I have rejected it. I don't
think it is worthwhile to be placed in forum again.
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: Ben Wang
Priority: Critical
Attachments: TestMemoryLeak.java, TreeCache.xml
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
7237
days inactive
7253
days old
14 comments
3 participants
participants (3)
-
Ben Wang (JIRA) -
Manik Surtani (JIRA)
-
Sudhakar Pandey (JIRA)