[jboss-jira] [JBoss JIRA] (WFLY-4691) "Periodic Recovery" Exception in thread "bitronix-task-scheduler" java.lang.OutOfMemoryError
[
https://issues.jboss.org/browse/WFLY-4691?page=com.atlassian.jira.plugin....
]
Tom Jenkinson commented on WFLY-4691:
-------------------------------------
I think you will get better input on the forum for this type of enquiry. Why can't you
use Narayana (inbuilt in WFLY) rather than BTM? I don't think the transaction manager
is easily replaced in WFLY as far as I know.
With the information you have provided it does look you may just need to increase your
memory heap, but its difficult to say. As this is not a supported feature (as far as I
know) to replace the TM I will close the issue for now, but please do feel free to raise a
forum discussion to see if others in the community can assist you with your issue.
"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)