DefaultMessageListenerContainer not shutting down

[alvins]

I know there have been other threads about this but none which have helped. I am using tomcat, activemq and using an Message driven pojo via DefaultMessageListenerContainer.

Everything is fine except that tomcat does not shutdown gracefully (the process hangs). If I remove the MDP from spring config everything works fine which means it is definately the MDP hence DefaultMessageListenerContainer. From my debugging I can see that the MDP thread is still hanging around while all most other tomcat threads have stopped.

Has anyone come across this and/or solved it?

[Lyserg]

Hello,

do you use the Webapplicationcontext with a ServletContextListener in your enviroment ?
Normally when the applicationcontext stops, the defaultmesaagelistenercontainer also stops.

Regards
agim

[alvins]

Not sure what you mean - but in my web.xml I have the following -

<!-- Listeners -->
<listener>
<listener-class>org.springframework.web.context.ContextLoade rListener</listener-class>
</listener>

I can see in the logs that it tries to shutdown but the process doesn't die it seems.

[springmk]

Did you try Spring 2.0.4 and above?

[barathwajram]

Its a guess. Think through this.

ContextLoaderListener - is an implementation to load the spring context via the web.xml. But it may not be the responsibility of the web container to call the close() or destroy() method on the ApplicationContext that was created by the web container. I dont think it's happening. So you may need to grab the Application context being in a ServletContextListener.destroy() and call applicationContext.close() method. Hopefully that will bring down your Spring beans and will fire the destroy methods on all spring managed beans.

Check it out.

[Lyserg]

ContextLoaderListener - is an implementation to load the spring context via the web.xml. But it may not be the responsibility of the web container to call the close() or destroy() method on the ApplicationContext that was created by the web container. I dont think it's happening.

I think you're worong, have a look at ContextLoaderLister (destroy method)

public void contextDestroyed(ServletContextEvent event) {
		if (this.contextLoader != null) {
			this.contextLoader.closeWebApplicationContext(event.getServletContext());
		}
}

closeWebbapplicationContext calls close on the applicationcontexts. So normally with the ContextLoaderListener you should be fine with the MEssageListenerContainer.


@alvins

Do you use any (custom ) receiveTimeout in your MessageListenerContainer

regards
agim

[kaushik]

Hi,
i have an application in which DefaultmessageListenerContainer starts listening on JMS and processes incomming messages.

In event of too many messages being unprocessed, i would like to shutdown my listeners until I fix the problem and then start the listeners again.

i tried using teh shutdown(0 and initialise() methods of DefaultMessageListenerContainer, but it is shutting down all my spring beans including the caller bean itself.

is tehre another way i can do this?

appreciate your help
thank you
kaushik

[Lyserg]

Hi,

i tried using teh shutdown(0 and initialise() methods of DefaultMessageListenerContainer, but it is shutting down all my spring beans including the caller bean itself.

how do you initialize the applicationcontext ?
I would suggest to use the start and stop methods for starting/stopping the defaultmessagelistenercontainer.

rgds
agim

[kaushik]

Hi,

I get the application context using ApplicationContextAwareInterface which returns me teh refeference to the original singleton bean that was defined in spring-config.xml file.

I tried using start and stop as well, but same result- all singleton's getting destroyed including my caller bean which also exists in same application context.


kaushik

[penzhengca]

just set the timeout, it will be ok.


<property name="receiveTimeout" value="300"/>