Return-Path: 
 <users-return-5292-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 83601 invoked from network); 21 Jan 2009 16:40:25 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 21 Jan 2009 16:40:25 -0000
Received: (qmail 34215 invoked by uid 500); 21 Jan 2009 16:40:24 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 34201 invoked by uid 500); 21 Jan 2009 16:40:24 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 34190 invoked by uid 500); 21 Jan 2009 16:40:24 -0000
Delivered-To: apmail-activemq-camel-user@activemq.apache.org
Received: (qmail 34187 invoked by uid 99); 21 Jan 2009 16:40:24 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 08:40:24 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Jan 2009 16:40:02 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1LPg7B-0006hS-J2
	for camel-user@activemq.apache.org; Wed, 21 Jan 2009 08:39:41 -0800
Message-ID: <21586961.post@talk.nabble.com>
Date: Wed, 21 Jan 2009 08:39:41 -0800 (PST)
From: mario_horny <mario.horny@dzbank.de>
To: camel-user@activemq.apache.org
Subject: Re: timeout exception when pushing a message to a JMS Queue
In-Reply-To: <21562561.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: mario.horny@dzbank.de
References: <21562561.post@talk.nabble.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Hi all,

I solved this using the JMSConfigFeature solution:
http://cwiki.apache.org/CXF20DOC/using-the-jmsconfigfeature.html

But I had to be careful with the wsdl File. In order to use the JMS
configuration from the config XML file, the <jms:address> has to be left
blank.

<!-- Definition der Service-Implementierung mit Bindung und Adresse -->
<wsdl:service name="myService">
    <wsdl:port name="myPort" binding="....">
      <jms:address>
      </jms:address>
    </wsdl:port>
  </wsdl:service>

Regards,
Mario


mario_horny wrote:
> 
> Hi guys,
> 
> I've got the following scenario. I want to receive a HTTP Message, put the
> received message into a queue, wait for response and give the response
> back as HTTP response.
> 
> My spring.xml looks like that:
> 
> <!-- define INBOUND interface of the router  -->
> <cxf:cxfEndpoint id="RouterIn" address="..."  serviceClass="..." >
> </cxf:cxfEndpoint>
> 
> <!-- define OUTBOUND interface of the router -->
> <cxf:cxfEndpoint id="RouterOut" 
> wsdlURL="mywsdl.wsdl"
> endpointName="myPort"
> serviceName="myService"
> serviceClass="..."
> </cxf:cxfEndpoint>
> 
> <!-- Define the route to the VR Infoforum service -->    		
> <camelContext id="camel"
> xmlns="http://activemq.apache.org/camel/schema/spring">
>   <route errorHandlerRef="myDeadLetterErrorHandler">
>      <from uri="cxf:bean:RouterIn" />
>      <to uri="cxf:bean:RouterOut" /> 
>    </route>
> </camelContext> 
> 
> <!-- error handling  -->
> <bean id="myDeadLetterErrorHandler"
> class="org.apache.camel.builder.DeadLetterChannelBuilder">
>    <!-- define dead letter endpoint for messages that cannot be routed -->
>    <!--  property name="defaultDeadLetterEndpointUri" value"TODO"/ -- >
>    <!-- reference the redelivery policy to use -->
>    <property name="redeliveryPolicy" ref="myRedeliveryPolicyConfig"/>
> </bean>
> 
> <!-- here we set the redelivery settings -->
> <bean id="myRedeliveryPolicyConfig"
> class="org.apache.camel.processor.RedeliveryPolicy">
>    <!-- try redelivery at most 0 times, after that the exchange is dead 
> -->
>       <property name="maximumRedeliveries" value="0"/>
> </bean>   
> 
> In the wsdl File, the JMS definitions are made whose values are resolved
> using a JNDI file:
> 
> <!-- Definition der Service-Implementierung mit Bindung und Adresse -->
> <wsdl:service name="myService">
>     <wsdl:port name="myPort" binding="....">
>       <jms:address  jndiDestinationName="OutQueue"
> jndiReplyDestinationName="InQueue" jndiConnectionFactoryName="QueueConFac"
> destinationStyle="queue">
>         <jms:JMSNamingProperty
> value="com.sun.jndi.fscontext.RefFSContextFactory"
> name="java.naming.factory.initial" />
>         <jms:JMSNamingProperty value="file:."
> name="java.naming.provider.url" />
>       </jms:address>
>     </wsdl:port>
>   </wsdl:service>
> 
> The router is deployed well into a spring container. But when I send a
> message to the inbound interface, I _immediatly_ get a timeout exception
> back. 
> 
> Here is what the log looks like:
>   
> FINE: Payload to be sent out is :[<soap:Envelope
> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Body><ns1:gibDokumenteOperation
> xmlns:ns1="http://vrs-schema.genoip.de/VRInfoForumDokumente"><ns3:gibDokumente
> xmlns:ns2="http://vrs-schema.genoip.de/VRInfoForumDokumente/uebernehmeDokumente"
> xmlns:ns3="http://vrs-schema.genoip.de/VRInfoForumDokumente/gibDokumente"
> xmlns:ns4="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
> xmlns:ns5="http://www.genoip.de/protocol"><Organisation>?</Organisation><Optionen><Filter><DokumentID>?</DokumentID></Filter><VersandSynchron>true</VersandSynchron><DokumenteMitliefern>true</DokumenteMitliefern><AnhangMitliefern>true</AnhangMitliefern></Optionen></ns3:gibDokumente></ns1:gibDokumenteOperation></soap:Body></soap:Envelope>]
> Jan 20, 2009 11:50:27 AM org.apache.cxf.transport.jms.JMSConduit
> sendExchange
> FINE: JMSConduit send message
> .
> .
> .
> INFO: Interceptor has thrown exception, unwinding now
> java.lang.RuntimeException: Timeout receiving message with correlationId
> dfrseai100_xn08693_Thread[qtp0-0 -
> /CamelContext/VRInfoForumRouter,5,main]1232448628836
>         at
> org.apache.cxf.transport.jms.JMSConduit.sendExchange(JMSConduit.java:145)
>         at
> org.apache.cxf.transport.jms.JMSOutputStream.doClose(JMSOutputStream.java:56)
>         at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:167)
>         at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66)
>         at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
>         at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>         at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:466)
>         at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:308)
>         at
> org.apache.camel.component.cxf.CxfProducer.invokeClient(CxfProducer.java:284)
>         at
> org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:192)
>         at
> org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:165)
>         at
> org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:43)
>         at
> org.apache.camel.processor.SendProcessor.process(SendProcessor.java:75)
>         at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>         at
> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:173)
>         at
> org.apache.camel.processor.DeadLetterChannel.process(DeadLetterChannel.java:94)
>         at
> org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
>         at
> org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:52)
>         at
> org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:41)
>         at
> org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:66)
>         at
> org.apache.camel.component.cxf.CamelInvoker.invoke(CamelInvoker.java:178)
>         at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56)
>         at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37)
>         at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92)
>         at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220)
>         at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78)
>         at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:278)
>         at
> org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:252)
>         at
> org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:70)
>         at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:757)
>         at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
>         at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>         at org.mortbay.jetty.Server.handle(Server.java:320)
> 
> How can I configure the timeout behavior ? Feasible would be something
> like "wait for XXX seconds, after that put the message to the dead letter
> error handler". Or is there something I do fundamentally wrong ?
> 
> I'm using Artix 5.5 with camel 1.5.1.0. 
> 
> Many thanks in advance,
> Mario
> 

-- 
View this message in context: http://www.nabble.com/timeout-exception-when-pushing-a-message-to-a-JMS-Queue-tp21562561s22882p21586961.html
Sent from the Camel - Users mailing list archive at Nabble.com.