You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2010/09/29 18:55:33 UTC
[jira] Resolved: (QPID-2749) [Java Broker] Add
-XX:+ExplicitGCInvokesConcurrent to qpid-server[.bat]
[ https://issues.apache.org/jira/browse/QPID-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack resolved QPID-2749.
------------------------------------
Resolution: Fixed
Correctly set for bat/bash script
> [Java Broker] Add -XX:+ExplicitGCInvokesConcurrent to qpid-server[.bat]
> -----------------------------------------------------------------------
>
> Key: QPID-2749
> URL: https://issues.apache.org/jira/browse/QPID-2749
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: M2.1, M3, M4, 0.5, 0.6
> Reporter: Rob Godfrey
> Assignee: Andrew Kennedy
> Fix For: 0.7
>
>
> Currently JAVA_GC is set as following in qpid-server
> JAVA_GC="-XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError"
> In the case where an explicit GC is called this can cause significant delay. In order to avoid this the following option should also be supplied
> -XX:+ExplicitGCInvokesConcurrent
> In the case where RMI connections are being made to the JVM, Explicit GCs may be being called periodically (by default every hour) causing significant pauses in processing without this setting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org