Elements cannot be written to disk store because the spool thread has died (Doc ID 1956469.1)

Last updated on NOVEMBER 03, 2016

Applies to:

Oracle WebCenter Sites - Version 11.1.1.6.1 and later
Information in this document applies to any platform.

Symptoms

After getting an out of memory exception in WebLogic:
2014-12-15 08:27:00,607 INFO [org.jasig.cas.services.DefaultServicesManagerImpl] -
Exception in thread "RMI TCP Connection(5728)-10.5.80.18" Exception in thread "scheduler_QuartzSchedulerThread" java.lang.OutOfMemoryError: getNewTla
at java.lang.String.toCharArray(String.java:2725)
at java.lang.Thread.setName(Thread.java:1094)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:651)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
java.lang.OutOfMemoryError: getNewTla
at org.quartz.Trigger.getFullName(Trigger.java:435)
at org.quartz.simpl.TriggerComparator.compare(RAMJobStore.java:1408)
at java.util.TreeMap.cmp(TreeMap.java:2273)
at java.util.TreeMap.remove(TreeMap.java:2815)
at java.util.TreeSet.remove(TreeSet.java:259)
at org.quartz.simpl.RAMJobStore.acquireNextTrigger(RAMJobStore.java:1144)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)


The following message is repeating in the logs:
Dec 15, 2014 8:28:31 AM net.sf.ehcache.store.DiskStore put
SEVERE: pageByQryCache: Elements cannot be written to disk store because the spool thread has died.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms