[jboss-jira] [JBoss JIRA] (WFLY-4691) "Periodic Recovery" Exception in thread "bitronix-task-scheduler" java.lang.OutOfMemoryError

[Mike Mike (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-4691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082906#comment-13082906 ] 

Mike Mike commented on WFLY-4691:
---------------------------------

I would switch to Narayana immediately, but I couldn’t find solutions for all my needs:
-	Injection of transaction manager by JNDI and supporting a programmatic solution for my Spring Context during integration test time.
-	Support of JNDI prepared real XA-Datasources and a solution for Mock XA-Datasources without container for integration test time.

A lot of tutorials promising full XA, JPA and Spring support, but in reality nothing works with all together.


> "Periodic Recovery" Exception in thread "bitronix-task-scheduler" java.lang.OutOfMemoryError
> --------------------------------------------------------------------------------------------
>
>                 Key: WFLY-4691
>                 URL: https://issues.jboss.org/browse/WFLY-4691
>             Project: WildFly
>          Issue Type: Bug
>          Components: Transactions
>    Affects Versions: 9.0.0.CR1
>            Reporter: Mike Mike
>            Assignee: Jason Greene
>
> I am using a BitronixTransactionManager with xa-data-sources. After the migration from Jboss 7.1.1.FINAL to Wildfly 9.0.0.CR I noticed the following error in the server.log:
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) Exception in thread "Periodic Recovery" Exception in thread "bitronix-task-scheduler" java.lang.OutOfMemoryError: GC overhead limit exceeded
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at java.util.Arrays.copyOf(Arrays.java:2271)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at java.io.ByteArrayOutputStream.toByteArray(ByteArrayOutputStream.java:178)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.arjuna.state.OutputBuffer.buffer(OutputBuffer.java:162)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUidsInternal(FileSystemStore.java:265)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.objectstore.FileSystemStore.allObjUids(FileSystemStore.java:160)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.arjuna.objectstore.ObjectStore.allObjUids(ObjectStore.java:69)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.jta.recovery.arjunacore.CommitMarkableResourceRecordRecoveryModule.periodicWorkSecondPass(CommitMarkableResourceRecordRecoveryModule.java:462)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:793)
> 18:09:31,064 ERROR [stderr] (Periodic Recovery) 	at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:375)
> 18:09:31,064 ERROR [stderr] (bitronix-task-scheduler) java.lang.OutOfMemoryError: GC overhead limit exceeded
> After the error, the application was still working. I don't see an effect, yet. Does anybody has seen this error before?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)