As you are using text message , I don't think it's not an issue of stream cache.
Maybe you need to check if there is something wrong when persisting the message 
into the DB.


--  
Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) 
(English)
          http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang  
Weibo: 姜宁willem





On Monday, September 16, 2013 at 11:48 AM, bhaumikananda wrote:

> Hi Willem Jiang,
>  
> I am using text message. The connection details are -  
>  
> <endpoint id="fitOptInMsgQueue" uri="wmq:myProjQueue" />
> <bean id="PROPAGATION_REQUIRED_FIT_OPTION"
> class="org.apache.camel.spring.spi.SpringTransactionPolicy">
> <property name="transactionManager" ref="jmsTransactionManager" />
> <property name="propagationBehaviorName" value="PROPAGATION_REQUIRED"/>
> </bean>
> .
> .
> <bean id="wmq" class="org.apache.camel.component.jms.JmsComponent">
> <property name="connectionFactory" ref="cachedConnectionFactory" />
> <property name="transactionManager" ref="jmsTransactionManager" />
> <property name="transacted" value="true" />
> <property name="asyncConsumer" value="true" />
> <property name="concurrentConsumers" value="${mq.concurrent.consumers}" />
> 5
> <property name="maxConcurrentConsumers"
> value="${mq.max.concurrent.consumers}"></property> 20
> <property name="errorHandlerLoggingLevel" value="ERROR" />
> <property name="errorHandlerLogStackTrace" value="false" />
> </bean>
>  
> <bean id="jmsTransactionManager"
> class="org.springframework.jms.connection.JmsTransactionManager">
> <property name="connectionFactory" ref="cachedConnectionFactory" />
> </bean>
>  
> <bean id="cachedConnectionFactory"
> class="org.springframework.jms.connection.CachingConnectionFactory"
> destroy-method="destroy">
> <property name="sessionCacheSize" value="50" />
> <property name="targetConnectionFactory">
> <ref bean="queueConnectionFactory" />
> </property>
> </bean>
>  
> <bean id="queueConnectionFactory"
> class="com.ibm.mq.jms.MQQueueConnectionFactory">
> <property name="hostName" value="${mq.host.name (http://mq.host.name)}" />
> <property name="port" value="${mq.host.port}" />
> <property name="queueManager" value="${mq.queueManager}" />
> <property name="channel" value="${mq.channel}" />
> <property name="transportType" value="${mq.transportType}" />
> <property name="securityExit" value="bctoolsj.wsmqtools.exits.BCPKIJCExit"
> />
> </bean>
>  
> ** Also I think it will be useful if I share the DB connection as well **  
>  
> <bean id="sql" class="org.apache.camel.component.sql.SqlComponent">
> <property name="dataSource" ref="myDS" />
> </bean>
>  
> <bean id="myDS" class="org.apache.commons.dbcp.BasicDataSource"
> destroy-method="close">
> <property name="driverClassName" value="net.sourceforge.jtds.jdbc.Driver"
> />
> <property name="url" value="${my.db.connectionurl}" />
> <property name="username" value="${my.db.user}" />
> <property name="password" value="${my.db.pwd}" />
> <property name="testOnBorrow" value="true"/>
> <property name="validationQuery" value="SELECT 1"/>
> <property name="maxActive" value="${my.active.db.threads}"/>8
> </bean>
>  
>  
>  
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/My-camel-route-not-able-to-handle-exception-tp5739381p5739494.html
> Sent from the Camel - Users mailing list archive at Nabble.com 
> (http://Nabble.com).



Reply via email to