[jboss-user] [JBoss Messaging] - Re: Jboss Messaging How To
ataylor
do-not-reply at jboss.com
Mon Apr 21 10:02:47 EDT 2008
looks like the docs are out of date, the clientid is now set via a constructor.
I would start with a simple connection factory like:
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=ConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=bisocket</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <attribute name="JNDIBindings">
| <bindings>
| <binding>/ConnectionFactory</binding>
| <binding>/XAConnectionFactory</binding>
| <binding>java:/ConnectionFactory</binding>
| <binding>java:/XAConnectionFactory</binding>
| </bindings>
| </attribute>
| </mbean>
here are all the configurable attributes
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
| name="jboss.messaging.connectionfactory:service=MyExampleConnectionFactory"
| xmbean-dd="xmdesc/ConnectionFactory-xmbean.xml">
|
| <constructor>
|
| <!- - You can specify the default Client ID to use for connections created using this factory - ->
|
| <arg type="java.lang.String" value="MyClientID"/>
|
| </constructor>
|
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
|
| <!- - The transport to use - can be bisocket, sslbisocket or http - ->
|
| <depends optional-attribute-name="Connector">jboss.messaging:service=Connector,transport=http</depends>
|
| <depends>jboss.messaging:service=PostOffice</depends>
|
| <!- - PrefetchSize determines the approximate maximum number of messages the client consumer will buffer locally - ->
|
| <attribute name="PrefetchSize">150</attribute>
|
| <!- - Paging params to be used for temporary queues - ->
|
| <attribute name="DefaultTempQueueFullSize">200000</attribute>
|
| <attribute name="DefaultTempQueuePageSizeSize">2000</attribute>
|
| <attribute name="DefaultTempQueueDownCacheSize">2000</attribute>
|
| <!- - The batch size to use when using the DUPS_OK_ACKNOWLEDGE acknowledgement mode - ->
|
| <attribute name="DupsOKBatchSize">5000</attribute>
|
| <!- - Does this connection factory support automatic failover? - ->
|
| <attribute name="SupportsFailover">false</attribute>
|
| <!- - Does this connection factory support automatic client side load balancing? - ->
|
| <attribute name="SupportsLoadBalancing">false</attribute>
|
| <!- - 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">true</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">
|
| <bindings>
|
| <binding>/acme/MyExampleConnectionFactory</binding>
|
| <binding>/acme/MyExampleConnectionFactoryDupe</binding>
|
| <binding>java:/xyz/CF1</binding>
|
| <binding>java:/connectionfactories/acme/connection_factory</binding>
|
| </bindings>
|
| </attribute>
|
| </mbean>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145522#4145522
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4145522
More information about the jboss-user
mailing list