[jboss-cvs] JBossAS SVN: r66632 - in branches/JBPAPP_4_2_0_GA_CP: messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Oct 31 16:55:56 EDT 2007
Author: clebert.suconic at jboss.com
Date: 2007-10-31 16:55:55 -0400 (Wed, 31 Oct 2007)
New Revision: 66632
Modified:
branches/JBPAPP_4_2_0_GA_CP/build/build-thirdparty.xml
branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/connection-factories-service.xml
branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/messaging-service.xml
branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml
Log:
Update jboss-messaging to 1.4.0.SP1 (library and resources)
Modified: branches/JBPAPP_4_2_0_GA_CP/build/build-thirdparty.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/build/build-thirdparty.xml 2007-10-31 20:35:26 UTC (rev 66631)
+++ branches/JBPAPP_4_2_0_GA_CP/build/build-thirdparty.xml 2007-10-31 20:55:55 UTC (rev 66632)
@@ -122,7 +122,7 @@
<componentref name="trove" version="1.0.2-brew"/>
<componentref name="woodstox" version="3.1.1-brew"/>
<componentref name="xdoclet" version="1.2.3-brew"/>
- <componentref name="jboss/messaging" version="snapshot"/>
+ <componentref name="jboss/messaging" version="1.4.0.SP1-brew"/>
</build>
<synchronizeinfo/>
Modified: branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/connection-factories-service.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/connection-factories-service.xml 2007-10-31 20:35:26 UTC (rev 66631)
+++ branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/connection-factories-service.xml 2007-10-31 20:55:55 UTC (rev 66632)
@@ -3,7 +3,7 @@
<!--
Messaging Connection Factories deployment descriptor.
- $Id$
+ $Id: connection-factories-service.xml 3201 2007-10-19 10:39:50Z timfox $
-->
<server>
@@ -115,7 +115,15 @@
<!- - The class name of the factory used to create the load balancing policy to use on the client side - ->
<attribute name="LoadBalancingFactory">org.jboss.jms.client.plugin.RoundRobinLoadBalancingFactory</attribute>
+
+ <!- - Whether we should be strict TCK compliant, i.e. how we deal with foreign messages, defaults to false- ->
+
+ <attribute name="StrictTck">false</attribute>
+ <!- - Disable JBoss Remoting Connector sanity checks - There is rarely a good reason to set this to true - ->
+
+ <attribute name="DisableRemotingChecks">false</attribute>
+
<!- - The connection factory will be bound in the following places in JNDI - ->
<attribute name="JNDIBindings">
Modified: branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/messaging-service.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/messaging-service.xml 2007-10-31 20:35:26 UTC (rev 66631)
+++ branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/messaging-service.xml 2007-10-31 20:55:55 UTC (rev 66632)
@@ -3,7 +3,7 @@
<!--
The JBoss Messaging service deployment descriptor.
- $Id$
+ $Id: messaging-service.xml 3204 2007-10-19 12:42:17Z timfox $
-->
<server>
@@ -83,7 +83,7 @@
<!-- Use XA when pulling persistent messages from a remote node to this one. -->
- <attribute name="UseXAForMessagePull">true</attribute>
+ <attribute name="UseXAForMessagePull">false</attribute>
<!-- When redistributing messages in the cluster. Do we need to preserve the order of messages received
by a particular consumer from a particular producer? -->
@@ -93,6 +93,11 @@
<!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
<attribute name="RecoverDeliveriesTimeout">300000</attribute>
+
+ <!-- The password used by the message sucker connections to create connections.
+ THIS SHOULD ALWAYS BE CHANGED AT INSTALL TIME TO SECURE SYSTEM
+ <attribute name="SuckerPassword"></attribute>
+ -->
<depends optional-attribute-name="PersistenceManager">jboss.messaging:service=PersistenceManager</depends>
Modified: branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml
===================================================================
--- branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml 2007-10-31 20:35:26 UTC (rev 66631)
+++ branches/JBPAPP_4_2_0_GA_CP/messaging/src/etc/server-jbm/default/deploy/jboss-messaging.sar/remoting-bisocket-service.xml 2007-10-31 20:55:55 UTC (rev 66632)
@@ -3,7 +3,7 @@
<!--
Standard bisocket-based Remoting service deployment descriptor.
- $Id$
+ $Id: remoting-bisocket-service.xml 3237 2007-10-21 15:27:51Z timfox $
-->
<server>
@@ -17,6 +17,9 @@
<attribute name="Configuration">
<config>
<invoker transport="bisocket">
+
+ <!-- There should be no reason to change these parameters - warning!
+ Changing them may stop JBoss Messaging working correctly -->
<attribute name="marshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="unmarshaller" isParam="true">org.jboss.jms.wireformat.JMSWireFormat</attribute>
<attribute name="dataType" isParam="true">jms</attribute>
@@ -24,12 +27,30 @@
<attribute name="timeout" isParam="true">0</attribute>
<attribute name="serverBindAddress">${jboss.bind.address}</attribute>
<attribute name="serverBindPort">4457</attribute>
- <attribute name="leasePeriod">10000</attribute>
<attribute name="clientSocketClass" isParam="true">org.jboss.jms.client.remoting.ClientSocketWrapper</attribute>
- <attribute name="serverSocketClass" isParam="true">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
- <attribute name="numberOfRetries" isParam="true">1</attribute>
+ <attribute name="serverSocketClass">org.jboss.jms.server.remoting.ServerSocketWrapper</attribute>
<attribute name="numberOfCallRetries" isParam="true">1</attribute>
- <attribute name="clientMaxPoolSize" isParam="true">50</attribute>
+ <attribute name="pingFrequency" isParam="true">214748364</attribute>
+ <attribute name="pingWindowFactor" isParam="true">10</attribute>
+ <attribute name="onewayThreadPool">org.jboss.jms.server.remoting.DirectThreadPool</attribute>
+ <!-- End immutable parameters -->
+
+ <!-- Periodicity of client pings. Server window by default is twice this figure -->
+ <attribute name="clientLeasePeriod" isParam="true">10000</attribute>
+
+ <!-- Number of seconds to wait for a connection in the client pool to become free -->
+ <attribute name="numberOfRetries" isParam="true">10</attribute>
+
+ <!-- Max Number of connections in client pool. This should be significantly higher than
+ the max number of sessions/consumers you expect -->
+ <attribute name="clientMaxPoolSize" isParam="true">200</attribute>
+
+ <!-- Use these parameters to specify values for binding and connecting control connections to
+ work with your firewall/NAT configuration
+ <attribute name="secondaryBindPort">xyz</attribute>
+ <attribute name="secondaryConnectPort">abc</attribute>
+ -->
+
</invoker>
<handlers>
<handler subsystem="JMS">org.jboss.jms.server.remoting.JMSServerInvocationHandler</handler>
More information about the jboss-cvs-commits
mailing list