geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-143) PdxDeserializationDUnitTest and PdxClientServerDUnitTest failing because debug level logging left enabled by previous test
Date Thu, 23 Jul 2015 21:10:06 GMT

    [ https://issues.apache.org/jira/browse/GEODE-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639505#comment-14639505
] 

ASF subversion and git services commented on GEODE-143:
-------------------------------------------------------

Commit aeafb0151c28d397961a64bf9e8f9541dcb508ed in incubator-geode's branch refs/heads/develop
from [~dschneider]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=aeafb01 ]

GEODE-143: logging must not cause cached values to be deserialized

A more powerful StringUtils.forceToString now exists that will also
print out the elements of arrays. It used to just to a toString on the
array which only shows the array identity. The new code will (by default)
show the first 16 element values and after that say how many more the array
had that are not shown. If you set the sys prop StringUtils.MAX_ARRAY_ELEMENTS_TO_CONVERT
you can change the default of 16.


> 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)

Mime
View raw message