Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revert "Fix issue relate with CollectionUsageThreshold of memory pool" #3308

Merged
merged 1 commit into from
Oct 16, 2018

Conversation

gacholio
Copy link
Contributor

@gacholio gacholio commented Oct 16, 2018

Reverts #2993

since the change was causing test failures

j> 14:09:22 Exception in thread "MemoryMXBean notification dispatcher" java.lang.IllegalArgumentException: committed value cannot be larger than the max value
j> 14:09:22 	at java.lang.management.MemoryUsage.<init>(MemoryUsage.java:118)
j> 14:09:22 	at com.ibm.lang.management.internal.ExtendedGarbageCollectorMXBeanImpl.buildGcInfo(ExtendedGarbageCollectorMXBeanImpl.java:94)
j> 14:09:22 	at com.ibm.lang.management.internal.MemoryNotificationThread.dispatchGCNotificationHelper(MemoryNotificationThread.java:95)
j> 14:09:22 	at com.ibm.lang.management.internal.MemoryNotificationThread.processNotificationLoop(Native Method)
j> 14:09:22 	at com.ibm.lang.management.internal.MemoryNotificationThread.run(MemoryNotificationThread.java:183)

@gacholio gacholio merged commit ac41290 into master Oct 16, 2018
@gacholio gacholio deleted the revert-2993-issue2982 branch October 16, 2018 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants