spring-jms

Our system will not shutdown when a "Stop" command is issued from the Tomcat Manager. I have determined that it is related to ActiveMQ/Spring. I have even figured out how to get it to shutdown, however my solution is a hack (at least I hope this isn't the "correct" way to do it). I would like to know the proper way to shutdown ActiveMQ so that I can remove my hack. I inherited this component and I have no information about why certain architectural decisions were made, after a lot of digging I think I understand his thoughts, but I could be missing something. In other words, the real problem

I am trying to setup spring-web to connect to remote Jboss-7.1.1 HornetQ JMS by following this site. But I am getting below error, is there anything I need to add the spring-bean configuration. The current spring-web runs on tomcat. spring-bean.xml <?xml version="1.0" encoding="UTF-8"?> <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:jms="http://www.springframework.org/schema/jms" xmlns:p="http://www.springframework.org/schema/p" xmlns:jee="http://www.springframework.org/schema/jee" xsi:schemaLocation="http://www

I have configured CachingConnectionFactory that wraps a MQTopicConnectionFactory and MQQueueConnectionFactory with cache size set to 10 each. These are than used in several jms:outbound-channel-adapter or jms:message-driven-channel-adapter as part of various spring integration workflows that I have in my application. It is noticed that once in a while the connection count on MQ channel reaches maximum allowed (about 1000) when the process stops functioning. This is a serious problem for a production application. Bringing the application down does not reduce the connection count so looks like

What are the advantages of using DefaultJmsListenerContainerFactory over DefaultMessageListenerContainer ? If i configure DMLC directly , i do get a handle to check the status by calling isRunning() . Also i do get a facility to start and stop the DMLC However, per new spring specs, if i configure DefaultJmsListenerContainerFactory , i do not get handle of DMLC, so i am unable to do any of above operations. So looking at above limitation, can somebody explain why one should use DefaultJmsListenerContainerFactory over DMLC Also, if i use DefaultJmsListenerContainerFactory , what are the ways to

I want to write test for something like below; There is a listener called state-info-1 in src/main . It does some changes to any message it gets and publishes the new message on activemq topic state-info-2 . I will build a dummy message and publish on to activemq topic state-info-1 . Finally verify that, the received message on topic state-info-2 is like i expected. My Listeners are like; @JmsListener(destination = "state-info-1", containerFactory = "connFactory") public void receiveMessage(Message payload) { // Do Stuff and Publish to state-info-2 } Is it possible i can write test for this?

In the following test I'm trying to simulate the following scenario: A message queue is started. A consumer designed to fail during message processing is started. A message is produced. The consumer starts processing the message. During processing an exception is thrown to simulate message processing failure. The failing consumer is stopped. Another consumer is started with the intent to pick up the redelivered message. But my test fails and the message is not redelivered to the new consumer. I'll appreciate any hints on this. MessageProcessingFailureAndReprocessingTest.java