On 1/16/07, magic.moose <[EMAIL PROTECTED]> wrote:
thank you, you're right, I forgot to turn the persistance off. Anyway, vm://localhost?broker.persistent=false disables persistance, no more db (derby?) is used, no ddl executed. Is there something more I can do about that?
Your producer really should specify the DeliveryMode of NON_PERSISTENT. Setting the broker to persistent=false just makes it use a VM (RAM) based persistence implementation, not to disable persistence per se. i.e. it means don't use JDBC or the journal.
I thought that maybe JmsTemplate overides global connectionFactory setting for each send and so I set deliveryPersistent to false.
Yes, the delivery mode is set on the producer (which JmsTemplate creates)
Still, I got the same serialization exception when Activemq tries to storeContent. any clue?
Do you have a full stack trace? I'm not sure how easy its gonna be to never, ever, try to persist the message to some file at some point (e.g. if the broker is running low on RAM it can spool messages to disk) - so a more JMS-complaint solution to your problem might be to implement Externalizable or something. -- James ------- http://radio.weblogs.com/0112098/
