We have a need to cache frequently-used, read-mostly data in a clustered J2EE environement (using Websphere app server). The data doesn't change frequently, but when it does, we don't have the option to restart the app server to refresh the cache. I have looked at the Seppuku pattern, but, obviously, that pattern is more suitable for WebLogic applications. I also studied the A.C.E. (Active Cluster Expiry Cache) pattern, but again, this pattern requires the use of JMS for expiry logic, which unfortunately is not a viable option for us at this time. I would really appreciate it if someone can point us in the right direction here?