Hide Forgot
project_key: SOA Intermittently, we get the stack overflow error. It doesn't seem to be related to the query. java.lang.StackOverflowError at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164) at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119) at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36) at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86) at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411) at java.util.LinkedHashMap.put(LinkedHashMap.java:370) at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164) at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119) at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36) at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86) at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411) at java.util.LinkedHashMap.put(LinkedHashMap.java:370) at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164) at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119) at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36) at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86) at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411) at java.util.LinkedHashMap.put(LinkedHashMap.java:370) at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164) at org.teiid.cache.DefaultCache.validate(DefaultCache.java:119) at org.teiid.cache.DefaultCache.access$000(DefaultCache.java:36) at org.teiid.cache.DefaultCache$1.removeEldestEntry(DefaultCache.java:86) at java.util.LinkedHashMap.putImpl(LinkedHashMap.java:411) at java.util.LinkedHashMap.put(LinkedHashMap.java:370) at org.teiid.cache.DefaultCache.remove(DefaultCache.java:164)
Link: Added: This issue Cloned from TEIID-1492
Security: Added: Public
Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://issues.jboss.org/browse/TEIID-1492 Users would encounter a stack overflow error: java.lang.StackOverflowError. This was caused by a bug in the entry removal code. This code has now been rectified, so users will no longer see this problem. The expiration queue logic was updated at the same time to ensure that it is properly bounded.