After further investigation, it appears that it ran out of memory and thus
had to write to disk. It is unclear why this would all of a sudden start
happening though.
These are the settings for our Shiro session cache in our ehcache.xml file:
<cache name="shiro-activeSessionCache"
maxElementsInMemory="10000"
overflowToDisk="true"
eternal="true"
timeToLiveSeconds="0"
timeToIdleSeconds="0"
diskPersistent="false"
diskExpiryThreadIntervalSeconds="600"
>
</cache>
I was contemplating turning off session caching but I believe that made the
application slower when attempted previously. Any suggestions on fine
tuning this so that I don't consistently have a huge log file?
--
View this message in context:
http://shiro-user.582556.n2.nabble.com/shiro-activeSessionCache-data-file-has-become-extremely-large-2GB-tp7579227p7579229.html
Sent from the Shiro User mailing list archive at Nabble.com.
