Return-Path: 
 <users-return-6299-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 79142 invoked from network); 5 Apr 2009 02:57:13 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 5 Apr 2009 02:57:13 -0000
Received: (qmail 54870 invoked by uid 500); 5 Apr 2009 02:57:13 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 54796 invoked by uid 500); 5 Apr 2009 02:57:13 -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 54786 invoked by uid 99); 5 Apr 2009 02:57:13 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2009 02:57:13 +0000
X-ASF-Spam-Status: No, hits=0.2 required=10.0
	tests=SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.142.186 as permitted sender)
Received: from [209.85.142.186] (HELO ti-out-0910.google.com) (209.85.142.186)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Apr 2009 02:57:03 +0000
Received: by ti-out-0910.google.com with SMTP id y8so1352234tia.10
        for <users@camel.apache.org>; Sat, 04 Apr 2009 19:56:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from
         :user-agent:mime-version:to:subject:references:in-reply-to
         :x-enigmail-version:content-type:content-transfer-encoding;
        bh=X1E7wrTtB2R4sFom2WkSnC22/nJmylnzYTMTzwIT+Oo=;
        b=BfKdk+I6uz1vPFlhdvUwFo8nHtXP4LnDZolABegaIQsU0xMS6VtJxcNVR0+4CkMZxT
         6ZR3KkNAxJ70hPGG5PWX+5QceFmB9Z676DWTk+VxNFkt40hyCI9bKqod0/yUv48hDGUL
         ESCnWrR6du7im1BjfoCjHasfS49MeS83wtivc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=jsFyqnRlvNCtcpUqQqpEzzCIslvYZKrcpnam/IU+1L+J1QbtL5RMND9KV68it7VZGK
         rtm5enOMIryPgXv9/7qG2UgVHSo2X3AdnLKlWTRmDJCCQssB0C5Oc0dHLSideFR0+/5J
         fqZF37hjeSfDM5vNTJ+2GewtRgTUy9WtNbw/k=
Received: by 10.110.63.17 with SMTP id l17mr4247960tia.3.1238900200170;
        Sat, 04 Apr 2009 19:56:40 -0700 (PDT)
Received: from ?192.168.0.131? ([221.218.167.28])
        by mx.google.com with ESMTPS id b4sm6868158tic.16.2009.04.04.19.56.38
        (version=TLSv1/SSLv3 cipher=RC4-MD5);
        Sat, 04 Apr 2009 19:56:39 -0700 (PDT)
Message-ID: <49D81DE1.2050607@gmail.com>
Date: Sun, 05 Apr 2009 10:56:33 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: users@camel.apache.org
Subject: Re: Camel CXF Component with ActiveMQ
References: <22879705.post@talk.nabble.com>
In-Reply-To: <22879705.post@talk.nabble.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi,

If you are using Multicast, please keep in mind the default aggregation
strategy is using the latest exchange. So you need put the bean endpoint
 as the last one to endpoint like this.

 		<multicast>
 			<pipeline>
 				<convertBodyTo type="java.lang.String"/>
 				<to uri="activemq:TEST.FOO"/>
 				<to uri="file:C:\temp"/>
 			</pipeline>
          	  	<pipeline>
 				<to
 uri="bean:confirmationResponseBean?method=createConfirmationResponse" />
			</pipeline>

 		</multicast>

BTW, there is a thread[1] which discussed the same issue two weeks ago.

[1]http://www.nabble.com/Camel-2.0---Multicast-issue----td22725597.html#a22738417

Willem


ychawla wrote:
> Hello All,
> I have a question.  I have a Camel route configured to work with the CXF
> component using Camel 1.6.0.  I am trying to invoke a service, send the
> message to a queue and send a response.  However, the message seem to hang
> in the JMS queue.  Here is the route:
> 
> 	<cxf:cxfEndpoint id="dropoffSynchronousWebService-endpoint"
> 		serviceClass="org.wijiscommons.ssaf.drop_off.DropOffSynchronousService"
> 		address="/DropOffSynchronousService"
> 		endpointName="s:DropOffSynchronousService"
> 		serviceName="s:DropOffSynchronousService"
> 		xmlns:s="http://wijiscommons.org/ssaf/drop-off/"
> 
> 	/>
> 
> 
> 	<camelContext xmlns="http://activemq.apache.org/camel/schema/spring">
>     
> 	<route>
> 		<from uri="cxf:bean:dropoffSynchronousWebService-endpoint?dataFormat=POJO"
> />
> 		<to uri="bean:ProcessCXFIntoDOMBean?method=process" />
> 		<to uri="activemq:TEST.FOO"/>
> 		<to uri="bean:confirmationResponseBean?method=createConfirmationResponse"
> />
> 	</route>
> 
> In activeMQ, I see this error:
> 
> Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was
> not received within: 20000 millis on the exchange: Exchange[JmsMessage:
> ActiveMQTextMessage
> 
> Any ideas?
> 
> I also tried to see up the route in a multicast scenario:
> 
> 		<multicast>
> 			<pipeline> 
> 				<to
> uri="bean:confirmationResponseBean?method=createConfirmationResponse" />
> 			</pipeline>	
> 
> 			<pipeline>
> 				<convertBodyTo type="java.lang.String"/>
> 				<to uri="activemq:TEST.FOO"/>
> 				<to uri="file:C:\temp"/>
> 			</pipeline>
> 		</multicast> 
> 
> Funny thing with the 2nd example is that the message returned to the client
> is the string representation of the input message, rather than the out
> message I explicity set in the confirmationResponseBean like this:
> 
> exchange.getOut().setBody(returnDoc.getDocumentElement());
> 
> If I take activemq out of the equation and have a simple route like this,
> all is fine:
> 	<route>
> 		<from uri="cxf:bean:dropoffSynchronousWebService-endpoint?dataFormat=POJO"
> />
> 		<to uri="bean:ProcessCXFIntoDOMBean?method=process" />
> 		<to uri="bean:confirmationResponseBean?method=createConfirmationResponse"
> />
> 	</route>
> 
> 
> Any ideas?  I have tried all different types of solutions and have had no
> luck.
> 
> Thanks,
> Yogesh