On 9/20/07, kumar k <[EMAIL PROTECTED]> wrote:
> I have 2 jms consumer su, 2 bean su and 1 jms provider su in a SA. In
> standalone servicemix mode this works fine. But in servicemix-web second jms
> consumer is not able to start . Error is connection refused: connect.
>
> NFO - ServiceAssemblyLifeCycle - Starting service assembly: itm-sa
> INFO - ServiceUnitLifeCycle - Initializing service unit: itm-jmsprovider-su
> INFO - ServiceUnitLifeCycle - Initializing service unit: itm-jmsconsumer-su
> INFO - ServiceUnitLifeCycle - Initializing service unit: itm-firstbean-su
> INFO - ServiceUnitLifeCycle - Initializing service unit: itm-secondbean-su
> INFO - ServiceUnitLifeCycle - Initializing service unit: itm-jmsconsumer2-su
> INFO - ServiceUnitLifeCycle - Starting service unit: itm-jmsprovider-su
> INFO - ServiceUnitLifeCycle - Starting service unit: itm-jmsconsumer-su
> INFO - ServiceUnitLifeCycle - Starting service unit: itm-firstbean-su
> INFO - ServiceUnitLifeCycle - Starting service unit: itm-secondbean-su
> INFO - ServiceUnitLifeCycle - Starting service unit: itm-jmsconsumer2-su
> INFO - DeploymentService - Error in start
> java.lang.Exception: <?xml version="1.0" encoding="UTF-8"?>
> <jbi-task xmlns="http://java.sun.com/xml/ns/jbi/management-message";
> version="1.0">
> <jbi-task-result>
> <frmwk-task-result>
> <frmwk-task-result-details>
> <task-result-details>
> <task-id>start</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> </task-result-details>
> </frmwk-task-result-details>
> </frmwk-task-result>
> <component-task-result>
> <component-name>servicemix-jms</component-name>
> <component-task-result-details>
> <task-result-details>
> <task-id>start</task-id>
> <task-result>FAILED</task-result>
> <message-type>ERROR</message-type>
> <task-status-msg>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Unable to start service unit</loc-message>
> </msg-loc-info>
> </task-status-msg>
> <exception-info>
> <nesting-level>1</nesting-level>
> <msg-loc-info>
> <loc-token/>
> <loc-message>Could not connect to broker URL: tcp://localhost:61616.
> Reason: java.net.ConnectException: Connection refused: connect</loc-message>
> <stack-trace><![CDATA[javax.jms.JMSException: Could not connect to broker
> URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection
> refused: connect
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:33)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:280)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:214)
> at
> org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:161)
> at
> org.apache.servicemix.jms.AbstractJmsProcessor.start(AbstractJmsProcessor.java:74)
> at org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:348)
> at org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:55)
What happens if you package the JMS consumer SUs in separately? Put
each one in it's own SA and deploy them separately just to see what
happens.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Castor - http://castor.org/
