[GEODE-1097] allow Lambda invocations to be named so that they show up in test logs

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.0.0-incubating.M2
• Component/s: tests
• Assignee: Bruce J Schuchardt
• Reporter: Bruce J Schuchardt
• Created: 14/Mar/16 22:51
• Updated: 12/Apr/16 05:59
• Resolved: 15/Mar/16 18:00

Description

Currently lambda invocations are logged like this:

[vm_1][info 2016/03/14 10:17:04.395 PDT <RMI TCP Connection(1)-10.118.33.195> tid=0x14] Received method: com.gemstone.gemfire.test.dunit.DurableClientSimpleDUnitTest$$Lambda$5/1964980796.run with 0 args on object: com.gemstone.gemfire.test.dunit.DurableClientSimpleDUnitTest$$Lambda$5/1964980796@5e43dcd9

It would be helpful to be able to have more context than this logged, such as

[vm_0][info 2016/03/14 15:30:36.314 PDT <RMI TCP Connection(1)-10.118.33.195> tid=0x14] Received method: com.gemstone.gemfire.test.dunit.NamedCallable.call with 0 args on object: callable(getTestGetNotifiedClients_port)

so that we can tell what the Lambda is doing.