Hi! Excellent! Thanks for the tip, it worked like a charm, and will do until 3.0.1. Looking forward to it ;)
/Eje gnodet wrote: > > We don't have any snapshots deployed for 3.0.1. > The workaround is to disable the tx log. > In /conf/tx.xml, comment the <jencks:howlLog /> > element and uncomment the previous one > (<bean id="transactionLog" ... />). > It means that you won't be able to recover transactions > from a crash, but I would not recommend to use > it in production if you need receoverable transactions. > > > On 10/18/06, Eyji <[EMAIL PROTECTED]> wrote: >> >> Yup, that's the one, and I guess you can figure out my next question: >> When is >> 3.0.1 out. Really need that patch :) >> Another solution would be to use a Snapshot of course, but we don't want >> other things to bail out, or can you recommend us to use the current one? >> >> /Eje >> >> >> >> gnodet wrote: >> > >> > I guess you hit the following problem: >> > http://issues.apache.org/activemq/browse/SM-622 >> > This has been fixed and will be available in 3.0.1 >> > >> > On 10/18/06, Eyji <[EMAIL PROTECTED]> wrote: >> >> >> >> Thanks for your quick reply! I've now managed to reconfigure and >> deploy >> >> my SU >> >> successfully using a JCA-based JMS transactional management. However, >> the >> >> only thing I get after submitting messages to the queue is "Status is >> >> STATUS_NO_TRANSACTION" exception from servicemix. Thankful for hints >> >> around >> >> this! >> >> >> >> Regards, >> >> /Eje >> >> >> >> >> >> gnodet wrote: >> >> > >> >> > You are trying to deploy a SU packaged for servicemix-lwcontainer >> >> > to servicemix-jms, which is not possible. >> >> > You can either use the lightweight components (jms or jca) and >> >> > deploy them in the lwcontainer, or use servicemix-jms >> >> > (http://servicemix.goopen.org/site/servicemix-jms.html) but the >> content >> >> > of the SU is not the same. >> >> > >> >> > On 10/17/06, Eyji <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Hi! >> >> >> >> >> >> I've been trying to deploy a SU using instructions from >> >> >> http://servicemix.org/site/jca.html. My servicemix.xml includes the >> >> >> following: >> >> >> >> >> >> <?xml version="1.0" encoding="UTF-8"?> >> >> >> >> >> >> <beans xmlns:sm="http://servicemix.apache.org/config/1.0"; >> >> >> xmlns:duh="http://my.system/duh";> >> >> >> >> >> >> <classpath> >> >> >> <location>.</location> >> >> >> <location> >> >> >> >> >> >> lib/servicemix-components-${servicemix-version}.jar >> >> >> </location> >> >> >> </classpath> >> >> >> >> >> >> <sm:serviceunit id="jbi"> >> >> >> <sm:activationSpecs> >> >> >> <sm:activationSpec >> componentName="mottagare" >> >> >> service="duh:MottagareService" endpoint="mottagare" >> >> >> destinationService="duh:validerare"> >> >> >> <sm:component> >> >> >> <bean >> >> >> class="org.apache.servicemix.components.jms.JmsInUsingJCABinding"> >> >> >> >> >> >> <property >> >> >> name="jcaContainer" ref="jencks" /> >> >> >> >> >> >> <property >> >> >> name="activationSpec"> >> >> >> <bean >> >> >> class="org.apache.activemq.ra.ActiveMQActivationSpec"> >> >> >> >> >> <property >> >> >> name="destination" value="my.q" /> >> >> >> >> >> <property >> >> >> name="destinationType" value="javax.jms.Queue" /> >> >> >> </bean> >> >> >> </property> >> >> >> >> >> >> <!-- use XA >> >> transactions >> >> >> --> >> >> >> <property >> >> >> name="transactionManager" ref="transactionManager" /> >> >> >> </bean> >> >> >> </sm:component> >> >> >> </sm:activationSpec> >> >> >> </sm:activationSpecs> >> >> >> </sm:serviceunit> >> >> >> >> >> >> <bean id="jencks" class="org.jencks.JCAContainer"> >> >> >> >> >> >> <!-- lets use the default configuration of work >> >> manager >> >> >> and transaction >> >> >> manager--> >> >> >> <property name="bootstrapContext"> >> >> >> <bean >> >> >> >> >> >> class="org.jencks.factory.BootstrapContextFactoryBean"> >> >> >> <property name="threadPoolSize" >> >> >> value="25" /> >> >> >> </bean> >> >> >> </property> >> >> >> >> >> >> <!-- the JCA Resource Adapter --> >> >> >> <property name="resourceAdapter"> >> >> >> <bean id="activeMQResourceAdapter" >> >> >> >> >> >> class="org.apache.activemq.ra.ActiveMQResourceAdapter"> >> >> >> <property name="serverUrl" >> >> >> >> value="tcp://localhost:61616" >> >> /> >> >> >> </bean> >> >> >> </property> >> >> >> </bean> >> >> >> >> >> >> <!-- Geronimo XA Transaction Manager --> >> >> >> <bean id="transactionManager" >> >> >> class="org.jencks.factory.TransactionManagerFactoryBean" /> >> >> >> >> >> >> </beans> >> >> >> >> >> >> >> >> >> Upon deploying the SA using Maven, I get the following error: >> >> >> >> >> >> <?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>deploy</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 >> >> >> xmlns="http://java.sun.com/xml/ns/jbi/management-message";> >> >> >> <component-name>servicemix-jms</component-name> >> >> >> <component-task-result-details> >> >> >> <task-result-details> >> >> >> <task-id>deploy</task-id> >> >> >> <task-result>FAILED</task-result> >> >> >> <message-type>ERROR</message-type> >> >> >> <task-status-msg> >> >> >> <msg-loc-info> >> >> >> <loc-token/> >> >> >> <loc-message>Unable to find suitable deployer for Service Unit >> >> >> 'duh-jms-su'</loc-message> >> >> >> </msg-loc-info> >> >> >> </task-status-msg> >> >> >> </task-result-details> >> >> >> </component-task-result-details> >> >> >> </component-task-result> >> >> >> <component-task-result >> >> >> xmlns="http://java.sun.com/xml/ns/jbi/management-message";> >> >> >> <component-name>servicemix-lwcontainer</component-name> >> >> >> <component-task-result-details> >> >> >> <task-result-details> >> >> >> <task-id>deploy</task-id> >> >> >> <task-result>SUCCESS</task-result> >> >> >> </task-result-details> >> >> >> </component-task-result-details> >> >> >> </component-task-result> >> >> >> </jbi-task-result> >> >> >> </jbi-task> >> >> >> >> >> >> The number of letters in the error message impress me, the content >> >> >> doesn't. >> >> >> :) >> >> >> Hope you can help me out here, I'm stuck and tired of trial and >> >> error.... >> >> >> >> >> >> Regards, >> >> >> /Eje >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> http://www.nabble.com/Unable-to-find-suitable-deployer-tf2459316.html#a6854522 >> >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Cheers, >> >> > Guillaume Nodet >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Unable-to-find-suitable-deployer-tf2459316.html#a6874679 >> >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> >> >> >> > >> > >> > -- >> > Cheers, >> > Guillaume Nodet >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Unable-to-find-suitable-deployer-tf2459316.html#a6875761 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/Unable-to-find-suitable-deployer-tf2459316.html#a6877842 Sent from the ServiceMix - User mailing list archive at Nabble.com.
