|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
Messaging Connection Factories deployment descriptor.
$Id: connection-factories-service.xml 6916 2007-12-05 17:53:00Z pmuir $
-->
<server>
<!-- The default connection factory does not support automatic failover or load balancing-
this is so we can maintain compatiblity with applications written for JBoss MQ which use this
connection factory.
-->
<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>
<!-- A clustered connection factory that supports automatic failover and load balancing of created
connections.
This factory is not suitable to be used by MDBs.
-->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ClusteredConnectionFactory"
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>/ClusteredConnectionFactory</binding>
<binding>/ClusteredXAConnectionFactory</binding>
<binding>java:/ClusteredConnectionFactory</binding>
<binding>java:/ClusteredXAConnectionFactory</binding>
</bindings>
</attribute>
<attribute name="SupportsFailover">true</attribute>
<attribute name="SupportsLoadBalancing">true</attribute>
</mbean>
<!-- A connection factory with no JNDI bindings that is used in clustering to create the connections that
pull messages from one node to another
-->
<mbean code="org.jboss.jms.server.connectionfactory.ConnectionFactory"
name="jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory"
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="SupportsFailover">false</attribute>
<attribute name="SupportsLoadBalancing">false</attribute>
</mbean>
<!-- An example connection factory with all attributes shown
<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">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">
<bindings>
<binding>/acme/MyExampleConnectionFactory</binding>
<binding>/acme/MyExampleConnectionFactoryDupe</binding>
<binding>java:/xyz/CF1</binding>
<binding>java:/connectionfactories/acme/connection_factory</binding>
</bindings>
</attribute>
</mbean>
-->
</server>
|