Re: camel+quartz schedulers

2012-07-20 Thread Sudhakar.kaithepalli

can you tell me how to stop camel routes please. Its urgent to me.


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716245.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: setting http soTimeout via setHeader() is not working

2012-07-20 Thread khuss
Thanks for the pointer. However, this doesn't help. The way the code is
structured, we have another class called RequestProcessor to frame the
request and dynamically change the URI using setHeader(). 

--
View this message in context: 
http://camel.465427.n5.nabble.com/setting-http-soTimeout-via-setHeader-is-not-working-tp5716218p5716250.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: setting http soTimeout via setHeader() is not working

2012-07-20 Thread khuss
Just to clarify more: We need to build the URI based on a parameter that is
passed in the request. This means we need to access the Exchange object to
get the request parameter and append that to the URI. 

I do not see how we can do this without using the setHeader() method.
Unfortunately, the timeout mechanism doesn't work when we use setHeader().



--
View this message in context: 
http://camel.465427.n5.nabble.com/setting-http-soTimeout-via-setHeader-is-not-working-tp5716218p5716257.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Question on Camel WireTap EIP custom thread pool creation

2012-07-20 Thread Edwin
Thanks for your response Claus, I have removed the threads() however I still
get the same behavior.

I am using Camel version 2.9.2

Thanks,
Edwin

--
View this message in context: 
http://camel.465427.n5.nabble.com/Question-on-Camel-WireTap-EIP-custom-thread-pool-creation-tp5716239p5716259.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: camel+quartz schedulers

2012-07-20 Thread Sudhakar.kaithepalli
Hi

   Thanks for your quick response... 
and
1.) can u tell me how to stop camel route after it hit the FTP server.
one more thing is
2.) how can i find out the size of files in FTP server?


Thanks and regards..


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716260.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: camel+quartz schedulers

2012-07-20 Thread Sudhakar.kaithepalli



SimpleTrigger means, my camel route like this...

from(quartz://schedulerJob?trigger.repeatInterval=6trigger.repeatCount=+SimpleTrigger.REPEAT_INDEFINITELY).to(some
bean method ).end()

This is wht my camel route using quartz scheduler


-
Sudhakar Kaithepalli
--
View this message in context: 
http://camel.465427.n5.nabble.com/camel-quartz-schedulers-tp5715992p5716261.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: soap over jms

2012-07-20 Thread Christian Schneider
I think your problem is related to IBM MQ. Can you try to run the exmple 
with activemq first?


Maybe you need to use a fixed reply queue with the IBM broker.

Christian

Am 20.07.2012 07:15, schrieb bhushand:

Hello Willem
As I am trying to run example shared by Christian, all
configuration are from that files. Please find below configurations
For server:
jaxws:endpoint address=camel://direct:greeterServerEndpoint
id=server
implementor=#greeterImpl
endpointName=s2:JMSGreeterPortType 
serviceName=s2:JMSGreeterService
xmlns:s2=http://examples/jms-greeter; /

bean id=greeterImpl
class=main.java.demo.jms_greeter.server.GreeterJMSImpl/

 route is

route
from uri=jms:MyQueueName?exchangePattern=InOnly /
to uri=direct:greeterServerEndpoint /

setHeader headerName=SOAPJMS_contentType
constanttext/xml/constant
/setHeader
setHeader headerName=SOAPJMS_requestURI
constantjms://queue:MyQueueName/constant
/setHeader
/route

For Client:
jaxws:client id=greeterProxy
address=camel://direct:greeterClientEndpoint
endpointName=s2:JMSGreeterPortType 
serviceName=s2:JMSGreeterService
xmlns:s2=http://examples/jms-greeter;
serviceClass=main.java.examples.jms_greeter.JMSGreeterPortType 
/

bean id=client class=main.java.demo.jms_greeter.client.Client
property name=greeter ref=greeterProxy /
/bean

route is as follow,
route
from uri=direct:greeterClientEndpoint /
setHeader headerName=SOAPJMS_contentType
constanttext/xml/constant
/setHeader
setHeader headerName=SOAPJMS_requestURI
constantjms://queue:MyQueueName/constant
/setHeader
to uri=jms:MyQueueName?exchangePattern=InOnly /
/route


Here I am running client  getting previous error. From configuration my
understanding is, When client is executed it will place message over queue
then it will call server impl class. If  I am wrong, please correct me.


--Thanks
  Bhushan



--
View this message in context: 
http://camel.465427.n5.nabble.com/soap-over-jms-tp5715942p5716279.html
Sent from the Camel - Users mailing list archive at Nabble.com.



--
 
Christian Schneider

http://www.liquid-reality.de

Open Source Architect
Talend Application Integration Division http://www.talend.com



Re: setting http soTimeout via setHeader() is not working

2012-07-20 Thread Claus Ibsen
On Thu, Jul 19, 2012 at 5:25 PM, khuss kamal.huss...@alcatel-lucent.com wrote:
 Just to clarify more: We need to build the URI based on a parameter that is
 passed in the request. This means we need to access the Exchange object to
 get the request parameter and append that to the URI.

 I do not see how we can do this without using the setHeader() method.
 Unfortunately, the timeout mechanism doesn't work when we use setHeader().


Yes the recipient list can do that, just use an expression / method
call / simple etc. to build the URI with the soTimeout value you want.




 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/setting-http-soTimeout-via-setHeader-is-not-working-tp5716218p5716257.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen


Re: Question on Camel WireTap EIP custom thread pool creation

2012-07-20 Thread Claus Ibsen
On Thu, Jul 19, 2012 at 6:05 PM, Edwin edwin.rabbi...@gmail.com wrote:
 Thanks for your response Claus, I have removed the threads() however I still
 get the same behavior.

 I am using Camel version 2.9.2


Can you try with 2.10, I think there was a bug in wire tap custom
thread pool, but it may only be when using XML DSL.
But testing with latest release would be good.

And just to be sure you see 2nd thread pool. Can you double check its
for wire tap and not some kind of other pool?

 Thanks,
 Edwin

 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Question-on-Camel-WireTap-EIP-custom-thread-pool-creation-tp5716239p5716259.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen


Re: testing pollEnrich via mock

2012-07-20 Thread Claus Ibsen
Hi

See advice with where you can replace the uri of pollEnrich in the unit test
http://camel.apache.org/advicewith.html

Or you can use property placeholders for the uris, and then use a
different .properties file for unit testing
http://camel.apache.org/using-propertyplaceholder.html

On Thu, Jul 19, 2012 at 5:45 PM, sensen n.sen...@web.de wrote:
 Hello,
 I love the test-support of camel.
 Unfortunately, currently I have a problem: I want to create a route which
 uses
 a PollEnrich-component. And I want to write a test which mocks away the URI
 which
 is used by the pollEnrich-component.

 But I cannot manage this. I tried the following test, which fails.
 This means: Firstly the assertMockEndpointsSatisfied fails and
 secondly, when the route is executed it in fact accesses the endpoint
 file:asfd. (But it should not use this file since I wanted to mock
 it away)

 Any hints, how I can manage that the pollEnrich is mocked?

 @@Test
 public class TestPollEnrich extends CamelTestSupport
 {
 @Override
 public String isMockEndpointsAndSkip()
 { return file:*; }

 public void testStdFlow() throws Exception
 {
 getMockEndpoint(mock://file:asfd).expectedMessageCount(1);
 super.sendBody(direct:start, egal);
 assertMockEndpointsSatisfied();
 }

 @Override
 protected RouteBuilder createRouteBuilder() throws Exception
 {
 return new RouteBuilder()
 {  @Override
 public void configure() throws Exception
 {  from(direct:start).pollEnrich(file:asfd); }
 };
 }
 }


 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/testing-pollEnrich-via-mock-tp5716258.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen


Re: Multiple JPA Consumers

2012-07-20 Thread MSE
hi, 
i am new in camel and i have a problem to create a mutli processing JPA
route on a table:
my configuration is seems to be correct but no multiprocessing occur on my
bean AcquisitionMvibsComponent ... any suggestion would be appreciate

here is my configuration


threadPool id=myPool threadName=MPH poolSize=16
maxPoolSize=30 maxQueueSize=1000 /

route
from

uri=jpa://diamis.xpeach.acquisition.AcquisitionRequest?maximumResults=5#38;consumer.namedQuery=acquisitionrequest#38;consumer.delay=1000#38;persistenceUnit=monitoringPU
/
transacted ref=required_new_database /
camel:doTry


threads executorServiceRef=myPool
bean ref=AcquisitionMvibsComponent 
method=process /
/threads


to 
uri=MQconnection:queue:DISTRIBUTION.DISPATCHER /
camel:doCatch

exceptiondiamis.xpeach.exception.XPeachException/exception
bean 
ref=ExceptionToStringTransformer method=doTransform/bean
to uri=MQconnection:queue:ERROR/to
/camel:doCatch
/camel:doTry
/route



--
View this message in context: 
http://camel.465427.n5.nabble.com/Multiple-JPA-Consumers-tp472290p5716287.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Forced termination of the current exchange and returning appropriate response code

2012-07-20 Thread Claus Ibsen
Hi

You can do a content based router, and if the certificate is invalid,
then return a response.
http://camel.apache.org/content-based-router.html

There is also a stop EIP to stop further processing. You can put that
on the exchange as a property from java code, eg so you can just use a
bean to check if the certificate is valid or not. And if not valid,
then set the message with some response payload, and then mark it to
stop.

There is a constant on Exchange with the name of the property
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Exchange.html#ROUTE_STOP

See for example the StopProcessor source code.

There are other ways such as thrown an exception and using the error
handler to react and stop routing etc.


On Thu, Jul 19, 2012 at 9:37 AM, helander leh...@gmail.com wrote:
 In my setup I have a cxf endpoint that are consumed by a route. As the first
 step in my route I have a bean that picks up the TLSSession from the
 exchange and puts back a property on the exchange that contains the peer
 certificates. I doing this in order to access information from the client
 certificates further down the route. In the case that no client certificate
 has been provided (access was via http and not https or the http server
 configuration may not have required the certificates to be provided by the
 client) I would like to force the exchange to return ( no further
 processing along the route) and provide some appropriate return code.

 What specific operations do I have to do on the exchange (or its in/out
 messages) to make Camel terminate the route with the appropriate (HTTP)
 return code.

 /Lars

 --
 View this message in context: 
 http://camel.465427.n5.nabble.com/Forced-termination-of-the-current-exchange-and-returning-appropriate-response-code-tp5716235.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen


Camel ActiveMQ consumers do not consume after restart

2012-07-20 Thread Marco Zapletal

Hi folks,

We have an application where we have two Camel contexts (C1, C2) which 
exchange messages via two queues (Q1, Q2). These queues are located on 
the same ActiveMQ broker. Thereby, the message flow goes as follows:


C1 - Q1 - C2
C2 - Q2 - C1

C2 uses furthermore some internal queues on the AMQ broker, but I 
guess they are not relevant to the problem.


The issue we are facing can be described as follows and happens only 
when C1 or C2 go down or have to be restarted


- In case, no messages are produced of either C1/C2 while the other one 
restarts, everything is fine - i.e., there is no problem with consuming 
messages


- In case, messages are produced of either C1/C2 and are put in the 
respective queue, during the absence of the other Camel application, we 
gonna face problems with consuming messages from the queues.
We have especially tested this scenario by stopping C2. C1 produces 
messages to Q1. Then we restart C2 again and (almost) nothing happened.


- By almost I mean, that the context of C2 starts up without errors. 
What is also observed is that when we have 1 concurrentConsumer defined 
in the AMQ consumer configuration in C2, 1 message is consumed (if 3 
concurrentConsumers are defined, 3 messages are consumed). Afterwards, 
consumption stops.


- When restarting C2 again, 1 message is consumed from Q1 (in case of 1 
concurrentConsumer)


- C2 exposes also two CXF services as producers of routes. Both of the 
two routes have one of those internal AMQ queues as their final 
destination. When we want to access their respective WSDL URL, the 
request hangs.


- We have an admin Web application monitoring C2 via JMX. The admin 
application hangs due to no response from C2's JMX services (although 
the C2 context starts up properly according to the logs).


- Nothing special can be seen in the logs. We examined the logs on DEBUG 
level (on Camel as well as on AMQ side) and nothing special could be seen.


- We went back to a rather base config. No transactions, no connection 
pools, no caching of consumers/producers. We have experimented with the 
prefetch (setting it to 1 or even 0) without success.


- In order to reach proper behavior again, Q1/Q2 (and maybe even the 
internal queues of C2) have to be purged. Then C2 has be to be 
restarted again. After this procedure, message passing is back to normal.



Sorry for the long post, but I want to describe the problem as detailed 
as possible. Since we have been working on this now for days any help 
would be highly appreciated.



Thanks and best regards,


Marco





Re: NPE in CamelNamespaceHandler with JDK7

2012-07-20 Thread Willem Jiang

I'll take a look at this issue next week.

On Fri Jul 20 15:50:16 2012, hschoeneberg wrote:

Yes, of course - done!

Kind regards,
Hendrik Schöneberg



--
View this message in context: 
http://camel.465427.n5.nabble.com/NPE-in-CamelNamespaceHandler-with-JDK7-tp5716241p5716284.html
Sent from the Camel - Users mailing list archive at Nabble.com.





--
Willem
--
FuseSource
Web: http://www.fusesource.com
Blog:http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang



Re: Converting CSV to XML

2012-07-20 Thread ambarish.d
Hello Claus,

Thanks for the help. Bindy was really helpful. 
I am still using xstream though, its lot more easier (I feel).

Giving the working solution of this problem if anybody needs one.

 /DataFormat bindy = new BindyCsvDataFormat(com.your.package.dto);
 from(file://TEST?fileName=Employee.csv).
unmarshal(bindy). 
marshal(). 
xstream(). 
to(file://TESTOUT?fileName=employee.xml); /


This works as expected. /com.your.package.dto.EmployeeDTO/ has to be
annotated properly to make this work.

List of dependencies:

camel-bindy-2.9.0.jar, camel-core-2.9.0.jar,camel-csv-2.9.0.jar,
camel-xstream-2.9.0.jar,
slf4j-api-1.6.4.jar, slf4j-log4j12-1.6.4.jar,
solr-commons-csv-1.3.0.jar,xstream-1.3.1
  




-
thanks
Amby
http://workingwithqueues.blogspot.com/ 
--
View this message in context: 
http://camel.465427.n5.nabble.com/Converting-CSV-to-XML-tp5711086p5716294.html
Sent from the Camel - Users mailing list archive at Nabble.com.


No language could be found for: js

2012-07-20 Thread RobertO
I'm trying to use javascript in my routes but keep getting the No language
could be found for: js error in my unit tests when I load the camelcontext
via spring.  I've found other references to this error on the mailing list
but have so far been unable to resolve this.

Camel v2.9.2

I've added these dependencies to my pom:

dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-script/artifactId
version${camel.version}/version
/dependency

dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-script-javascript/artifactId
version${camel.version}/version
/dependency

Can someone give me instructions on how to fix this?

Thank you.




--
View this message in context: 
http://camel.465427.n5.nabble.com/No-language-could-be-found-for-js-tp5716299.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: How to invoke CXF webservice from processor bean

2012-07-20 Thread jeyaseelan78
Hi,
I hope you are asking for the wsdl, here is my wsdl...

wsdl:definitions xmlns:ns1=http://schemas.xmlsoap.org/soap/http;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:tns=http://pas.adapter.service.xyz.abc.XX/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
name=PasApplicationAdapterServiceService
targetNamespace=http://pas.adapter.service.xyz.abc.XX/;
wsdl:types
xs:schema xmlns:tns=http://pas.adapter.service.xyz.abc.XX/;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=unqualified
elementFormDefault=unqualified
targetNamespace=http://pas.adapter.service.xyz.abc.XX/;
xs:element name=processClient 
type=tns:processClient /
xs:element name=processClientResponse 
type=tns:processClientResponse
/
xs:element name=processPASLoadStatus 
type=tns:processPASLoadStatus
/
xs:element name=processPASLoadStatusResponse
type=tns:processPASLoadStatusResponse /
xs:complexType name=processClient
xs:sequence
xs:element minOccurs=0 name=arg0 
type=xs:string /
/xs:sequence
/xs:complexType
xs:complexType name=processClientResponse
xs:sequence
xs:element minOccurs=0 name=return 
type=xs:string /
/xs:sequence
/xs:complexType
xs:complexType name=processPASLoadStatus
xs:sequence
xs:element minOccurs=0 name=arg0 
type=xs:string /
/xs:sequence
/xs:complexType
xs:complexType name=processPASLoadStatusResponse
xs:sequence /
/xs:complexType
xs:element name=Exception type=tns:Exception /
xs:complexType name=Exception
xs:sequence
xs:element minOccurs=0 
name=message type=xs:string /
/xs:sequence
/xs:complexType
/xs:schema
/wsdl:types
wsdl:message name=processClient
wsdl:part element=tns:processClient 
name=parameters/wsdl:part
/wsdl:message
wsdl:message name=processPASLoadStatus
wsdl:part element=tns:processPASLoadStatus
name=parameters/wsdl:part
/wsdl:message
wsdl:message name=processClientResponse
wsdl:part element=tns:processClientResponse
name=parameters/wsdl:part
/wsdl:message
wsdl:message name=Exception
wsdl:part element=tns:Exception name=Exception/wsdl:part
/wsdl:message
wsdl:message name=processPASLoadStatusResponse
wsdl:part element=tns:processPASLoadStatusResponse
name=parameters/wsdl:part
/wsdl:message
wsdl:portType name=PasApplicationAdapterService
wsdl:operation name=processClient
wsdl:input message=tns:processClient
name=processClient/wsdl:input
wsdl:output message=tns:processClientResponse
name=processClientResponse/wsdl:output
wsdl:fault message=tns:Exception 
name=Exception/wsdl:fault
/wsdl:operation
wsdl:operation name=processPASLoadStatus
wsdl:input message=tns:processPASLoadStatus
name=processPASLoadStatus/wsdl:input
wsdl:output message=tns:processPASLoadStatusResponse

name=processPASLoadStatusResponse/wsdl:output
wsdl:fault message=tns:Exception 
name=Exception/wsdl:fault
/wsdl:operation
/wsdl:portType
wsdl:binding name=PasApplicationAdapterServiceServiceSoapBinding
type=tns:PasApplicationAdapterService
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http; /
wsdl:operation name=processClient
soap:operation soapAction= style=document /
wsdl:input name=processClient
soap:body use=literal /
/wsdl:input
wsdl:output name=processClientResponse
soap:body use=literal /
/wsdl:output
wsdl:fault name=Exception
soap:fault name=Exception use=literal /
/wsdl:fault

Re: cxfEndpoints and different transports (http, https) using PAX Web

2012-07-20 Thread Scott England-Sullivan
Lars,

I created an example project that can be reviewed here:
https://github.com/sully6768/camel-sandbox/tree/trunk/examples.  It uses
the latest Fuse ESB 4.4.1 if you want to try it out.  There is a small
write up under the proxy project.  Both projects are required though if you
want to actually deploy it and test it.  Otherwise glean what you can from
it.

Regards,
Scott ES

On Thu, Jul 19, 2012 at 2:07 PM, helander leh...@gmail.com wrote:

 Hi Scott, and thank you very much for the information you provided so far.
 I am looking forward for the additional details you so kindly intended to
 provide.

 However at this point I do not understand how this will going to solve my
 requirements, but maybe that will be totally clear when you provide some
 more details

 Thanks

 Lars

 --
 View this message in context:
 http://camel.465427.n5.nabble.com/cxfEndpoints-and-different-transports-http-https-using-PAX-Web-tp5716216p5716263.html
 Sent from the Camel - Users mailing list archive at Nabble.com.




-- 
-- 
Scott England-Sullivan
--
FuseSource
Web: http://www.fusesource.com
Blog: http://sully6768.blogspot.com
Twitter: sully6768


Custom component query

2012-07-20 Thread gilboy
Hi

I need to create an event driven custom component. 

The sender which invokes the event driven consumer is a spring managed bean.
My custom component consumer is not spring managed as this is obviously
created from my endpoint which acts as a factory for my producers and
consumers. 

Hence, I am a little confused as to how the sender gets wired up to the
consumer as one is created via spring(sender) and the consumer is created
via my custom endpoint

Thanks!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Custom-component-query-tp5716302.html
Sent from the Camel - Users mailing list archive at Nabble.com.


Re: Custom component query

2012-07-20 Thread Doug Douglass
Camel Proxy[1] describes several ways of wiring things up (and links to
others) depending our your needs.

[1] http://camel.apache.org/using-camelproxy.html

On Fri, Jul 20, 2012 at 4:09 PM, gilboy josephoto...@gmail.com wrote:

 Hi

 I need to create an event driven custom component.

 The sender which invokes the event driven consumer is a spring managed
 bean.
 My custom component consumer is not spring managed as this is obviously
 created from my endpoint which acts as a factory for my producers and
 consumers.

 Hence, I am a little confused as to how the sender gets wired up to the
 consumer as one is created via spring(sender) and the consumer is created
 via my custom endpoint

 Thanks!



 --
 View this message in context:
 http://camel.465427.n5.nabble.com/Custom-component-query-tp5716302.html
 Sent from the Camel - Users mailing list archive at Nabble.com.



Re: Camel ActiveMQ consumers do not consume after restart

2012-07-20 Thread Christian Müller
Which version of Camel and ActiveMQ do you use?
Which MEP do you use?

Best,
Christian

Sent from a mobile device
Am 20.07.2012 16:26 schrieb Marco Zapletal marco.zaple...@gmail.com:

 Hi folks,

 We have an application where we have two Camel contexts (C1, C2) which
 exchange messages via two queues (Q1, Q2). These queues are located on the
 same ActiveMQ broker. Thereby, the message flow goes as follows:

 C1 - Q1 - C2
 C2 - Q2 - C1

 C2 uses furthermore some internal queues on the AMQ broker, but I guess
 they are not relevant to the problem.

 The issue we are facing can be described as follows and happens only when
 C1 or C2 go down or have to be restarted

 - In case, no messages are produced of either C1/C2 while the other one
 restarts, everything is fine - i.e., there is no problem with consuming
 messages

 - In case, messages are produced of either C1/C2 and are put in the
 respective queue, during the absence of the other Camel application, we
 gonna face problems with consuming messages from the queues.
 We have especially tested this scenario by stopping C2. C1 produces
 messages to Q1. Then we restart C2 again and (almost) nothing happened.

 - By almost I mean, that the context of C2 starts up without errors. What
 is also observed is that when we have 1 concurrentConsumer defined in the
 AMQ consumer configuration in C2, 1 message is consumed (if 3
 concurrentConsumers are defined, 3 messages are consumed). Afterwards,
 consumption stops.

 - When restarting C2 again, 1 message is consumed from Q1 (in case of 1
 concurrentConsumer)

 - C2 exposes also two CXF services as producers of routes. Both of the two
 routes have one of those internal AMQ queues as their final destination.
 When we want to access their respective WSDL URL, the request hangs.

 - We have an admin Web application monitoring C2 via JMX. The admin
 application hangs due to no response from C2's JMX services (although the
 C2 context starts up properly according to the logs).

 - Nothing special can be seen in the logs. We examined the logs on DEBUG
 level (on Camel as well as on AMQ side) and nothing special could be seen.

 - We went back to a rather base config. No transactions, no connection
 pools, no caching of consumers/producers. We have experimented with the
 prefetch (setting it to 1 or even 0) without success.

 - In order to reach proper behavior again, Q1/Q2 (and maybe even the
 internal queues of C2) have to be purged. Then C2 has be to be restarted
 again. After this procedure, message passing is back to normal.


 Sorry for the long post, but I want to describe the problem as detailed as
 possible. Since we have been working on this now for days any help would be
 highly appreciated.


 Thanks and best regards,


 Marco