Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <24184908.post@talk.nabble.com>
Date: Wed, 24 Jun 2009 06:36:51 -0700 (PDT)
From: Tim83 <tim.struyf@roots.be>
To: users@camel.apache.org
Subject: Problems with JMS messages being dropped by camel when restarting
 the context
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi all,

I've stumbled upon an issue and am not sure how to solve it. :confused:
Basicly I've setup some routes using camel 1.6.0 that consume messages and
dispatches them to our services.  Everything works fine except for one
thing.

When I restart my camel context I start to lose messages, and I get the
errors on my consumers.

The route that I use for testing looks like this

<camel:route>
	<camel:from uri="activemq:queue:in.A" />
	<camel:policy ref="PROPAGATION_REQUIRED"/>
	<!-- first assemble the document -->
	<camel:to uri="activemq:queue:service.1?requestTimeout=500000"
pattern="OutIn"/>
	<camel:choice>
		<camel:when>
			<camel:el>${in.headers.errorMessage != null}</camel:el>
			<camel:to uri="activemq:queue:DLQ.in.A?disableReplyTo=true"
pattern="InOnly"/>
			<camel:to uri="activemq:queue:out.A?disableReplyTo=true"
pattern="InOnly"/>
		</camel:when>
		<camel:otherwise>
			<camel:choice>
				<camel:when>
					<camel:el>${in.body["some field"] == "true"}</camel:el>
					<camel:process ref="convertMessageProcessor"/>
					<camel:to uri="activemq:queue:service.B?requestTimeout=500000"
pattern="OutIn"/>
					<camel:choice>
						<camel:when>
							<camel:el>${in.headers.errorMessage} != null</camel:el>
							<camel:process ref="unconvertMessageProcessor"/>
							<camel:to uri="activemq:queue:DLQ.in.A?disableReplyTo=true"
pattern="InOnly"/>
							<!-- send a warning message to ICD that the assembly is
delayed/failed -->
							<camel:to uri="activemq:queue:out.A?disableReplyTo=true"
pattern="InOnly"/>
						</camel:when>
						<camel:otherwise>
							<camel:to uri="activemq:queue:out.A?disableReplyTo=true"
pattern="InOnly"/>
						</camel:otherwise>
					</camel:choice>
				</camel:when>
				<camel:otherwise>
					<camel:to uri="activemq:queue:out.A?disableReplyTo=true"
pattern="InOnly"/>
				</camel:otherwise>
			</camel:choice>
		</camel:otherwise>
	</camel:choice>
</camel:route>

<bean id="jmsConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
    	<property name="connectionFactory" ref="jmsFactory"/>
	    <property name="transacted" value="true"/>
	    <property name="concurrentConsumers" value="1"/>
	    <property name="transactedInOut" value="true"/>
	    <property name="transactionManager" ref="jmsTransactionManager"/>
	   	<property name="replyToTempDestinationAffinity" value="producer"/>
	</bean>
	<bean id="jmsTransactionManager"
class="org.springframework.jms.connection.JmsTransactionManager">
		<property name="connectionFactory" ref="jmsFactory"/>
	</bean>
	
	<!-- camel policy we refer to in our route -->
	<bean id="PROPAGATION_REQUIRED"
class="org.apache.camel.spring.spi.SpringTransactionPolicy">
		<constructor-arg>
			<bean
class="org.springframework.transaction.support.TransactionTemplate">
				<property name="transactionManager" ref="jmsTransactionManager"/>
			</bean>
		</constructor-arg>
	</bean>

When I stop the camel context right after the message has arrived in the
service.B consumer, but before it's finished I see the following error in
the console output.

Cannot publish to a deleted Destination:
temp-queue://ID:56P3J-57576-1245848023626-0:0:2; nested exception is
javax.jms.InvalidDestinationException: Cannot publish to a deleted
Destination: temp-queue://ID:56P3J-57576-1245848023626-0:0:2

After which the message is lost?

I also have a simillar issue with the delayer, if I restart my context when
the message got picked up by the delayer the message gets lost?
<camel:route>
	<camel:from uri="activemq:queue:DLQ.in.A" />
	<camel:policy ref="PROPAGATION_REQUIRED"/>
	<camel:bean ref="enricher" method="enrich"/>
	<camel:delayer>
		<camel:simple>header.JMSTimestamp</camel:simple>
		<camel:delay>60000</camel:delay>
	</camel:delayer>
	<camel:to uri="activemq:queue:in.A?disableReplyTo=true" pattern="InOnly"/>
</camel:route>

Does anybody have the same issue? or know how to solve this?

best regards,
Tim
-- 
View this message in context: http://www.nabble.com/Problems-with-JMS-messages-being-dropped-by-camel-when-restarting-the-context-tp24184908p24184908.html
Sent from the Camel - Users mailing list archive at Nabble.com.