You have to make the mbean service name attribute unique as well as any
attributes that would conflict with other invoker settings:
 
  <mbean code="org.jboss.mq.il.oil.OILServerILService"
         name="jboss.mq:service=InvocationLayer,type=OIL,custom=xxx">
    <depends optional-attribute-name="Invoker">jboss.mq:service=Invoker</depends>
    <attribute name="ConnectionFactoryJNDIRef">ConnectionFactory2</attribute>
    <attribute name="XAConnectionFactoryJNDIRef">XAConnectionFactory2</attribute>
    <attribute name="ServerBindPort">80902</attribute>
    <attribute name="PingPeriod">60000</attribute>
    <attribute name="EnableTcpNoDelay">true</attribute>
  </mbean>
 
xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx
----- Original Message -----
Sent: Monday, June 02, 2003 5:01 AM
Subject: [JBoss-user] jbossmq-service.xml: Connection Factory example needed

All,
 
I'm using JBoss 3.0.4. Can somebody please send me an example on how to configure additional connection factories in jbossmq-service.xml or an external file (preferably).
I see the existing entries but want to define additional factories and simply copying one of the existing definitions and changing the name of the ConnectionFactoryJNDIRef gives me exceptions during deploy saying
 
org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.mq:service=InvocationLayer,type=OIL
 
Can someone give me some help with this? The bought manual does not show any sample configurations for JMS Connection Factories.

 

Reply via email to