[JBoss JIRA] (JBCACHE-1637) Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
by Nghi Nguyen Van (JIRA)
[ https://issues.jboss.org/browse/JBCACHE-1637?page=com.atlassian.jira.plug... ]
Nghi Nguyen Van updated JBCACHE-1637:
-------------------------------------
Description:
Our application environment have Xmx=3gb. While it is running the used memory is around 90% of the JVM capacity (~2.7GB) including >500MB cached content by Jboss cache. If I want to dump the jboss cached content out of the JVM the application then got OutOfMemoryError.
The problem come from the way JbossCache use JVM memory to response content back to JMX client, it nearly doubled JbossCache used memory: 2.7gb + 500Mb=3.3gb > JVM capacity => OOME
I think that JBossCache should improve by:
# response content back to JMX client continuously
# provide option to write content to an output file
was:
* Our application environment have Xmx=3gb. While it is running the used memory is around 90% of the JVM capacity (~2.7GB) including >500MB cached content by Jboss cache. If I want to dump the jboss cached content out of the JVM the application then got OutOfMemoryError.
The problem come from the way JbossCache use JVM memory to response back to JMX client, it nearly double JbossCache used memory: 2.7gb + 500Mb=3.3gb > JVM capacity.
I think that JBossCache should improve by:
# response content back to JMX client continuously
# provide option to write content to an output file
> Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
> -------------------------------------------------------------------------------------------
>
> Key: JBCACHE-1637
> URL: https://issues.jboss.org/browse/JBCACHE-1637
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: 3.2.5.GA, 3.3.0.GA
> Reporter: Nghi Nguyen Van
> Assignee: Manik Surtani
>
> Our application environment have Xmx=3gb. While it is running the used memory is around 90% of the JVM capacity (~2.7GB) including >500MB cached content by Jboss cache. If I want to dump the jboss cached content out of the JVM the application then got OutOfMemoryError.
> The problem come from the way JbossCache use JVM memory to response content back to JMX client, it nearly doubled JbossCache used memory: 2.7gb + 500Mb=3.3gb > JVM capacity => OOME
> I think that JBossCache should improve by:
> # response content back to JMX client continuously
> # provide option to write content to an output file
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
- 1
- 0
[JBoss JIRA] (JBCACHE-1637) Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
by Nghi Nguyen Van (JIRA)
[ https://issues.jboss.org/browse/JBCACHE-1637?page=com.atlassian.jira.plug... ]
Nghi Nguyen Van updated JBCACHE-1637:
-------------------------------------
Component/s: JMX
> Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
> -------------------------------------------------------------------------------------------
>
> Key: JBCACHE-1637
> URL: https://issues.jboss.org/browse/JBCACHE-1637
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JMX
> Affects Versions: 3.2.5.GA, 3.3.0.GA
> Reporter: Nghi Nguyen Van
> Assignee: Manik Surtani
>
> * Our application environment have Xmx=3gb. While it is running the used memory is around 90% of the JVM capacity (~2.7GB) including >500MB cached content by Jboss cache. If I want to dump the jboss cached content out of the JVM the application then got OutOfMemoryError.
> The problem come from the way JbossCache use JVM memory to response back to JMX client, it nearly double JbossCache used memory: 2.7gb + 500Mb=3.3gb > JVM capacity.
> I think that JBossCache should improve by:
> # response content back to JMX client continuously
> # provide option to write content to an output file
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
- 1
- 0
[JBoss JIRA] (JBCACHE-1637) Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
by Nghi Nguyen Van (JIRA)
Nghi Nguyen Van created JBCACHE-1637:
----------------------------------------
Summary: Jboss Cache DataContainer should allow printDetails write to a file to save JVM memory cost
Key: JBCACHE-1637
URL: https://issues.jboss.org/browse/JBCACHE-1637
Project: JBoss Cache
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.2.5.GA, 3.3.0.GA
Reporter: Nghi Nguyen Van
Assignee: Manik Surtani
* Our application environment have Xmx=3gb. While it is running the used memory is around 90% of the JVM capacity (~2.7GB) including >500MB cached content by Jboss cache. If I want to dump the jboss cached content out of the JVM the application then got OutOfMemoryError.
The problem come from the way JbossCache use JVM memory to response back to JMX client, it nearly double JbossCache used memory: 2.7gb + 500Mb=3.3gb > JVM capacity.
I think that JBossCache should improve by:
# response content back to JMX client continuously
# provide option to write content to an output file
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 5 months
- 1
- 0
- ← Newer
- 1
- Older →