[JBoss Messaging] - Re: Exception when starten 2nd node
by mbreuer
"timfox" wrote : "mbreuer" wrote :
| | You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to the clustering section, it also adresses jbossmq.
| |
|
| JBoss 5 is still a beta.
|
| If you used EAP 4.3 you would find the documentation already refers to JBoss Messaging.
|
| Since you are using 4.2 I assume you are not a paying support customer and are relying on free support in this forum.
|
| If you would like to volunteer to "fill the gap" and bring the JBoss AS 5 documentation up to date, I shall create a JIRA task and assign it you?
|
| What's your JIRA user name?
|
| Thanks for offering to help out :)
:o)
You are confusing me! A doc already is existing for 4.3 (just say paying customers). For 4.2 (say non-paying customers) the doc is missing.
In general i could write a doc filling this gap. But this is a hen-egg-problem. How can I get the required information for docs?
Please solve my confusion ...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162808#4162808
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162808
17 years, 9 months
[JBoss Messaging] - testDistributedQueue queue fails by JBoss-messaging-1.4.0.SP
by saho
Hi All,
im using JBoss 4.2.2. and JBoss-messaging-1.4.0.SP3-CP02 with null-perisistence config.
I habe 2 JBoss machines at the same cluster, they have the same groupname and unique ServerPeer ID.
By the first machine start, JBoss starts gracefully.
But when the second machine starts throws the following exception:
| java.lang.IllegalStateException: Channel id map for node 2 already contains binding for queue 12
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBindingInMemory(MessagingPostOffice.java:2380)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.internalAddBinding(MessagingPostOffice.java:1868)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.addBinding(MessagingPostOffice.java:449)
| at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:126)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
| at sun.reflect.GeneratedMethodAccessor22.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at org.jboss.system.ServiceController.start(ServiceController.java:435)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy4.start(Unknown Source)
| at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
|
I habe the following configs:
messaging-servicexml node1
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| The JBoss Messaging service deployment descriptor.
|
| $Id: messaging-service.xml 3881 2008-03-14 16:01:43Z timfox $
| -->
|
| <server>
|
| <!-- ServerPeer MBean configuration
| ============================== -->
|
| <mbean code="org.jboss.jms.server.ServerPeer"
| name="jboss.messaging:service=ServerPeer"
| xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
|
| <!-- The unique id of the server peer - in a cluster each node MUST have a unique value - must be an integer -->
|
| <attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:1}</attribute>
|
| <!-- The default JNDI context to use for queues when they are deployed without specifying one -->
|
| <attribute name="DefaultQueueJNDIContext">/queue</attribute>
|
| <!-- The default JNDI context to use for topics when they are deployed without specifying one -->
|
| <attribute name="DefaultTopicJNDIContext">/topic</attribute>
|
| <attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>
|
| <!-- The JAAS security domain to use for JBoss Messaging -->
|
| <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
|
| <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis -->
|
| <attribute name="DefaultSecurityConfig">
| <security>
| <role name="guest" read="true" write="true" create="true"/>
| </security>
| </attribute>
|
| <!-- The default Dead Letter Queue (DLQ) to use for destinations.
| This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
|
| <!-- The default maximum number of times to attempt delivery of a message before sending to the DLQ (if configured).
| This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultMaxDeliveryAttempts">10</attribute>
|
| <!-- The default Expiry Queue to use for destinations. This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
|
| <!-- The default redelivery delay to impose. This can be overridden on a per destination basis -->
|
| <attribute name="DefaultRedeliveryDelay">0</attribute>
|
| <!-- The periodicity of the message counter manager enquiring on queues for statistics -->
|
| <attribute name="MessageCounterSamplePeriod">5000</attribute>
|
| <!-- The maximum amount of time for a client to wait for failover to start on the server side after
| it has detected failure -->
|
| <attribute name="FailoverStartTimeout">60000</attribute>
|
| <!-- The maximum amount of time for a client to wait for failover to complete on the server side after
| it has detected failure -->
|
| <attribute name="FailoverCompleteTimeout">300000</attribute>
|
| <!-- The maximum number of days results to maintain in the message counter history -->
|
| <attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
|
| <!-- The name of the connection factory to use for creating connections between nodes to pull messages -->
|
| <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</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? -->
|
| <attribute name="DefaultPreserveOrdering">false</attribute>
|
| <!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
|
| <attribute name="RecoverDeliveriesTimeout">300000</attribute>
|
| <!-- Set to true to enable message counters that can be viewed via JMX -->
|
| <attribute name="EnableMessageCounters">false</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>
|
| <depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends>
|
| <depends>jboss.messaging:service=Connector,transport=bisocket</depends>
|
| </mbean>
|
| </server>
|
|
messaging-servicexml node2
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| The JBoss Messaging service deployment descriptor.
|
| $Id: messaging-service.xml 3881 2008-03-14 16:01:43Z timfox $
| -->
|
| <server>
|
| <!-- ServerPeer MBean configuration
| ============================== -->
|
| <mbean code="org.jboss.jms.server.ServerPeer"
| name="jboss.messaging:service=ServerPeer"
| xmbean-dd="xmdesc/ServerPeer-xmbean.xml">
|
| <!-- The unique id of the server peer - in a cluster each node MUST have a unique value - must be an integer -->
|
|
| <attribute name="ServerPeerID">${jboss.messaging.ServerPeerID:2}</attribute>
|
|
| <!-- The default JNDI context to use for queues when they are deployed without specifying one -->
|
| <attribute name="DefaultQueueJNDIContext">/queue</attribute>
|
| <!-- The default JNDI context to use for topics when they are deployed without specifying one -->
|
| <attribute name="DefaultTopicJNDIContext">/topic</attribute>
|
| <attribute name="PostOffice">jboss.messaging:service=PostOffice</attribute>
|
| <!-- The JAAS security domain to use for JBoss Messaging -->
|
| <attribute name="SecurityDomain">java:/jaas/messaging</attribute>
|
| <!-- The default security configuration to apply to destinations - this can be overridden on a per destination basis -->
|
| <attribute name="DefaultSecurityConfig">
| <security>
| <role name="guest" read="true" write="true" create="true"/>
| </security>
| </attribute>
|
| <!-- The default Dead Letter Queue (DLQ) to use for destinations.
| This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultDLQ">jboss.messaging.destination:service=Queue,name=DLQ</attribute>
|
| <!-- The default maximum number of times to attempt delivery of a message before sending to the DLQ (if configured).
| This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultMaxDeliveryAttempts">10</attribute>
|
| <!-- The default Expiry Queue to use for destinations. This can be overridden on a per destinatin basis -->
|
| <attribute name="DefaultExpiryQueue">jboss.messaging.destination:service=Queue,name=ExpiryQueue</attribute>
|
| <!-- The default redelivery delay to impose. This can be overridden on a per destination basis -->
|
| <attribute name="DefaultRedeliveryDelay">0</attribute>
|
| <!-- The periodicity of the message counter manager enquiring on queues for statistics -->
|
| <attribute name="MessageCounterSamplePeriod">5000</attribute>
|
| <!-- The maximum amount of time for a client to wait for failover to start on the server side after
| it has detected failure -->
|
| <attribute name="FailoverStartTimeout">60000</attribute>
|
| <!-- The maximum amount of time for a client to wait for failover to complete on the server side after
| it has detected failure -->
|
| <attribute name="FailoverCompleteTimeout">300000</attribute>
|
| <!-- The maximum number of days results to maintain in the message counter history -->
|
| <attribute name="DefaultMessageCounterHistoryDayLimit">-1</attribute>
|
| <!-- The name of the connection factory to use for creating connections between nodes to pull messages -->
|
| <attribute name="ClusterPullConnectionFactoryName">jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory</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? -->
|
| <attribute name="DefaultPreserveOrdering">false</attribute>
|
| <!-- Max. time to hold previously delivered messages back waiting for clients to reconnect after failover -->
|
| <attribute name="RecoverDeliveriesTimeout">300000</attribute>
|
| <!-- Set to true to enable message counters that can be viewed via JMX -->
|
| <attribute name="EnableMessageCounters">false</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>
|
| <depends optional-attribute-name="JMSUserManager">jboss.messaging:service=JMSUserManager</depends>
|
| <depends>jboss.messaging:service=Connector,transport=bisocket</depends>
|
| </mbean>
|
| </server>
|
|
destination-service.xml
| <?xml version="1.0" encoding="UTF-8"?>
|
| <!--
| Messaging Destinations deployment descriptor.
|
| $Id: destinations-service.xml 1930 2007-01-09 18:16:04Z timfox $
| -->
|
| <server>
|
| <!--
| The Default Dead Letter Queue. This destination is a dependency of an EJB MDB container.
| -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=DLQ"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <!--
| The Default Expiry Queue.
| -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=ExpiryQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <!--
| Example destinations.
| -->
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=testTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="durpublisher" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=securedTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="publisher" read="true" write="true" create="false"/>
| </security>
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=testDurableTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="durpublisher" read="true" write="true" create="true"/>
| </security>
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=testQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="SecurityConfig">
| <security>
| <role name="guest" read="true" write="true"/>
| <role name="publisher" read="true" write="true" create="false"/>
| <role name="noacc" read="false" write="false" create="false"/>
| </security>
| </attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=A"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=B"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=C"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=D"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=ex"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <!-- It's possible for indiviual queues and topics to use a specific queue for
| an expiry or DLQ -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=PrivateDLQ"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
| <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=TopicWithOwnDLQAndExpiryQueue"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
| <attribute name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
| </mbean>
|
| <!-- Queues and Topics can also specify their own redelivery delay -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=QueueWithOwnRedeliveryDelay"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="RedeliveryDelay">5000</attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=TopicWithOwnRedeliveryDelay"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="RedeliveryDelay">5000</attribute>
| </mbean>
|
| <!--
| Example clustered destinations.
| -->
|
| <mbean code="org.jboss.jms.server.destination.QueueService"
| name="jboss.messaging.destination:service=Queue,name=testDistributedQueue"
| xmbean-dd="xmdesc/Queue-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="Clustered">true</attribute>
| </mbean>
|
| <mbean code="org.jboss.jms.server.destination.TopicService"
| name="jboss.messaging.destination:service=Topic,name=testDistributedTopic"
| xmbean-dd="xmdesc/Topic-xmbean.xml">
| <depends optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
| <depends>jboss.messaging:service=PostOffice</depends>
| <attribute name="Clustered">true</attribute>
| </mbean>
|
| </server>
|
Thanks for any help
Regards
Saho
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162796#4162796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162796
17 years, 9 months
[JBoss Messaging] - Re: Exception when starten 2nd node
by mbreuer
"timfox" wrote : "mbreuer" wrote :
| | The app server 4.2.2 docs don't describe how jms works with new messaging. Even there's a note, that future revision will use new jboss messaging. Also it notes that messaging will work completely different from jbossmq.
| |
|
| What do you expect ?
|
I expect a manual describing how new jboss messaging(jms) works with as.
You are right, jbossas 4.2.2 comes with jbossmq, so it does not reference jboss messaging. But newer manuals (5.0.0 beta) have no changes to the clustering section, it also adresses jbossmq.
As ataylor described, the jboss messaging developers are not responsible for the integration into jbossas. So I will start a post to that forum.
anonymous wrote :
| Have you read the user guide?
|
| Hint: Go to jboss.org and follow the links.
|
JBoss Messaging Users Guide? Yes, i read it but is does not fill the gap between messaging and as.
JBossAS Users guide? Yes, but it adresses JBossMQ. (4.2.2) The "Clustering Guide" link to as 5.0.0 is not acessible, the configuration guide link is accepted, but the "newer" doc is unchanged in the clustering section. :(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162790#4162790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162790
17 years, 9 months
Delivery Status Notification (Failure)
by postmaster＠lists.jboss.org
This is an automatically generated Delivery Status Notification.
Delivery to the following recipients failed.
hr@localhost
17 years, 9 months
