RE: [openjms-user] For OpenJMs Developers : OpenJMS Performance with Persistent Messages and Durable subscribers..

Not a good idea. If the server goes down after the message
has been published to active subscribers, but before it is
made persistent, you will end up with inconsistency.
You would also have to add some synchronization to ensure
that acknowledgements for a message don't occur before the
message is made persistent.


> -----Original Message-----
> From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> [mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org]On Behalf Of Sanjeev
> Aggarwal
> Sent: Friday, 27 June 2003 8:12 PM
> To: [email protected]; [email protected]
> Cc: [email protected]
> Subject: [openjms-user] For OpenJMs Developers : OpenJMS Performance
> with Persistent Messages and Durable subscribers..
>
>
> Hi,
>
> I am using Persistent messages and Durable subscribers on Topics. I looked
> into the OpenJMS Code. Found that it is saving the JMSMessage into the
> database before publishing it to subscribers.
>
> Can I change it, in a way that message is published to
> subscribers and then
> saved in the database in a seperate thread so that subscribers
> gets a faster
> delivery of messages.
>
> Thanks,
> Sanjeev.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: INetU
> Attention Web Developers & Consultants: Become An INetU Hosting Partner.
> Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
> INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
> _______________________________________________
> openjms-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openjms-user
>