Have to admit I'm pretty new to this and inherited the project that we have.
This is how my jms template is setup, looks like I don't use transactions
and auto ack, since that's the default.
<bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory" ref="connectionFactory"/>
<property name="sessionTransacted" value="false"/>
<property name="receiveTimeout" value="5000"/>
</bean>
The consumers use this interface MessageListener and override onMessage.
Using this code to send to the next Queue, I have 4 Queues.
final Article msgArticle = article;
jmsTemplate.send(this.destination, new MessageCreator() {
@Override
public Message createMessage(Session session) throws
JMSException {
logger.info("finish saving article, send out article for
next step");
ObjectMessage msg = session.createObjectMessage();
msg.setObject(msgArticle);
return msg;
}
});
Does that sound like a reasonable approach ?
Any other information you would want me to provide ?
Thanks,
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Memory-limit-reached-tp4700568p4700602.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.