You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Eric Shu (Jira)" <ji...@apache.org> on 2019/08/22 17:13:00 UTC
[jira] [Assigned] (GEODE-7114) CI failure:
TransactionTimeOutDUnitTest.test4 is flaky
[ https://issues.apache.org/jira/browse/GEODE-7114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Shu reassigned GEODE-7114:
-------------------------------
Assignee: Eric Shu
> CI failure: TransactionTimeOutDUnitTest.test4 is flaky
> ------------------------------------------------------
>
> Key: GEODE-7114
> URL: https://issues.apache.org/jira/browse/GEODE-7114
> Project: Geode
> Issue Type: Bug
> Components: transactions
> Reporter: Eric Shu
> Assignee: Eric Shu
> Priority: Major
>
> This test is flaky, as test may be timed out later than expected due to resources constraints during the test run.
> [vm0] [info 2019/08/21 00:24:49.917 GMT <GlobalTXTimeoutMonitor> tid=0xcc] Transaction org.apache.geode.internal.jta.GlobalTransaction@15e9a353 has timed out.
> [vm0] [warn 2019/08/21 00:24:49.752 GMT <StatSampler> tid=0xca] Statistics sampling thread detected a wakeup delay of 3895 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
> [vm0] [info 2019/08/21 00:24:50.818 GMT <RMI TCP Connection(1)-172.17.0.4> tid=0x20] Got result: EXCEPTION_OCCURRED
> [vm0] java.lang.AssertionError: TimeOut did not rollback the transaction
> [vm0] at org.junit.Assert.fail(Assert.java:88)
> [vm0] at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.runTest6(TransactionTimeOutDUnitTest.java:312)
> [vm0] at org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest.lambda$test4$bb17a952$1(TransactionTimeOutDUnitTest.java:166)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [vm0] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at org.apache.geode.test.dunit.internal.MethodInvoker.executeObject(MethodInvoker.java:123)
> [vm0] at org.apache.geode.test.dunit.internal.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:69)
> [vm0] at sun.reflect.GeneratedMethodAccessor53.invoke(Unknown Source)
> [vm0] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [vm0] at java.lang.reflect.Method.invoke(Method.java:498)
> [vm0] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:200)
> [vm0] at sun.rmi.transport.Transport$1.run(Transport.java:197)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> [vm0] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:573)
> [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:834)
> [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:688)
> [vm0] at java.security.AccessController.doPrivileged(Native Method)
> [vm0] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:687)
> [vm0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm0] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm0] at java.lang.Thread.run(Thread.java:748)
> [vm0] from org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748.run with 0 args on object: org.apache.geode.internal.jta.dunit.TransactionTimeOutDUnitTest$$Lambda$189/1487881748@5060d4ee (took 7958 ms)
> [locator] [warn 2019/08/21 00:24:50.140 GMT <StatSampler> tid=0x3a] Statistics sampling thread detected a wakeup delay of 3777 ms, indicating a possible resource issue. Check the GC, memory, and CPU statistics.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)