[
https://issues.apache.org/jira/browse/GEODE-6247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-6247.
------------------------------
Resolution: Fixed
Fix Version/s: 1.9.0
Fixed by GEODE-6253
> HostStatSampler posts suspect string stemming from native code in JDK11,
> causing failure in NetstatDUnitTest
> -------------------------------------------------------------------------------------------------------------
>
> Key: GEODE-6247
> URL: https://issues.apache.org/jira/browse/GEODE-6247
> Project: Geode
> Issue Type: Bug
> Reporter: Patrick Rhomberg
> Assignee: Scott Jewell
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> In JDK11 run
> https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK11/builds/278:
> {noformat}
> org.apache.geode.management.internal.cli.NetstatDUnitTest > classMethod FAILED
> java.lang.AssertionError: Suspicious strings were written to the log
> during this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 2183
> [fatal 2019/01/04 00:15:19.050 UTC <StatSampler> tid=67] committed =
> 538968064 should be < max = 536870912
> java.lang.IllegalArgumentException: committed = 538968064 should be < max
> = 536870912
> at
> java.management/java.lang.management.MemoryUsage.<init>(MemoryUsage.java:166)
> at java.management/sun.management.MemoryImpl.getMemoryUsage0(Native
> Method)
> at
> java.management/sun.management.MemoryImpl.getHeapMemoryUsage(MemoryImpl.java:71)
> at
> org.apache.geode.internal.stats50.VMStats50.refresh(VMStats50.java:624)
> at
> org.apache.geode.internal.statistics.HostStatSampler.sampleSpecialStats(HostStatSampler.java:562)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:235)
> at java.base/java.lang.Thread.run(Thread.java:834)
> -----------------------------------------------------------------------
> Found suspect string in log4j at line 2193
> [fatal 2019/01/04 00:15:19.055 UTC <StatSampler> tid=67] Uncaught
> exception in thread Thread[StatSampler,10,RMI Runtime]
> java.lang.IllegalArgumentException: committed = 538968064 should be < max
> = 536870912
> at
> java.management/java.lang.management.MemoryUsage.<init>(MemoryUsage.java:166)
> at java.management/sun.management.MemoryImpl.getMemoryUsage0(Native
> Method)
> at
> java.management/sun.management.MemoryImpl.getHeapMemoryUsage(MemoryImpl.java:71)
> at
> org.apache.geode.internal.stats50.VMStats50.refresh(VMStats50.java:624)
> at
> org.apache.geode.internal.statistics.HostStatSampler.sampleSpecialStats(HostStatSampler.java:562)
> at
> org.apache.geode.internal.statistics.HostStatSampler.run(HostStatSampler.java:235)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
> Test report at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.320/test-results/distributedTest/1546563376/
> Artifacts at:
> http://files.apachegeode-ci.info/builds/apache-develop-main/1.9.0-build.320/test-artifacts/1546563376/distributedtestfiles-OpenJDK11-1.9.0-build.320.tgz
> This appears to be identical to the failure in GEODE-6046.
> We note that the difference in reported values is exactly 2MB.
> We note additionally that the suspect string itself appears during the
> class-rule startup, but before any class test is executed.
> Also possibly related to GEODE-6079, regarding how logs are written and the
> possibility of buffers not flushing properly before suspect strings are
> detected. It is not obvious that this suspect string failure does not truly
> belong to another test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
