You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by tnine <to...@gmail.com> on 2007/05/22 21:36:27 UTC
Active MQ appears to be running, but JBoss complains about the
MBeans
Hi all,
I am trying to embed the activemq-rar 4.1.1 into JBoss 4.0.5GA. I
followed the direction here
http://devzone.logicblaze.com/site/integrating-apache-activemq-with-jboss.html
and used tcp instead of vm since ultimately I'll have clustering and fail
over. I receive the following error when JBoss starts.
--- MBeans waiting for other MBeans ---
ObjectName: activemq.queue:name=outboundQueue
State: CONFIGURED
I Depend On:
jboss.jca:service=RARDeployment,name=activemq-rar-4.1.1.rar
ObjectName: activemq.topic:name=inboundTopic
State: CONFIGURED
I Depend On:
jboss.jca:service=RARDeployment,name=activemq-rar-4.1.1.rar
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=RARDeployment,name=activemq-rar-4.1.1.rar
State: NOTYETINSTALLED
Depends On Me:
activemq.queue:name=outboundQueue
activemq.topic:name=inboundTopic
Then after about 10 seconds of running, I receive this error message.
java.io.IOException: Wire format negociation timeout: peer did not send his
wire format.
at
org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:88)
at
org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:47)
at
org.apache.activemq.broker.TransportConnection.dispatch(TransportConnection.java:1138)
at
org.apache.activemq.broker.TransportConnection.processDispatch(TransportConnection.java:805)
at
org.apache.activemq.broker.TransportConnection.start(TransportConnection.java:885)
at
org.apache.activemq.broker.TransportConnector$1.onAccept(TransportConnector.java:148)
at
org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:167)
at java.lang.Thread.run(Thread.java:595)
However I can telnet to my localhost at port 61616 and it seems to connect
correctly. Any ideas how to get rid of this error?
Thanks,
Todd
broker-config.xml
<beans>
<broker xmlns="http://activemq.org/config/1.0" brokerName="pefcu.broker"
useJmx="true">
<persistenceAdapter>
<journaledJDBC journalLogFiles="5" dataDirectory="activemq-data"/>
<!-- To use a different datasource, use th following syntax : -->
<!--
<journaledJDBC journalLogFiles="5" dataDirectory="../data"
dataSource="#postgres-ds"/>
-->
</persistenceAdapter>
<transportConnectors>
<!-- prefixing a connector with discovery: causes the connector to be
advertiesed over rendezvous -->
<transportConnector name="pefcu.broker" uri="tcp://localhost:61616"
discoveryUri="multicast://default"/>
</transportConnectors>
<networkConnectors>
<!-- by default just auto discover the other brokers -->
<networkConnector uri="multicast://default"/>
<!--
<networkConnector
uri="static://(tcp://host1:61616,tcp://host2:61616)"/>
-->
</networkConnectors>
</broker>
activemq-jms-ds.xml
<connection-factories>
<tx-connection-factory>
<jndi-name>activemq/QueueConnectionFactory</jndi-name>
<xa-transaction/>
<track-connection-by-tx/>
<rar-name>activemq-rar-4.1.1.rar</rar-name>
<connection-definition>javax.jms.QueueConnectionFactory</connection-definition>
<ServerUrl>tcp://localhost:61616</ServerUrl>
<!--
<UserName>sa</UserName>
<Password></Password>
-->
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>3</idle-timeout-minutes>
</tx-connection-factory>
<tx-connection-factory>
<jndi-name>activemq/TopicConnectionFactory</jndi-name>
<xa-transaction/>
<track-connection-by-tx/>
<rar-name>activemq-rar-4.1.1.rar</rar-name>
<connection-definition>javax.jms.TopicConnectionFactory</connection-definition>
<ServerUrl>tcp://localhost:61616</ServerUrl>
<!--
<UserName>sa</UserName>
<Password></Password>
-->
<min-pool-size>1</min-pool-size>
<max-pool-size>200</max-pool-size>
<blocking-timeout-millis>30000</blocking-timeout-millis>
<idle-timeout-minutes>3</idle-timeout-minutes>
</tx-connection-factory>
<mbean code="org.jboss.resource.deployment.AdminObject"
name="activemq.queue:name=outboundQueue">
<attribute name="JNDIName">activemq/queue/outbound</attribute>
<depends
optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name=activemq-rar-4.1.1.rar</depends>
<attribute name="Type">javax.jms.Queue</attribute>
<attribute name="Properties">PhysicalName=queue.outbound</attribute>
</mbean>
<mbean code="org.jboss.resource.deployment.AdminObject"
name="activemq.topic:name=inboundTopic">
<attribute name="JNDIName">activemq/topic/inbound</attribute>
<depends
optional-attribute-name="RARName">jboss.jca:service=RARDeployment,name=activemq-rar-4.1.1.rar</depends>
<attribute name="Type">javax.jms.Topic</attribute>
<attribute name="Properties">PhysicalName=topic.inbound</attribute>
</mbean>
</connection-factories>
--
View this message in context: http://www.nabble.com/Active-MQ-appears-to-be-running%2C-but-JBoss-complains-about-the-MBeans-tf3799939s2354.html#a10750869
Sent from the ActiveMQ - User mailing list archive at Nabble.com.