CODEWITHSUNDEEP
javaapache-camelactivemq-classicapache-servicemix
Jonathan Anctil
Jonathan Anctil

Reputation: 1037

javax.jms.IllegalStateException: The Session is closed

I have different problems with a Camel Producer that I tried to solved but I've fallen into other problems.

1) The first implementation I did was to create a producer template each time we needed to communicate with an ActiveMQ topic. That resulted with poor memory results leading to server crashing after sometime.

The solution for the memory problem was to stop() producer template after each request. That fix has corrected the memory issue but cause some latency problem.

2) I read somewhere that it's not necessary to create each time a producer template. So I decide to fix the latency problem and declared only one producer template in my class and use it for each request. It seem to work fine, no memory leak, fix the latency problem...

BUT, when we send multiple queries that take a lot of time (20 sec each), it looks like we hit a timeout and the component crash with something like «javax.jms.IllegalStateException: The Session is closed».

Is there a way to do multi threading? Is this cause by using InOut exchange pattern? How the MAXIMUM_CACHE_POOL_SIZE works? Is my implementation is right?

I've put a sample of the code of my component:

public void process(Exchange exchange) throws Exception 
{        
    Message in = exchange.getIn(); 

    if (producerTemplate == null) {            
        CamelContext camelContext = exchange.getContext();
        //camelContext.getProperties().put(Exchange.MAXIMUM_CACHE_POOL_SIZE, "50");
        producerTemplate = camelContext.createProducerTemplate();
    }

    ...
    result = producerTemplate.sendBody(String.format("activemq:%s", camelContext.resolvePropertyPlaceholders("{{channel1}}")), ExchangePattern.InOut, messageToSend).toString(); 

    ...
    finalResult = producerTemplate.sendBody(String.format("activemq:%s", camelContext.resolvePropertyPlaceholders("{{channel2}}")), ExchangePattern.InOut, result).toString(); 

    ...
    in.setBody(finalResult );
}

Upvotes: 1

Views: 16375

Answers (1)

johan
johan

Reputation: 548

Yes it is because you use InOut pattern. Your route expects a response to the specified reply queue, which is never received, and therefore results in the default 20 sec. timeout.

Change the Exchange pattern to InOnly to resolve your issue.

Apart from that, your posted code seems to be fine. The MAXIMUM_CACHE_POOL_SIZE is used internally in Camel, and thus does not effect the ActiveMQ endpoint settings.

Upvotes: 1

Related Questions