Bug 1293016 - [GSS](6.4.z) EJB Passivation can fail from StackOverflowError with no message logged
Summary: [GSS](6.4.z) EJB Passivation can fail from StackOverflowError with no message...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: CR1
: EAP 6.4.7
Assignee: Tomas Hofman
QA Contact: Jan Martiska
URL: https://github.com/jbossas/jboss-eap/...
Whiteboard:
Depends On:
Blocks: eap647-payload 1301624
TreeView+ depends on / blocked
 
Reported: 2015-12-19 07:01 UTC by Brad Maxwell
Modified: 2019-10-10 10:44 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
: 1301624 (view as bug list)
Environment:
Last Closed: 2017-01-17 12:00:13 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1268424 0 high CLOSED [GSS](6.4.z) SFSB infinite loop if Passivate fails 2021-02-22 00:41:40 UTC
Red Hat Knowledge Base (Solution) 2191891 0 None None None 2016-03-08 00:39:40 UTC

Internal Links: 1268424

Description Brad Maxwell 2015-12-19 07:01:19 UTC
The call stack is below. There are some catches in some of the calls, but none are catching any of these and logging it.  The StackOverflowError is thrown up, but PassivateTask is running in a separate thread, so it appears the exception is thrown up to the JDK classes below and is never logged.

We need to catch Throwable at some point and log a message, also need to make sure that we are taking the correct action when it occurs since it failed to passivate.

java.lang.Throwable
    java.lang.Error
        java.lang.VirtualMachineError
            java.lang.StackOverflowError

org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:262)
 	at org.jboss.as.ejb3.cache.spi.impl.FilePersistentObjectStore.store(FilePersistentObjectStore.java:57)
 	at org.jboss.as.ejb3.cache.impl.backing.SimpleBackingCacheEntryStore.passivate(SimpleBackingCacheEntryStore.java:162)
 	at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:299)
 	at org.jboss.as.ejb3.cache.impl.backing.SerializationGroupMemberContainer.passivate(SerializationGroupMemberContainer.java:51) - What is this?
 	at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:199)
 	at org.jboss.as.ejb3.cache.impl.backing.PassivatingBackingCacheImpl.passivate(PassivatingBackingCacheImpl.java:58)
 	at org.jboss.as.ejb3.cache.spi.impl.PassivateTask.run(PassivateTask.java:46)
 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 	at java.lang.Thread.run(Thread.java:744)

Comment 8 Dominik Pospisil 2016-02-16 09:26:28 UTC
dev-acking - PR ready, no upstream

Comment 9 Jiří Bílek 2016-03-03 13:02:46 UTC
Verified with EAP 6.4.7.CP.CR2.

Comment 10 Petr Penicka 2017-01-17 12:00:13 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.


Note You need to log in before you can comment on or make changes to this bug.