er level makes sense, but often the higher level
abstraction provides convenience at a small expense.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457p4715000.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
class="org.springframework.jms.core.JmsTemplate">
>
>
>
>
>
>
>
>
>
> I'm sure the OP found the same thing out years ago, but just for anyone else
> with the same problem.
>
>
>
> --
> View this message in context:
> http://activemq.
thing out years ago, but just for anyone else
with the same problem.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457p4714981.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
le.com/Non-persistent-deliverymode-not-effect-tp4680457p4680984.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
eryMode" of jmsTemplet was always "1(NON_PERSISTENT)".
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457p4680500.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
() call in the MessageProducer is getting passed
the NON_PERSISTENT flag, or at least that it's deliveryMode is in-fact set
to NON_PERSISTENT.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457p4680486.html
Sent from the
r your time.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Non-persistent-deliverymode-not-effect-tp4680457.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
