JavaWorld
addict
Reged: 06/20/03
Posts: 482
|
|
Improve availability in Java enterprise applications
|
clukasik
stranger
Reged: 12/27/05
Posts: 1
|
|
If you're using JBoss as your app server, the JBossCache can be used to replicate serializable objects across your JBoss cluster. Even if you're not using JBoss as an app server, the JBossCache can be used as a "stand-alone." We're using it to cache and replicate session information. We have a separate cache setup with different replication rules for caching commonly requested objects.
|
Anonymous
Unregistered
|
|
i think simply serializing or storing session data in the database is the best approace. distributed caches can result in a serious network bottleneck given that session data changes rapidly and large numbers of session objects must be synchronized across the network. distributed caches also results in a less scalable application.
|
Anon-Harish
Unregistered
|
|
Storing session data in the db may cause issues if session affinity is on on the web servers.The WLM would try to send the request to the same app server.
|
Anonymous
Unregistered
|
|
I cannot make much out from having RMI as a solution for distributing cache across JVM's.
What is the JVM which is hosting RMI fails, what will happen to the cache.
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
