Thanks, Claus, for your feedback.
1. The AMQ is embedded to WebSphere 8.0.0.5, AMQ version is 5.7.0.
2. Here is the code, nothing special, just a Request-Reply on Camel:
JmsComponent jms =
JmsComponent.jmsComponentAutoAcknowledge(connectionFactory);
camelContext.addComponent("jms", jms);
final JmsEndpoint requestQueueEndpoint = (JmsEndpoint)
jms.createEndpoint("requestqueue?maxConcurrentConsumers=10");
requestQueueEndpoint.setDestinationName(configManagementService.getRequestQueue());
requestQueueEndpoint.setReplyTo(configManagementService.getResponseQueue());
...
Exchange exc = producer.createExchange();
exc.getIn().setBody(message); // message is of String type
exc.setPattern(ExchangePattern.InOut);
try {
//send request and wait for response
producer.process(exc);
} catch (Exception excep) {
LOG.error("Error occurred during camel route processing.",
excep);
}
String responseJson = exc.getOut().getBody(String.class);
Actualy, I don't think, that problem is in Camel, because it works fine with
a standalone AMQ - the problem is only with an embedded AMQ.
3. Request and reply queues are names queues.
4. The client and a server locates on the same host, so there is no problem
in the time synchronization. Evenmore, the custom logging is enabled and I'm
able to see, that message comes to request, reply queues or DLQ.
I definitelly think, that the problem is in a persistence to the disk. When
the problem occurs, there is no other way to solve it, except the removing
of the kahadb folder.
I just wonder, if somebody else was facing such a problem and has a right
solution for this case.
Thanks in advance for your response :)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Camel-and-Embedded-AMQ-Problem-consuming-from-a-queue-tp4671434p4671471.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
