geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Created] (GEODE-122) Suspect string from ClientServerFunctionExecutionDUnitTest.testServerExecution_SocketTimeOut_WithoutRegister
Date Wed, 15 Jul 2015 18:14:04 GMT
Dan Smith created GEODE-122:
-------------------------------

             Summary: Suspect string from ClientServerFunctionExecutionDUnitTest.testServerExecution_SocketTimeOut_WithoutRegister
                 Key: GEODE-122
                 URL: https://issues.apache.org/jira/browse/GEODE-122
             Project: Geode
          Issue Type: Bug
            Reporter: Dan Smith
            Priority: Minor


I hit this when running tests on my machine. The odd thing is that it looks like this function
should return a result unless it throws an exception. Maybe the thread is getting interrupted?
The distributed system is shut down before this warning shows up.

{noformat}
java.lang.AssertionError: Suspicious strings were written to the log during this run.
Fix the strings or use DistributedTestCase.addExpectedException to ignore.
-----------------------------------------------------------------------
Found suspect string in log4j at line 382

com.gemstone.gemfire.cache.execute.FunctionException: The function, executeFunctionHAOnServer,
did not send last result


[vm_2][info 2015/07/14 18:34:54.699 PDT <RMI TCP Connection(36)-10.118.33.109> tid=0xf40]
Marking DistributionManager gluon(11892)<v803>:14472 as closed.
[vm_2]
[vm_2][info 2015/07/14 18:34:54.700 PDT <RMI TCP Connection(36)-10.118.33.109> tid=0xf40]
Got result: null
[vm_2] from com.gemstone.gemfire.cache30.CacheTestCase.remoteTearDown with 0 args (took 29616
ms)
[vm_2]
[vm_2][warn 2015/07/14 18:34:54.700 PDT <ServerConnection on port 26766 Thread 2> tid=0x1cd3]
Exception on server while executing function: com.gemstone.gemfire.internal.cache.functions.TestFunction@3173a08a
[vm_2]com.gemstone.gemfire.cache.execute.FunctionException: The function, executeFunctionHAOnServer,
did not send last result
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.command.ExecuteFunction66.executeFunctionaLocally(ExecuteFunction66.java:330)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.command.ExecuteFunction66.cmdExecute(ExecuteFunction66.java:250)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.command.ExecuteFunction70.cmdExecute(ExecuteFunction70.java:51)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.BaseCommand.execute(BaseCommand.java:182)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doNormalMsg(ServerConnection.java:787)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.doOneMessage(ServerConnection.java:914)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.ServerConnection.run(ServerConnection.java:1159)
[vm_2]	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[vm_2]	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[vm_2]	at com.gemstone.gemfire.internal.cache.tier.sockets.AcceptorImpl$1$1.run(AcceptorImpl.java:580)
[vm_2]	at java.lang.Thread.run(Thread.java:745)
{noformat}






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message