User: chirino
Date: 01/10/27 18:27:00
Modified: src/etc/conf/default jbossmq-service.xml
Log:
Commiting my initial implementation of a message cache for the JBossMQ messages.
This should allow the server to scale so it can hold a larger number of message.
Revision Changes Path
1.7 +17 -1 jbossmq/src/etc/conf/default/jbossmq-service.xml
Index: jbossmq-service.xml
===================================================================
RCS file: /cvsroot/jboss/jbossmq/src/etc/conf/default/jbossmq-service.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- jbossmq-service.xml 2001/10/21 05:38:12 1.6
+++ jbossmq-service.xml 2001/10/28 01:27:00 1.7
@@ -7,7 +7,7 @@
<!-- -->
<!-- ===================================================================== -->
-<!-- $Id: jbossmq-service.xml,v 1.6 2001/10/21 05:38:12 chirino Exp $ -->
+<!-- $Id: jbossmq-service.xml,v 1.7 2001/10/28 01:27:00 chirino Exp $ -->
<!--
| This is where you can add and configure your MBeans.
@@ -35,6 +35,22 @@
<mbean code="org.jboss.mq.server.JBossMQService"
name="JBossMQ:service=Server"/>
+
+ <!--
+ | The MessageCache decides where to put JBossMQ message that
+ | are sitting around waiting to be consumed by a client.
+ |
+ | The memory marks are in Megabytes. Once the JVM memory usage hits
+ | the high memory mark, the old messages in the cache will start getting
+ | stored in the DataDirectory. As memory usage gets closer to the
+ | Max memory mark, the amount of message kept in the memory cache aproaches 0.
+ -->
+ <mbean code="org.jboss.mq.server.MessageCache"
+ name="JBossMQ:service=MessageCache">
+ <attribute name="HighMemoryMark">500</attribute>
+ <attribute name="MaxMemoryMark">600</attribute>
+ <attribute name="DataDirectory">tmp/jbossmq</attribute>
+ </mbean>
<!--
| The StateManager is used to keep JMS perisitent state data.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
