Here's my scenario:
I've configured a messageStore in my WSO2 esb 4.8.1 as follow:
<messageStore class="org.apache.synapse.message.store.impl.jms.JmsStore" name="JMSTest">
<parameter name="java.naming.factory.initial">org.apache.qpid.amqp_1_0.jms.jndi.PropertiesFileInitialContextFactory</parameter>
<parameter name="java.naming.provider.url">repository/conf/jms-jndi.properties</parameter>
<parameter name="store.jms.connection.factory">JMSMS</parameter>
<parameter name="store.jms.JMSSpecVersion">1.1</parameter>
<parameter name="store.jms.destination">QUEUE</parameter>
</messageStore>
I followed the configuration indicated by this official tutorial to connect the queue.
The first time a sequence tries to store a message using this store, an error is raised and the message is ignored.
[JMSTest-P-1]. Ignored MessageID : urn:uuid:414f50a0-91d2-4bdf-937b-cc283985c947 [JMSTest-P-1] cannot proceed. Message producer is null.
If I try to store a message during the next 5 minutes, the store will work. But after this kind of timeout the same error will by triggered if I try to store a message.
I've tried to add the store.jms.cache.connection
parameter to false
, and the transport.jms.CacheLevel
parameter to None
by editing the sourceView
in the admin console, but these parameters are erased if I modify the configuration in the MessageStore tab thus I am not on that they are really used.
Have you an idea towards which look to make so that the messageStore is active all the time?
Thank you for all the answers