Re: [eclipselink-users] Message Persistence for JMS Coordinated Cache

["Dave Muirhead" <dmuirhead@xxxxxxxxx>]

Hi Gordon-

Thank you for addressing my question.

My interpretation of your answer is that there is no particular benefit to using persistent JMS messages with Top/EclipseLink clustering.

For the benefit of those who might have the same question in the future and happen across this thread, would you please provide confirmation that this is in fact your guidance.

Thanks much,

Dave

On Thu, Nov 13, 2008 at 5:49 AM, Gordon Yorke <gordon.yorke@xxxxxxxxxx> wrote:

Hello Dave,
    If the JMS service fails you can assume that the cached objects will continue to be updated through normal application operation making the messages corresponding to those objects useless.  The longer the service is down the less useful the messages would be.
--Gordon

Dave Muirhead wrote:

When setting up an EclipseLink JMS Coordinated Cache, is it recommended to configure the JMS provider to use message persistence or not?

On one hand, it doesn't seem like message persistence would terribly beneficial, since newly started VMs would have no need to see cache modifications that occurred in the past. On the other hand, I can see wanting to preserve messages in the event the JMS provider fails.

Thanks in advance,

Dave

--

==========
Dave Muirhead
dmuirhead@xxxxxxxxx

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
  

_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users

-- 

==========
Dave Muirhead
dmuirhead@xxxxxxxxx