[
https://issues.apache.org/jira/browse/GEODE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639515#comment-14639515
]
Darrel Schneider commented on GEODE-143:
----------------------------------------
The above checkin will prevent debug level logging from deserializing the value
in the cache.
I don't know why this started happening with our apache geode jenkins builds.
It is not happening with our other jenkins builds.
> PdxDeserializationDUnitTest and PdxClientServerDUnitTest failing because
> debug level logging left enabled by previous test
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-143
> URL: https://issues.apache.org/jira/browse/GEODE-143
> Project: Geode
> Issue Type: Bug
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> PdxDeserializationDUnitTest and PdxClientServerDUnitTest started failing in
> this build: https://builds.apache.org/job/Geode-nightly/159/testReport/junit/
> The PdxDeserializationDUnitTest is failing for sure because a previous test
> left the log-level set to debug. This causes a debug level log message to
> deserialize the value for logging which causes this test to fail with:
> Caused by: com.gemstone.gemfire.SerializationException: Deserialization
> should not be happening in this VM
> I think the PdxClientServerDUnitTest is also caused by this because it is
> failing because it see a domain class instance and expect a PdxInstance.
> Two things need to be done to fix this ticket:
> 1. determine what test is leaving the log-level at debug/fine and fix it.
> 2. change the product to tolerate not being able to deserialize a value when
> it is being done for a log statement. Also logging should not cause the form
> stored in a VMCachedDeserializable to change from serialized to deserialized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
