[jira] [Work logged] (COLLECTIONS-799) UnmodifiableNavigableSet can be modified by pollFirst() and pollLast()
[
https://issues.apache.org/jira/browse/COLLECTIONS-799?focusedWorklogId=760639&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760639
]
ASF GitHub Bot logged work on COLLECTIONS-799:
--
Author: ASF GitHub Bot
Created on: 22/Apr/22 06:36
Start Date: 22/Apr/22 06:36
Worklog Time Spent: 10m
Work Description: scordio commented on PR #250:
URL:
https://github.com/apache/commons-collections/pull/250#issuecomment-1106061634
Hi @kinow and @garydgregory, anything I could do to help get this released?
Issue Time Tracking
---
Worklog Id: (was: 760639)
Time Spent: 2h (was: 1h 50m)
> UnmodifiableNavigableSet can be modified by pollFirst() and pollLast()
> --
>
> Key: COLLECTIONS-799
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-799
> Project: Commons Collections
> Issue Type: Bug
> Components: Collection, Set
>Affects Versions: 4.4
>Reporter: Stefano Cordio
>Assignee: Bruno P. Kinoshita
>Priority: Major
> Fix For: 4.5
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> [{{pollFirst()}}|https://docs.oracle.com/javase/7/docs/api/java/util/NavigableSet.html#pollFirst()]
> and
> [{{pollLast()}}|https://docs.oracle.com/javase/7/docs/api/java/util/NavigableSet.html#pollLast()]
> are successfully executed and do not throw an
> {{UnsupportedOperationException}} on an {{UnmodifiableNavigableSet}} instance.
> In my opinion,
> {{org.apache.commons.collections4.set.UnmodifiableNavigableSet}} should have
> an implementation similar to
> {{java.util.Collections.UnmodifiableNavigableSet}}, where both methods throw
> an {{UnsupportedOperationException}}:
> https://github.com/openjdk/jdk/blob/708407eddc9d52c01de02e3986c05e1c6225fa85/src/java.base/share/classes/java/util/Collections.java#L1278-L1279
> This was detected during working on
> https://github.com/assertj/assertj-core/pull/2328.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-collections] scordio commented on pull request #250: COLLECTIONS-799 - Prevent modifications of `UnmodifiableNavigableSet`
scordio commented on PR #250: URL: https://github.com/apache/commons-collections/pull/250#issuecomment-1106061634 Hi @kinow and @garydgregory, anything I could do to help get this released? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-build-plugin] dependabot[bot] opened a new pull request, #71: Bump maven-antrun-plugin from 3.0.0 to 3.1.0
dependabot[bot] opened a new pull request, #71: URL: https://github.com/apache/commons-build-plugin/pull/71 Bumps [maven-antrun-plugin](https://github.com/apache/maven-antrun-plugin) from 3.0.0 to 3.1.0. Commits https://github.com/apache/maven-antrun-plugin/commit/feceee80f82e1f52a8233a19015c1ed0e4cef2ef";>feceee8 [maven-release-plugin] prepare release maven-antrun-plugin-3.1.0 https://github.com/apache/maven-antrun-plugin/commit/4e899c4314aa9e1d8ee0e6b17844c849359c42ce";>4e899c4 [MANTRUN-236] Upgrade Maven Plugin Plugin to 3.6.4 https://github.com/apache/maven-antrun-plugin/commit/61c21bd0e95cb2e4433492f00eb473d5b39fb27d";>61c21bd Update CI URL https://github.com/apache/maven-antrun-plugin/commit/b44673765e5cb4990e779d9115226510403273a7";>b446737 Bump checkstyle from 9.2.1 to 9.3 https://github.com/apache/maven-antrun-plugin/commit/43cb90edb00dfd305574820b32d368a4ae25008d";>43cb90e [MANTRUN-232] Require Maven 3.2.5 - set proper maven scopes https://github.com/apache/maven-antrun-plugin/commit/2274253cdaed396d1de6964e1c6f93ebc7502141";>2274253 Shared GitHub Actions v2 https://github.com/apache/maven-antrun-plugin/commit/7911362e0ac86b5a1120bc8f6ef451c342ec";>7911362 Bump checkstyle from 9.0.1 to 9.2.1 https://github.com/apache/maven-antrun-plugin/commit/5bb03c35533255f04d98267c5662d3b2272835c2";>5bb03c3 (doc) Update plugins before release https://github.com/apache/maven-antrun-plugin/commit/e773180d4e7d1b661efe6fa7882fcd24c11e84bc";>e773180 Bump maven-site-plugin from 3.9.1 to 3.10.0 https://github.com/apache/maven-antrun-plugin/commit/68fc8330e278b92829168e66065b5fa32086df93";>68fc833 Bump xmlunit-matchers from 2.8.3 to 2.8.4 Additional commits viewable in https://github.com/apache/maven-antrun-plugin/compare/maven-antrun-plugin-3.0.0...maven-antrun-plugin-3.1.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-build-plugin] dependabot[bot] closed pull request #69: Bump actions/checkout from 2.4.0 to 3.0.1
dependabot[bot] closed pull request #69: Bump actions/checkout from 2.4.0 to 3.0.1 URL: https://github.com/apache/commons-build-plugin/pull/69 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-build-plugin] dependabot[bot] commented on pull request #69: Bump actions/checkout from 2.4.0 to 3.0.1
dependabot[bot] commented on PR #69: URL: https://github.com/apache/commons-build-plugin/pull/69#issuecomment-1106039911 Superseded by #70. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-build-plugin] dependabot[bot] opened a new pull request, #70: Bump actions/checkout from 2.4.0 to 3.0.2
dependabot[bot] opened a new pull request, #70: URL: https://github.com/apache/commons-build-plugin/pull/70 Bumps [actions/checkout](https://github.com/actions/checkout) from 2.4.0 to 3.0.2. Release notes Sourced from https://github.com/actions/checkout/releases";>actions/checkout's releases. v3.0.2 What's Changed Add set-safe-directory input to allow customers to take control. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/770";>actions/checkout#770 Prepare changelog for v3.0.2. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/777";>actions/checkout#777 Full Changelog: https://github.com/actions/checkout/compare/v3...v3.0.2";>https://github.com/actions/checkout/compare/v3...v3.0.2 v3.0.1 https://github-redirect.dependabot.com/actions/checkout/pull/762";>Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory https://github-redirect.dependabot.com/actions/checkout/pull/744";>Bumped various npm package versions v3.0.0 Updated to the node16 runtime by default This requires a minimum https://github.com/actions/runner/releases/tag/v2.285.0";>Actions Runner version of v2.285.0 to run, which is by default available in GHES 3.4 or later. v2.4.2 What's Changed Add set-safe-directory input to allow customers to take control. (https://github-redirect.dependabot.com/actions/checkout/issues/770";>#770) by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/776";>actions/checkout#776 Prepare changelog for v2.4.2. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/778";>actions/checkout#778 Full Changelog: https://github.com/actions/checkout/compare/v2...v2.4.2";>https://github.com/actions/checkout/compare/v2...v2.4.2 v2.4.1 Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory Changelog Sourced from https://github.com/actions/checkout/blob/main/CHANGELOG.md";>actions/checkout's changelog. v3.0.2 https://github-redirect.dependabot.com/actions/checkout/pull/770";>Add input set-safe-directory v3.0.1 https://github-redirect.dependabot.com/actions/checkout/pull/762";>Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory https://github-redirect.dependabot.com/actions/checkout/pull/744";>Bumped various npm package versions v3.0.0 https://github-redirect.dependabot.com/actions/checkout/pull/689";>Update to node 16 v2.3.1 https://github-redirect.dependabot.com/actions/checkout/pull/284";>Fix default branch resolution for .wiki and when using SSH v2.3.0 https://github-redirect.dependabot.com/actions/checkout/pull/278";>Fallback to the default branch v2.2.0 https://github-redirect.dependabot.com/actions/checkout/pull/258";>Fetch all history for all tags and branches when fetch-depth=0 v2.1.1 Changes to support GHES (https://github-redirect.dependabot.com/actions/checkout/pull/236";>here and https://github-redirect.dependabot.com/actions/checkout/pull/248";>here) v2.1.0 https://github-redirect.dependabot.com/actions/checkout/pull/191";>Group output https://github-redirect.dependabot.com/actions/checkout/pull/199";>Changes to support GHES alpha release https://github-redirect.dependabot.com/actions/checkout/pull/184";>Persist core.sshCommand for submodules https://github-redirect.dependabot.com/actions/checkout/pull/163";>Add support ssh https://github-redirect.dependabot.com/actions/checkout/pull/179";>Convert submodule SSH URL to HTTPS, when not using SSH https://github-redirect.dependabot.com/actions/checkout/pull/157";>Add submodule support https://github-redirect.dependabot.com/actions/checkout/pull/144";>Follow proxy settings https://github-redirect.dependabot.com/actions/checkout/pull/141";>Fix ref for pr closed event when a pr is merged https://github-redirect.dependabot.com/actions/checkout/pull/128";>Fix issue checking detached when git less than 2.22 v2.0.0 https://github-redirect.dependabot.com/actions/checkout/pull/108";>Do not pass cred on command line https://github-redirect.dependabot.com/actions/checkout/pull/107";>Add input persist-credentials https://github-redirect.dependabot.com/actions/checkout/pull/104";>Fallback to REST API to download repo v2 (beta) Improved fetch performance The default behavior now fetches only the SHA being checked-out Script authenticated git commands ... (truncated) Commits https://github.co
[GitHub] [commons-chain] dependabot[bot] closed pull request #30: Bump actions/checkout from 2.3.4 to 3.0.1
dependabot[bot] closed pull request #30: Bump actions/checkout from 2.3.4 to 3.0.1 URL: https://github.com/apache/commons-chain/pull/30 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-chain] dependabot[bot] commented on pull request #30: Bump actions/checkout from 2.3.4 to 3.0.1
dependabot[bot] commented on PR #30: URL: https://github.com/apache/commons-chain/pull/30#issuecomment-1106014817 Superseded by #32. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-chain] dependabot[bot] opened a new pull request, #32: Bump actions/checkout from 2.3.4 to 3.0.2
dependabot[bot] opened a new pull request, #32: URL: https://github.com/apache/commons-chain/pull/32 Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to 3.0.2. Release notes Sourced from https://github.com/actions/checkout/releases";>actions/checkout's releases. v3.0.2 What's Changed Add set-safe-directory input to allow customers to take control. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/770";>actions/checkout#770 Prepare changelog for v3.0.2. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/777";>actions/checkout#777 Full Changelog: https://github.com/actions/checkout/compare/v3...v3.0.2";>https://github.com/actions/checkout/compare/v3...v3.0.2 v3.0.1 https://github-redirect.dependabot.com/actions/checkout/pull/762";>Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory https://github-redirect.dependabot.com/actions/checkout/pull/744";>Bumped various npm package versions v3.0.0 Updated to the node16 runtime by default This requires a minimum https://github.com/actions/runner/releases/tag/v2.285.0";>Actions Runner version of v2.285.0 to run, which is by default available in GHES 3.4 or later. v2.4.2 What's Changed Add set-safe-directory input to allow customers to take control. (https://github-redirect.dependabot.com/actions/checkout/issues/770";>#770) by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/776";>actions/checkout#776 Prepare changelog for v2.4.2. by https://github.com/TingluoHuang";>@TingluoHuang in https://github-redirect.dependabot.com/actions/checkout/pull/778";>actions/checkout#778 Full Changelog: https://github.com/actions/checkout/compare/v2...v2.4.2";>https://github.com/actions/checkout/compare/v2...v2.4.2 v2.4.1 Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory v2.4.0 Convert SSH URLs like org-@github.com: to https://github.com/ - https://github-redirect.dependabot.com/actions/checkout/pull/621";>pr v2.3.5 Update dependencies Changelog Sourced from https://github.com/actions/checkout/blob/main/CHANGELOG.md";>actions/checkout's changelog. v3.0.2 https://github-redirect.dependabot.com/actions/checkout/pull/770";>Add input set-safe-directory v3.0.1 https://github-redirect.dependabot.com/actions/checkout/pull/762";>Fixed an issue where checkout failed to run in container jobs due to the new git setting safe.directory https://github-redirect.dependabot.com/actions/checkout/pull/744";>Bumped various npm package versions v3.0.0 https://github-redirect.dependabot.com/actions/checkout/pull/689";>Update to node 16 v2.3.1 https://github-redirect.dependabot.com/actions/checkout/pull/284";>Fix default branch resolution for .wiki and when using SSH v2.3.0 https://github-redirect.dependabot.com/actions/checkout/pull/278";>Fallback to the default branch v2.2.0 https://github-redirect.dependabot.com/actions/checkout/pull/258";>Fetch all history for all tags and branches when fetch-depth=0 v2.1.1 Changes to support GHES (https://github-redirect.dependabot.com/actions/checkout/pull/236";>here and https://github-redirect.dependabot.com/actions/checkout/pull/248";>here) v2.1.0 https://github-redirect.dependabot.com/actions/checkout/pull/191";>Group output https://github-redirect.dependabot.com/actions/checkout/pull/199";>Changes to support GHES alpha release https://github-redirect.dependabot.com/actions/checkout/pull/184";>Persist core.sshCommand for submodules https://github-redirect.dependabot.com/actions/checkout/pull/163";>Add support ssh https://github-redirect.dependabot.com/actions/checkout/pull/179";>Convert submodule SSH URL to HTTPS, when not using SSH https://github-redirect.dependabot.com/actions/checkout/pull/157";>Add submodule support https://github-redirect.dependabot.com/actions/checkout/pull/144";>Follow proxy settings https://github-redirect.dependabot.com/actions/checkout/pull/141";>Fix ref for pr closed event when a pr is merged https://github-redirect.dependabot.com/actions/checkout/pull/128";>Fix issue checking detached when git less than 2.22 v2.0.0 https://github-redirect.dependabot.com/actions/checkout/pull/108";>Do not pass cred on command line https://github-redirect.dependabot.com/actions/checkout/pull/107";>Add input persist-credentials https://github-redirect.dependabot.com/actions/checkout/pull/104";>Fallback to REST API to download repo v2 (beta) Improved fetch performance
[GitHub] [commons-dbcp] dependabot[bot] opened a new pull request, #185: Bump narayana-jta from 5.12.5.Final to 5.12.6.Final
dependabot[bot] opened a new pull request, #185: URL: https://github.com/apache/commons-dbcp/pull/185 Bumps narayana-jta from 5.12.5.Final to 5.12.6.Final. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [commons-compress] dependabot[bot] opened a new pull request, #286: Bump mockito.version from 4.4.0 to 4.5.1
dependabot[bot] opened a new pull request, #286: URL: https://github.com/apache/commons-compress/pull/286 Bumps `mockito.version` from 4.4.0 to 4.5.1. Updates `mockito-core` from 4.4.0 to 4.5.1 Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-core's releases. v4.5.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.5.1 2022-04-21 - https://github.com/mockito/mockito/compare/v4.5.0...v4.5.1";>2 commit(s) by Jeremy Landis, dependabot[bot] Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>#2623: Use zulu distribution and java 11 for release GHA job [(https://github-redirect.dependabot.com/mockito/mockito/issues/2624";>#2624)](https://github-redirect.dependabot.com/mockito/mockito/pull/2624";>mockito/mockito#2624) Missing errorprone module for 4.5.0 in central as release was done with jdk 8 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>#2623)](https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>mockito/mockito#2623) Bump kotlinVersion from 1.6.20 to 1.6.21 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2622";>#2622)](https://github-redirect.dependabot.com/mockito/mockito/pull/2622";>mockito/mockito#2622) v4.5.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.5.0 2022-04-19 - https://github.com/mockito/mockito/compare/v4.4.0...v4.5.0";>15 commit(s) by Andrei Silviu Dragnea, Rafael Winterhalter, Rick Ossendrijver, dependabot[bot] Bump versions.errorprone from 2.13.0 to 2.13.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2621";>#2621)](https://github-redirect.dependabot.com/mockito/mockito/pull/2621";>mockito/mockito#2621) Bump versions.errorprone from 2.12.1 to 2.13.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2619";>#2619)](https://github-redirect.dependabot.com/mockito/mockito/pull/2619";>mockito/mockito#2619) Groovy inline [(https://github-redirect.dependabot.com/mockito/mockito/issues/2618";>#2618)](https://github-redirect.dependabot.com/mockito/mockito/pull/2618";>mockito/mockito#2618) Bump actions/setup-java from 2 to 3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2615";>#2615)](https://github-redirect.dependabot.com/mockito/mockito/pull/2615";>mockito/mockito#2615) Bump versions.bytebuddy from 1.12.8 to 1.12.9 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2614";>#2614)](https://github-redirect.dependabot.com/mockito/mockito/pull/2614";>mockito/mockito#2614) Support subclass mocks on Graal VM. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2613";>#2613)](https://github-redirect.dependabot.com/mockito/mockito/pull/2613";>mockito/mockito#2613) Bump com.diffplug.spotless from 6.4.1 to 6.4.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2611";>#2611)](https://github-redirect.dependabot.com/mockito/mockito/pull/2611";>mockito/mockito#2611) Bump kotlinx-coroutines-core from 1.6.0-native-mt to 1.6.1-native-mt [(https://github-redirect.dependabot.com/mockito/mockito/issues/2609";>#2609)](https://github-redirect.dependabot.com/mockito/mockito/pull/2609";>mockito/mockito#2609) Bump versions.errorprone from 2.10.0 to 2.12.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2608";>#2608)](https://github-redirect.dependabot.com/mockito/mockito/pull/2608";>mockito/mockito#2608) Bump kotlinVersion from 1.6.10 to 1.6.20 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2607";>#2607)](https://github-redirect.dependabot.com/mockito/mockito/pull/2607";>mockito/mockito#2607) Bump com.diffplug.spotless from 6.4.0 to 6.4.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2606";>#2606)](https://github-redirect.dependabot.com/mockito/mockito/pull/2606";>mockito/mockito#2606) Bump com.diffplug.spotless from 6.3.0 to 6.4.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2605";>#2605)](https://github-redirect.dependabot.com/mockito/mockito/pull/2605";>mockito/mockito#2605) Bump org.eclipse.osgi from 3.17.100 to 3.17.200 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2597";>#2597)](https://github-redirect.dependabot.com/mockito/mockito/pull/2597";>mockito/mockito#2597) Deprecate ListUtil and Fields classes [(https://github-redirect.dependabot.com/mockito/mockito/issues/2593";>#2593)](https://github-redirect.dependabot.com/mockito/mockito/pull/2593";>mockito/mockito#2593) mockito-errorprone seems not compatible with ErrorProne 2.11.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2554";>#2554)](https://github-redirect.dependabot.com/mockito/mockito/issues/2554";>mockito/mockito#2554) NullPointerException from Groovy metaclass methods when using mockito-inline (but not mockito-core) [(ht
[GitHub] [commons-dbcp] dependabot[bot] opened a new pull request, #184: Bump maven-javadoc-plugin from 3.3.2 to 3.4.0
dependabot[bot] opened a new pull request, #184: URL: https://github.com/apache/commons-dbcp/pull/184 Bumps [maven-javadoc-plugin](https://github.com/apache/maven-javadoc-plugin) from 3.3.2 to 3.4.0. Commits https://github.com/apache/maven-javadoc-plugin/commit/40cc602f84dbb0689020b55b24970cdd7147722c";>40cc602 [maven-release-plugin] prepare release maven-javadoc-plugin-3.4.0 https://github.com/apache/maven-javadoc-plugin/commit/0c6b32fb5ec9c31b4e38d9f32616ff51102623da";>0c6b32f [MJAVADOC-714] Upgrade to Maven 3.2.5 https://github.com/apache/maven-javadoc-plugin/commit/506cb74e6abc4b108121b0c586a15b75dd5ccc39";>506cb74 [MJAVADOC-696] Invalid anchors in Javadoc and plugin mojo https://github.com/apache/maven-javadoc-plugin/commit/47d03d3a08cc58a93fa384f4661d79c350842b82";>47d03d3 [MJAVADOC-712] Remove remains of org.codehaus.doxia.sink.Sink https://github.com/apache/maven-javadoc-plugin/commit/5fae3b656e131fa233982eebf0944b5253fc845e";>5fae3b6 [MJAVADOC-711] Upgrade plugins in ITs https://github.com/apache/maven-javadoc-plugin/commit/03ca84372ab689c91dd0d5b63cc2ee12ee3c466b";>03ca843 Bump maven-archiver from 3.5.1 to 3.5.2 https://github.com/apache/maven-javadoc-plugin/commit/5dcfa6e70795d0b5cf5414a848e7e0aeb5541413";>5dcfa6e Bump plexus-archiver from 4.2.6 to 4.2.7 https://github.com/apache/maven-javadoc-plugin/commit/ca00601609903a0e88a067b2aa3d49e88191937a";>ca00601 Bump junit in /src/it/projects/MJAVADOC-498_modulepath https://github.com/apache/maven-javadoc-plugin/commit/2583554135dc04db58a435ebcbd2cd19f0d2563a";>2583554 Bump commons-io from 2.2 to 2.7 in /src/it/projects/MJAVADOC-437/module2 https://github.com/apache/maven-javadoc-plugin/commit/9dd7bddb3db6d0d230092d7fbbd4188a98a3a75e";>9dd7bdd use shared gh action/release-drafter (https://github-redirect.dependabot.com/apache/maven-javadoc-plugin/issues/128";>#128) Additional commits viewable in https://github.com/apache/maven-javadoc-plugin/compare/maven-javadoc-plugin-3.3.2...maven-javadoc-plugin-3.4.0";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (GEOMETRY-146) PointSet/Map closest points
[
https://issues.apache.org/jira/browse/GEOMETRY-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17526158#comment-17526158
]
Matt Juntunen commented on GEOMETRY-146:
It turns out that my instincts on the performance of {{neighborEntries}} were
incorrect and I am not able to find a performance boost over just using
{{nearToFar}} or even just iterating through the entire map. Below are the JMH
results for the best implementation I could come up with.
||Benchmark||(dist)||(randomSeed)||(shape)||Mode||Cnt||Score||Error||Units||
|neighborEntries|random|1|block|avgt|5|18078272.739|± 2855877.430|ns/op|
|neighborEntriesFullBaseline|random|1|block|avgt|5|3953413.160|±
1299435.732|ns/op|
|neighborEntriesFullStreamBaseline|random|1|block|avgt|5|19190180.574|±
3775274.018|ns/op|
|neighborEntriesNearToFarBaseline|random|1|block|avgt|5|13143387.077|±
2344194.490|ns/op|
|neighborEntryIterable|random|1|block|avgt|5|15025352.786|± 3978281.128|ns/op|
- {{neighborEntries}} - supposedly "optimized" method
- {{neighborEntriesFullBaseline}} - iterating through the entire map and
checking the distance for each entry
- {{neighborEntriesFullStreamBaseline}} - filtering a stream over the map entry
set
- {{neighborEntriesNearToFarBaseline}} - iterating over the {{nearToFar}}
collection and breaking out of the loop when the max distance is passed
- {{neighborEntryIterable}} - iterator version of {{neighborEntries}}
Based on these results, I'm going to remove {{neighborEntries}} from the API.
There isn't a performance boost and the functionality can be implemented in
terms of the other methods.
> PointSet/Map closest points
> ---
>
> Key: GEOMETRY-146
> URL: https://issues.apache.org/jira/browse/GEOMETRY-146
> Project: Commons Geometry
> Issue Type: New Feature
>Reporter: Matt Juntunen
>Priority: Major
> Fix For: 1.1
>
>
> Add methods to the new {{PointSet}} and {{PointMap}} interfaces to allow
> querying of points in order of distance from a query point.
> {code:java}
> PointSet {
> // find the closest point to pt or null if empty
> P closest(P pt);
> // iterate through points in order, with points closest to pt coming first
> Iterable closestFirst(P pt);
> // find the farthest point from pt or null if emtpy
> P farthest(P pt);
> // iterate through point in order, with points farthest from pt coming
> first
> Iterable farthestFirst(P pt);
> }
> {code}
> {{PointMap}} should have similar methods providing access to the map keys and
> entries.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-io] dependabot[bot] opened a new pull request, #348: Bump mockito-inline from 4.4.0 to 4.5.1
dependabot[bot] opened a new pull request, #348: URL: https://github.com/apache/commons-io/pull/348 Bumps [mockito-inline](https://github.com/mockito/mockito) from 4.4.0 to 4.5.1. Release notes Sourced from https://github.com/mockito/mockito/releases";>mockito-inline's releases. v4.5.1 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.5.1 2022-04-21 - https://github.com/mockito/mockito/compare/v4.5.0...v4.5.1";>2 commit(s) by Jeremy Landis, dependabot[bot] Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>#2623: Use zulu distribution and java 11 for release GHA job [(https://github-redirect.dependabot.com/mockito/mockito/issues/2624";>#2624)](https://github-redirect.dependabot.com/mockito/mockito/pull/2624";>mockito/mockito#2624) Missing errorprone module for 4.5.0 in central as release was done with jdk 8 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>#2623)](https://github-redirect.dependabot.com/mockito/mockito/issues/2623";>mockito/mockito#2623) Bump kotlinVersion from 1.6.20 to 1.6.21 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2622";>#2622)](https://github-redirect.dependabot.com/mockito/mockito/pull/2622";>mockito/mockito#2622) v4.5.0 Changelog generated by https://github.com/shipkit/shipkit-changelog";>Shipkit Changelog Gradle Plugin 4.5.0 2022-04-19 - https://github.com/mockito/mockito/compare/v4.4.0...v4.5.0";>15 commit(s) by Andrei Silviu Dragnea, Rafael Winterhalter, Rick Ossendrijver, dependabot[bot] Bump versions.errorprone from 2.13.0 to 2.13.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2621";>#2621)](https://github-redirect.dependabot.com/mockito/mockito/pull/2621";>mockito/mockito#2621) Bump versions.errorprone from 2.12.1 to 2.13.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2619";>#2619)](https://github-redirect.dependabot.com/mockito/mockito/pull/2619";>mockito/mockito#2619) Groovy inline [(https://github-redirect.dependabot.com/mockito/mockito/issues/2618";>#2618)](https://github-redirect.dependabot.com/mockito/mockito/pull/2618";>mockito/mockito#2618) Bump actions/setup-java from 2 to 3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2615";>#2615)](https://github-redirect.dependabot.com/mockito/mockito/pull/2615";>mockito/mockito#2615) Bump versions.bytebuddy from 1.12.8 to 1.12.9 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2614";>#2614)](https://github-redirect.dependabot.com/mockito/mockito/pull/2614";>mockito/mockito#2614) Support subclass mocks on Graal VM. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2613";>#2613)](https://github-redirect.dependabot.com/mockito/mockito/pull/2613";>mockito/mockito#2613) Bump com.diffplug.spotless from 6.4.1 to 6.4.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2611";>#2611)](https://github-redirect.dependabot.com/mockito/mockito/pull/2611";>mockito/mockito#2611) Bump kotlinx-coroutines-core from 1.6.0-native-mt to 1.6.1-native-mt [(https://github-redirect.dependabot.com/mockito/mockito/issues/2609";>#2609)](https://github-redirect.dependabot.com/mockito/mockito/pull/2609";>mockito/mockito#2609) Bump versions.errorprone from 2.10.0 to 2.12.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2608";>#2608)](https://github-redirect.dependabot.com/mockito/mockito/pull/2608";>mockito/mockito#2608) Bump kotlinVersion from 1.6.10 to 1.6.20 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2607";>#2607)](https://github-redirect.dependabot.com/mockito/mockito/pull/2607";>mockito/mockito#2607) Bump com.diffplug.spotless from 6.4.0 to 6.4.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2606";>#2606)](https://github-redirect.dependabot.com/mockito/mockito/pull/2606";>mockito/mockito#2606) Bump com.diffplug.spotless from 6.3.0 to 6.4.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2605";>#2605)](https://github-redirect.dependabot.com/mockito/mockito/pull/2605";>mockito/mockito#2605) Bump org.eclipse.osgi from 3.17.100 to 3.17.200 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2597";>#2597)](https://github-redirect.dependabot.com/mockito/mockito/pull/2597";>mockito/mockito#2597) Deprecate ListUtil and Fields classes [(https://github-redirect.dependabot.com/mockito/mockito/issues/2593";>#2593)](https://github-redirect.dependabot.com/mockito/mockito/pull/2593";>mockito/mockito#2593) mockito-errorprone seems not compatible with ErrorProne 2.11.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2554";>#2554)](https://github-redirect.dependabot.com/mockito/mockito/issues/2554";>mockito/mockito#2554) NullPointerException from Groovy metaclass methods when using mockito-inline (but not mockito-core) [(https://github-r
[GitHub] [commons-vfs] garydgregory commented on pull request #150: Call `refresh` by default in `AbstractFileObject.onChange`
garydgregory commented on PR #150: URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-1105839064 OK, then if someone wants to get this build green, they know where to dig. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (COLLECTIONS-807) Upgrade org.junit.Test to org.junit.jupiter.api.Test
[
https://issues.apache.org/jira/browse/COLLECTIONS-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved COLLECTIONS-807.
-
Fix Version/s: 4.5
Resolution: Fixed
In git master.
> Upgrade org.junit.Test to org.junit.jupiter.api.Test
>
>
> Key: COLLECTIONS-807
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-807
> Project: Commons Collections
> Issue Type: Sub-task
>Reporter: John Patrick
>Priority: Major
> Fix For: 4.5
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Covers '17' usages of legacy usage of;
> {code:java}
> import org.junit.Test;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Work logged] (COLLECTIONS-807) Upgrade org.junit.Test to org.junit.jupiter.api.Test
[
https://issues.apache.org/jira/browse/COLLECTIONS-807?focusedWorklogId=760426&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760426
]
ASF GitHub Bot logged work on COLLECTIONS-807:
--
Author: ASF GitHub Bot
Created on: 21/Apr/22 21:06
Start Date: 21/Apr/22 21:06
Worklog Time Spent: 10m
Work Description: garydgregory merged PR #295:
URL: https://github.com/apache/commons-collections/pull/295
Issue Time Tracking
---
Worklog Id: (was: 760426)
Time Spent: 1h 10m (was: 1h)
> Upgrade org.junit.Test to org.junit.jupiter.api.Test
>
>
> Key: COLLECTIONS-807
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-807
> Project: Commons Collections
> Issue Type: Sub-task
>Reporter: John Patrick
>Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Covers '17' usages of legacy usage of;
> {code:java}
> import org.junit.Test;
> {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-collections] garydgregory merged pull request #295: COLLECTIONS-807: Upgraded org.junit.Test to org.junit.jupiter.api.Test
garydgregory merged PR #295: URL: https://github.com/apache/commons-collections/pull/295 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (POOL-318) java.util.ConcurrentModificationException
[ https://issues.apache.org/jira/browse/POOL-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory closed POOL-318. Resolution: Information Provided > java.util.ConcurrentModificationException > - > > Key: POOL-318 > URL: https://issues.apache.org/jira/browse/POOL-318 > Project: Commons Pool > Issue Type: Bug >Affects Versions: 2.4.2 >Reporter: Sanjeev >Priority: Major > > I am using commons.pool.2.4.2 and once size of existing pool reduces to > certain number, application runs perparePool() > I can see some instances of java.util.ConcurrentModificationException in > error logs. > at > org.apache.commons.pool2.BasePooledObjectFactory.makeObject(BasePooledObjectFactory.java:60) > at > org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868) > at > org.apache.commons.pool2.impl.GenericObjectPool.ensureIdle(GenericObjectPool.java:927) > at > org.apache.commons.pool2.impl.GenericObjectPool.ensureMinIdle(GenericObjectPool.java:906) > at > org.apache.commons.pool2.impl.GenericObjectPool.preparePool(GenericObjectPool.java:844) > . > at java.lang.Thread.run(Thread.java:722) > Caused by: java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:894) > at java.util.HashMap$EntryIterator.next(HashMap.java:934) > at java.util.HashMap$EntryIterator.next(HashMap.java:932) > at > org.jboss.util.TimedCachePolicy.getValidKeys(TimedCachePolicy.java:364) > at > org.jboss.virtual.plugins.cache.IterableTimedVFSCache.findContext(IterableTimedVFSCache.java:65) > at > org.jboss.virtual.plugins.cache.CombinedVFSCache.findContext(CombinedVFSCache.java:116) > at > org.jboss.virtual.plugins.registry.DefaultVFSRegistry.getContext(DefaultVFSRegistry.java:132) > at org.jboss.virtual.VFS.getVFS(VFS.java:203) > at org.jboss.virtual.VFS.createNewRoot(VFS.java:228) > at org.jboss.virtual.VFS.getRoot(VFS.java:244) > at org.jboss.virtual.VFS.getRoot(VFS.java:313) > at > org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:105) > at > org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118) > at > org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) > at > org.springframework.core.io.UrlResource.getInputStream(UrlResource.java:123) > at > org.apache.cxf.bus.spring.BusApplicationContext.getConfigResources(BusApplicationContext.java:115) > at > org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:107) > at > org.apache.cxf.bus.spring.BusApplicationContext.loadBeanDefinitions(BusApplicationContext.java:262) > at > org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:123) > at > org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:422) > at > org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352) > at > org.apache.cxf.bus.spring.BusApplicationContext.(BusApplicationContext.java:91) > at > org.apache.cxf.bus.spring.SpringBusFactory.createApplicationContext(SpringBusFactory.java:102) > at > org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:93) > at > org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:86) > at > org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:64) > at > org.apache.cxf.bus.spring.SpringBusFactory.createBus(SpringBusFactory.java:53) > at > org.jboss.wsf.stack.cxf.client.ProviderImpl.setValidThreadDefaultBus(ProviderImpl.java:60) > at > org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:41) > at javax.xml.ws.Service.(Service.java:56) > at javax.xml.ws.Service.create(Service.java:680) > Application runs preparePool () in new thread. and next statement is to > borrow instance from pool. Borrowing does not fail but few poolPrepartion > fail log is in error log. > Any suggestions please? -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (POOL-393) BaseGenericObjectPool.jmxRegister may cost too much time
[
https://issues.apache.org/jira/browse/POOL-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525884#comment-17525884
]
Gary D. Gregory commented on POOL-393:
--
Note: The PR was closed.
> BaseGenericObjectPool.jmxRegister may cost too much time
>
>
> Key: POOL-393
> URL: https://issues.apache.org/jira/browse/POOL-393
> Project: Commons Pool
> Issue Type: Improvement
>Affects Versions: 2.4.2
>Reporter: Shichao Yuan
>Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
>
> When creating many pools, I find that it tasks too much time to register jmx.
> In the code, the ObjectName's postfix always starts with 1, so many
> InstanceAlreadyExistsExceptions may be thrown before registered successfully.
> Maybe a random number is a better choice, or a atomic long.
> {quote}private ObjectName jmxRegister(BaseObjectPoolConfig config,
> String jmxNameBase, String jmxNamePrefix) {
> ObjectName objectName = null;
> MBeanServer mbs = ManagementFactory.getPlatformMBeanServer();
> int i = 1;
> boolean registered = false;
> String base = config.getJmxNameBase();
> if (base == null)
> Unknown macro: \{ base = jmxNameBase; }
> while (!registered) {
> try {
> ObjectName objName;
> // Skip the numeric suffix for the first pool in case there is
> // only one so the names are cleaner.
> if (i == 1)
> Unknown macro: \{ objName = new ObjectName(base + jmxNamePrefix); }
> else
> Unknown macro: \{ objName = new ObjectName(base + jmxNamePrefix + i); }
> mbs.registerMBean(this, objName);
> objectName = objName;
> registered = true;
> } catch (MalformedObjectNameException e) {
> if (BaseObjectPoolConfig.DEFAULT_JMX_NAME_PREFIX.equals(
> jmxNamePrefix) && jmxNameBase.equals(base))
> Unknown macro: \{ // Shouldn't happen. Skip registration if it does.
> registered = true; }
> else
> Unknown macro: \{ // Must be an invalid name. Use the defaults instead.
> jmxNamePrefix = BaseObjectPoolConfig.DEFAULT_JMX_NAME_PREFIX; base =
> jmxNameBase; }
> } catch (InstanceAlreadyExistsException e)
> Unknown macro: \{ // Increment the index and try again i++; }
> catch (MBeanRegistrationException e)
> Unknown macro: \{ // Shouldn't happen. Skip registration if it does.
> registered = true; }
> catch (NotCompliantMBeanException e)
> }
> return objectName;
> }
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Closed] (POOL-392) Add Async addObjects Implementation
[
https://issues.apache.org/jira/browse/POOL-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory closed POOL-392.
Resolution: Information Provided
> Add Async addObjects Implementation
> ---
>
> Key: POOL-392
> URL: https://issues.apache.org/jira/browse/POOL-392
> Project: Commons Pool
> Issue Type: Improvement
>Reporter: David Mollitor
>Priority: Major
>
> {code:java|title=ObjectPool.java}
> default void addObjects(final int count) throws Exception {
> for (int i = 0; i < count; i++) {
> addObject();
> }
> }
> {code}
> I have a use case where `addObject` is a very expensive call: ~2m. So, to
> pre-populate the pool with 5 objects requires 10m+. Would be nice to have an
> async (ExecutorService) version which loads the pool in parallel.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (POOL-264) NullPointerException in GKOP.borrowObject()
[ https://issues.apache.org/jira/browse/POOL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525868#comment-17525868 ] Gary D. Gregory commented on POOL-264: -- I'm guessing this is fixed in 2.x... ok to close? > NullPointerException in GKOP.borrowObject() > --- > > Key: POOL-264 > URL: https://issues.apache.org/jira/browse/POOL-264 > Project: Commons Pool > Issue Type: Bug >Affects Versions: 1.5.6, 1.5.7, 1.6 >Reporter: Leonid Meyerguz >Priority: Major > Fix For: 1.5.8, 1.6.1 > > > While I cannot pin down a consistent repro, I occasionally observe a > NullPointerException at > org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1126) > The pool is configured as follows: > maxActive = -1 > maxIdle = 32 > maxTotal = 32 > whenExhaustedAction = WHEN_EXHAUSTED_GROW > timeBetweenEvictionRunsMillis = 2 > minEvictableIdleTimeMillis = 6 > numTestsPerEvictionRun = -1 > The NullPointerException is thrown in the WHEN_EXHAUSTED_GROW branch of the > code. Specifically it appears that latch.getPool() returns null. > Any suggestions for a work-around would be appreciated. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEANUTILS-540) BeanUtils.copyProperties not working in static inner class
[
https://issues.apache.org/jira/browse/BEANUTILS-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525825#comment-17525825
]
Ng Tsz Sum commented on BEANUTILS-540:
--
The `copyProperties` will work as expected if the static inner classes are
public.
> BeanUtils.copyProperties not working in static inner class
> ---
>
> Key: BEANUTILS-540
> URL: https://issues.apache.org/jira/browse/BEANUTILS-540
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
>Affects Versions: 1.9.3
> Environment: local test
>Reporter: Liu Jun Long
>Priority: Major
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> using below funtion copy beans, i have created two static inner class, but
> not copy successfully, then i have created two normal class, it's working
> fine.
> under Spring's package, working fine.
> package com;
> import org.apache.commons.beanutils.BeanUtils;
> //import org.springframework.beans.BeanUtils;
> public class Test {
> public static void main(String[] args) throws Exception {
> // TODO Auto-generated method stub
> Person person = new Person();
> person.setAddress("Shannxi");
> person.setName("Leo1");
> Student student = new Student();
> BeanUtils.copyProperties(student, person);
> System.out.println(student);
> //at firstly create two nomal class Employ and manager
> Employ employ = new Employ();
> employ.setAddress("Shannxi xian");
> employ.setName("Leo1");
> Manager manager = new Manager();
> BeanUtils.copyProperties(manager, employ);
> System.out.println(manager);
> }
> static class Person {
> private String name;
> private String address;
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> public String getAddress() {
> return address;
> }
> public void setAddress(String address) {
> this.address = address;
> }
> }
> static class Student {
> private String name;
> private String address;
> public String getName() {
> return name;
> }
> public void setName(String name) {
> this.name = name;
> }
> public String getAddress() {
> return address;
> }
> public void setAddress(String address) {
> this.address = address;
> }
> @Override
> public String toString() {
> return "Student [name=" + name + ", address=" + address + "]";
> }
> }
> }
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (BEANUTILS-484) Invalid case "eId" field
[
https://issues.apache.org/jira/browse/BEANUTILS-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525813#comment-17525813
]
Ng Tsz Sum commented on BEANUTILS-484:
--
This problem is not reproducible in
[c09e8de8|https://github.com/apache/commons-beanutils/commit/c09e8de8a0226ca288a9a7776f7d843ab610024e]
{code:java}
import java.lang.reflect.InvocationTargetException;
public class TestInvalidCase {
public String getEld() {
return eld;
}
public void setEld(String eld) {
this.eld = eld;
}
private String eld;
public static void main(String[] args) throws InvocationTargetException,
IllegalAccessException, NoSuchMethodException {
System.out.println(BeanUtils.describe(new TestInvalidCase()));
// {eld=null}
}
} {code}
> Invalid case "eId" field
>
>
> Key: BEANUTILS-484
> URL: https://issues.apache.org/jira/browse/BEANUTILS-484
> Project: Commons BeanUtils
> Issue Type: Bug
>Reporter: Daneel Yaitskov
>Priority: Major
>
> BeanUtils.describe returns "EId" for field "eId".
> I expected "eId" instead.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (POOL-405) NullPointerException at org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
[
https://issues.apache.org/jira/browse/POOL-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved POOL-405.
--
Fix Version/s: 2.12.0
Resolution: Fixed
> NullPointerException at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> ---
>
> Key: POOL-405
> URL: https://issues.apache.org/jira/browse/POOL-405
> Project: Commons Pool
> Issue Type: Bug
>Reporter: Gary D. Gregory
>Assignee: Gary D. Gregory
>Priority: Major
> Fix For: 2.12.0
>
>
> You get a {{NullPointerException}} at
> {{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
> when you pass an unknown key.
> The exception should be an {{IllegalStateException}} instead.
> For example:
>
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (JCS-231) Lateral TCP cache goes in loop and consumes all available resources
[
https://issues.apache.org/jira/browse/JCS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525751#comment-17525751
]
Andrea Vettori commented on JCS-231:
Hello, thanks for looking into the issue.
With the current master I don't get the exception at startup. Let's see what
happens if I leave it running... I'll let you know.
Thank you!
> Lateral TCP cache goes in loop and consumes all available resources
> ---
>
> Key: JCS-231
> URL: https://issues.apache.org/jira/browse/JCS-231
> Project: Commons JCS
> Issue Type: Bug
>Affects Versions: jcs-3.1
> Environment: Linux, Tomcat 9, Adoption JDK 11
>Reporter: Andrea Vettori
>Assignee: Thomas Vandahl
>Priority: Major
>
> Hello, we upgraded from 3.0 to 3.1 and had to go back for the following
> problem.
> With this LTCP configuration
> {{jcs.auxiliary.LTCP=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory}}
> {{jcs.auxiliary.LTCP.attributes=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes}}
> {{jcs.auxiliary.LTCP.attributes.TcpListenerPort=1120}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryAddr=228.5.6.8}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryPort=6782}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=true}}
> {{jcs.auxiliary.LTCP.attributes.Receive=true}}
> {{jcs.auxiliary.LTCP.attributes.AllowGet=false}}
> {{jcs.auxiliary.LTCP.attributes.IssueRemoveOnPut=false}}
>
> Most of the time JCS starts with the following logs
> {{{}16-Apr-2022 14:31:04.523 INFO [main]
> org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator. Using standard
> serializer
> [org.apache.commons.jcs3.utils.serialization.StandardSerializer@22aa6570] for
> auxiliary [jcs.auxiliary.LTCP]{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Instance for [] is null, creating{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Creating TCP service, lca = :1120{}}}{{{}16-Apr-2022 14:31:04.531 SEVERE
> [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService. Could
> not create sender to [] – Invalid address []{}}}{{{}16-Apr-2022 14:31:04.531
> SEVERE [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Failure, lateral instance will use zombie service{}}}{{
> java.io.IOException: Invalid address []}}{{ at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPSender.(LateralTCPSender.java:104)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService.(LateralTCPService.java:96)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.lambda$getCSNLInstance$0(LateralTCPCacheFactory.java:271)}}{{
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.getCSNLInstance(LateralTCPCacheFactory.java:251)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCacheNoWait(LateralTCPCacheFactory.java:143)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:110)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:56)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseAuxiliary(CompositeCacheConfigurator.java:450)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:234)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:157)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegions(CompositeCacheConfigurator.java:135)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.doConfigure(CompositeCacheManager.java:455)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:406)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:365)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:347)}}{{
> at
> org.apache.commons.jcs3.eng
[jira] [Updated] (POOL-405) NullPointerException at org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
[
https://issues.apache.org/jira/browse/POOL-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated POOL-405:
-
Description:
You get a {{NullPointerException}} at
{{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
when you pass an unknown key.
The exception should be an {{IllegalStateException}} instead.
For example:
{noformat}
java.lang.NullPointerException
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
{noformat}
was:
It is possible to get a {{NullPointerException}} at
{{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
This should be an {{IllegalStateException}} instead.
For example:
{noformat}
java.lang.NullPointerException
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
{noformat}
> NullPointerException at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> ---
>
> Key: POOL-405
> URL: https://issues.apache.org/jira/browse/POOL-405
> Project: Commons Pool
> Issue Type: Bug
>Reporter: Gary D. Gregory
>Assignee: Gary D. Gregory
>Priority: Major
>
> You get a {{NullPointerException}} at
> {{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
> when you pass an unknown key.
> The exception should be an {{IllegalStateException}} instead.
> For example:
>
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-pool] michael-o commented on pull request #143: Pool 269 generic exceptions
michael-o commented on PR #143: URL: https://github.com/apache/commons-pool/pull/143#issuecomment-1105303046 I still don't consider this as a clean solution, but only halfbreed not to wait for next major. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (POOL-405) NullPointerException at org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
[
https://issues.apache.org/jira/browse/POOL-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated POOL-405:
-
Description:
It is possible to get a {{NullPointerException}} at
{{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
This should be an {{IllegalStateException}} instead.
For example:
{noformat}
java.lang.NullPointerException
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
{noformat}
was:
It is possible to get a {{NullPointerException}} at
{{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
For example:
{noformat}
java.lang.NullPointerException
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
{noformat}
> NullPointerException at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> ---
>
> Key: POOL-405
> URL: https://issues.apache.org/jira/browse/POOL-405
> Project: Commons Pool
> Issue Type: Bug
>Reporter: Gary D. Gregory
>Assignee: Gary D. Gregory
>Priority: Major
>
> It is possible to get a {{NullPointerException}} at
> {{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
> This should be an {{IllegalStateException}} instead.
> For example:
>
> {noformat}
> java.lang.NullPointerException
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
> at
> org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (POOL-405) NullPointerException at org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
Gary D. Gregory created POOL-405:
Summary: NullPointerException at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
Key: POOL-405
URL: https://issues.apache.org/jira/browse/POOL-405
Project: Commons Pool
Issue Type: Bug
Reporter: Gary D. Gregory
Assignee: Gary D. Gregory
It is possible to get a {{NullPointerException}} at
{{org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)}}
For example:
{noformat}
java.lang.NullPointerException
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1343)
at
org.apache.commons.pool2.impl.GenericKeyedObjectPool.invalidateObject(GenericKeyedObjectPool.java:1320)
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (POOL-269) Use a generic exception instead of Exception
[
https://issues.apache.org/jira/browse/POOL-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory resolved POOL-269.
--
Fix Version/s: 2.12.0
(was: 3.0)
Resolution: Fixed
> Use a generic exception instead of Exception
>
>
> Key: POOL-269
> URL: https://issues.apache.org/jira/browse/POOL-269
> Project: Commons Pool
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Gary D. Gregory
>Priority: Major
> Fix For: 2.12.0
>
>
> Too many methods say {{throws Exception}} in their signature. This is neither
> helpful nor good API design. You never know what the exception is and where
> it came from.
> An exception translation pattern has to be applied to make code usable, e.g.,
> like the Spring project does or Maven with {{BuildException}}.
> Unfortunately, this ugly practive has prevailed in several Apache projects
> like Lucene.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (POOL-269) Use generic exceptions instead of java.lang.Exception
[
https://issues.apache.org/jira/browse/POOL-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated POOL-269:
-
Summary: Use generic exceptions instead of java.lang.Exception (was: Use a
generic exception instead of Exception)
> Use generic exceptions instead of java.lang.Exception
> -
>
> Key: POOL-269
> URL: https://issues.apache.org/jira/browse/POOL-269
> Project: Commons Pool
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Michael Osipov
>Assignee: Gary D. Gregory
>Priority: Major
> Fix For: 2.12.0
>
>
> Too many methods say {{throws Exception}} in their signature. This is neither
> helpful nor good API design. You never know what the exception is and where
> it came from.
> An exception translation pattern has to be applied to make code usable, e.g.,
> like the Spring project does or Maven with {{BuildException}}.
> Unfortunately, this ugly practive has prevailed in several Apache projects
> like Lucene.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-pool] garydgregory merged pull request #143: Pool 269 generic exceptions
garydgregory merged PR #143: URL: https://github.com/apache/commons-pool/pull/143 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (JCS-231) Lateral TCP cache goes in loop and consumes all available resources
[
https://issues.apache.org/jira/browse/JCS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Vandahl updated JCS-231:
---
Assignee: Thomas Vandahl
> Lateral TCP cache goes in loop and consumes all available resources
> ---
>
> Key: JCS-231
> URL: https://issues.apache.org/jira/browse/JCS-231
> Project: Commons JCS
> Issue Type: Bug
>Affects Versions: jcs-3.1
> Environment: Linux, Tomcat 9, Adoption JDK 11
>Reporter: Andrea Vettori
>Assignee: Thomas Vandahl
>Priority: Major
>
> Hello, we upgraded from 3.0 to 3.1 and had to go back for the following
> problem.
> With this LTCP configuration
> {{jcs.auxiliary.LTCP=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory}}
> {{jcs.auxiliary.LTCP.attributes=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes}}
> {{jcs.auxiliary.LTCP.attributes.TcpListenerPort=1120}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryAddr=228.5.6.8}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryPort=6782}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=true}}
> {{jcs.auxiliary.LTCP.attributes.Receive=true}}
> {{jcs.auxiliary.LTCP.attributes.AllowGet=false}}
> {{jcs.auxiliary.LTCP.attributes.IssueRemoveOnPut=false}}
>
> Most of the time JCS starts with the following logs
> {{{}16-Apr-2022 14:31:04.523 INFO [main]
> org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator. Using standard
> serializer
> [org.apache.commons.jcs3.utils.serialization.StandardSerializer@22aa6570] for
> auxiliary [jcs.auxiliary.LTCP]{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Instance for [] is null, creating{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Creating TCP service, lca = :1120{}}}{{{}16-Apr-2022 14:31:04.531 SEVERE
> [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService. Could
> not create sender to [] – Invalid address []{}}}{{{}16-Apr-2022 14:31:04.531
> SEVERE [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Failure, lateral instance will use zombie service{}}}{{
> java.io.IOException: Invalid address []}}{{ at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPSender.(LateralTCPSender.java:104)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService.(LateralTCPService.java:96)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.lambda$getCSNLInstance$0(LateralTCPCacheFactory.java:271)}}{{
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.getCSNLInstance(LateralTCPCacheFactory.java:251)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCacheNoWait(LateralTCPCacheFactory.java:143)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:110)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:56)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseAuxiliary(CompositeCacheConfigurator.java:450)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:234)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:157)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegions(CompositeCacheConfigurator.java:135)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.doConfigure(CompositeCacheManager.java:455)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:406)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:365)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:347)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:336)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.getInstance(CompositeCacheManager.java:188)}}{{
>
[jira] [Commented] (JCS-231) Lateral TCP cache goes in loop and consumes all available resources
[
https://issues.apache.org/jira/browse/JCS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525666#comment-17525666
]
Thomas Vandahl commented on JCS-231:
Would you please test the current master? I attempted a fix.
> Lateral TCP cache goes in loop and consumes all available resources
> ---
>
> Key: JCS-231
> URL: https://issues.apache.org/jira/browse/JCS-231
> Project: Commons JCS
> Issue Type: Bug
>Affects Versions: jcs-3.1
> Environment: Linux, Tomcat 9, Adoption JDK 11
>Reporter: Andrea Vettori
>Priority: Major
>
> Hello, we upgraded from 3.0 to 3.1 and had to go back for the following
> problem.
> With this LTCP configuration
> {{jcs.auxiliary.LTCP=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory}}
> {{jcs.auxiliary.LTCP.attributes=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes}}
> {{jcs.auxiliary.LTCP.attributes.TcpListenerPort=1120}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryAddr=228.5.6.8}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryPort=6782}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=true}}
> {{jcs.auxiliary.LTCP.attributes.Receive=true}}
> {{jcs.auxiliary.LTCP.attributes.AllowGet=false}}
> {{jcs.auxiliary.LTCP.attributes.IssueRemoveOnPut=false}}
>
> Most of the time JCS starts with the following logs
> {{{}16-Apr-2022 14:31:04.523 INFO [main]
> org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator. Using standard
> serializer
> [org.apache.commons.jcs3.utils.serialization.StandardSerializer@22aa6570] for
> auxiliary [jcs.auxiliary.LTCP]{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Instance for [] is null, creating{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Creating TCP service, lca = :1120{}}}{{{}16-Apr-2022 14:31:04.531 SEVERE
> [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService. Could
> not create sender to [] – Invalid address []{}}}{{{}16-Apr-2022 14:31:04.531
> SEVERE [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Failure, lateral instance will use zombie service{}}}{{
> java.io.IOException: Invalid address []}}{{ at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPSender.(LateralTCPSender.java:104)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService.(LateralTCPService.java:96)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.lambda$getCSNLInstance$0(LateralTCPCacheFactory.java:271)}}{{
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.getCSNLInstance(LateralTCPCacheFactory.java:251)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCacheNoWait(LateralTCPCacheFactory.java:143)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:110)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:56)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseAuxiliary(CompositeCacheConfigurator.java:450)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:234)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:157)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegions(CompositeCacheConfigurator.java:135)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.doConfigure(CompositeCacheManager.java:455)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:406)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:365)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:347)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:336)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManag
[jira] [Commented] (JCS-231) Lateral TCP cache goes in loop and consumes all available resources
[
https://issues.apache.org/jira/browse/JCS-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525608#comment-17525608
]
Thomas Vandahl commented on JCS-231:
Could you please re-run the process with debug-logs enabled and post the
results here?
> Lateral TCP cache goes in loop and consumes all available resources
> ---
>
> Key: JCS-231
> URL: https://issues.apache.org/jira/browse/JCS-231
> Project: Commons JCS
> Issue Type: Bug
>Affects Versions: jcs-3.1
> Environment: Linux, Tomcat 9, Adoption JDK 11
>Reporter: Andrea Vettori
>Priority: Major
>
> Hello, we upgraded from 3.0 to 3.1 and had to go back for the following
> problem.
> With this LTCP configuration
> {{jcs.auxiliary.LTCP=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory}}
> {{jcs.auxiliary.LTCP.attributes=org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.TCPLateralCacheAttributes}}
> {{jcs.auxiliary.LTCP.attributes.TcpListenerPort=1120}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryAddr=228.5.6.8}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryPort=6782}}
> {{jcs.auxiliary.LTCP.attributes.UdpDiscoveryEnabled=true}}
> {{jcs.auxiliary.LTCP.attributes.Receive=true}}
> {{jcs.auxiliary.LTCP.attributes.AllowGet=false}}
> {{jcs.auxiliary.LTCP.attributes.IssueRemoveOnPut=false}}
>
> Most of the time JCS starts with the following logs
> {{{}16-Apr-2022 14:31:04.523 INFO [main]
> org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator. Using standard
> serializer
> [org.apache.commons.jcs3.utils.serialization.StandardSerializer@22aa6570] for
> auxiliary [jcs.auxiliary.LTCP]{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Instance for [] is null, creating{}}}{{{}16-Apr-2022 14:31:04.524 INFO [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Creating TCP service, lca = :1120{}}}{{{}16-Apr-2022 14:31:04.531 SEVERE
> [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService. Could
> not create sender to [] – Invalid address []{}}}{{{}16-Apr-2022 14:31:04.531
> SEVERE [main]
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.
> Failure, lateral instance will use zombie service{}}}{{
> java.io.IOException: Invalid address []}}{{ at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPSender.(LateralTCPSender.java:104)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPService.(LateralTCPService.java:96)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.lambda$getCSNLInstance$0(LateralTCPCacheFactory.java:271)}}{{
> at
> java.base/java.util.concurrent.ConcurrentHashMap.compute(ConcurrentHashMap.java:1908)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.getCSNLInstance(LateralTCPCacheFactory.java:251)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCacheNoWait(LateralTCPCacheFactory.java:143)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:110)}}{{
> at
> org.apache.commons.jcs3.auxiliary.lateral.socket.tcp.LateralTCPCacheFactory.createCache(LateralTCPCacheFactory.java:56)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseAuxiliary(CompositeCacheConfigurator.java:450)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:234)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegion(CompositeCacheConfigurator.java:157)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator.parseRegions(CompositeCacheConfigurator.java:135)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.doConfigure(CompositeCacheManager.java:455)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:406)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:365)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:347)}}{{
> at
> org.apache.commons.jcs3.engine.control.CompositeCacheManager.configure(CompositeCacheManager.java:336)}}{{
> at
> org.apache.commons.jcs3.engine.
[jira] [Closed] (BEANUTILS-553) Introspection on lombok Class set first two letters of property name to uppercase in PropertyDescritor when just the second one was uppercase
[
https://issues.apache.org/jira/browse/BEANUTILS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edward gallego ruano closed BEANUTILS-553.
--
Resolution: Not A Bug
the Instrospection is maked for Java rt, not for apache commons-beantils.
> Introspection on lombok Class set first two letters of property name to
> uppercase in PropertyDescritor when just the second one was uppercase
> -
>
> Key: BEANUTILS-553
> URL: https://issues.apache.org/jira/browse/BEANUTILS-553
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
>Affects Versions: 1.9.4
> Environment: jdk1.8.0_141
> lombok 1.18.22
>Reporter: edward gallego ruano
>Priority: Major
>
> with Bean instance from a lombok class the Introspection set first two
> letters of property name to uppercase in PropertyDescritor when just the
> second one was uppercase:
> ej:
> {code:java}
> @Getter
> @Setter
> public Class MyBean {
> DPropertyType dPropertyName;
> }{code}
> then if we used de methods :
> {code:java}
> getPropertyUtils().isReadable(MyBeanInstance,"dPropertyName") or
> getPropertyUtils().isWriteable(MyBeanInstance,"dPropertyName")
> both return false{code}
> the Beans Specification paragraph 8.8 say :
> ??"...However to support the occasional use of all??
> ??upper-case names, we check if the first two characters of the name are both
> upper case and if??
> ??so leave it alone."??
> but the Instrospection inside those methods return data:
> {code:java}
> BeanIntrospectionData data = getIntrospectionData(bean.getClass()); {code}
> with the PropertyDescriptor:
> {code:java}
> [java.beans.PropertyDescriptor[name=DPropertyName; propertyType=class
> my.package.DPropertyType ; readMethod=public my.package.DPropertyType
> my.package.MyBean.getDPropertyName(); writeMethod=public void
> my.package.MyBean.setDPropertyName(my.package.DPropertyType)]] {code}
> but should be PropertyDescriptor:
> {code:java}
> [java.beans.PropertyDescriptor[name=dPropertyName; ..] {code}
> ?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (BEANUTILS-553) Introspection on lombok Class set first two letters of property name to uppercase in PropertyDescritor when just the second one was uppercase
[
https://issues.apache.org/jira/browse/BEANUTILS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525603#comment-17525603
]
edward gallego ruano commented on BEANUTILS-553:
the Instrocpection is maked for Java rt not for the commons-beanuils.
> Introspection on lombok Class set first two letters of property name to
> uppercase in PropertyDescritor when just the second one was uppercase
> -
>
> Key: BEANUTILS-553
> URL: https://issues.apache.org/jira/browse/BEANUTILS-553
> Project: Commons BeanUtils
> Issue Type: Bug
> Components: Bean / Property Utils
>Affects Versions: 1.9.4
> Environment: jdk1.8.0_141
> lombok 1.18.22
>Reporter: edward gallego ruano
>Priority: Major
>
> with Bean instance from a lombok class the Introspection set first two
> letters of property name to uppercase in PropertyDescritor when just the
> second one was uppercase:
> ej:
> {code:java}
> @Getter
> @Setter
> public Class MyBean {
> DPropertyType dPropertyName;
> }{code}
> then if we used de methods :
> {code:java}
> getPropertyUtils().isReadable(MyBeanInstance,"dPropertyName") or
> getPropertyUtils().isWriteable(MyBeanInstance,"dPropertyName")
> both return false{code}
> the Beans Specification paragraph 8.8 say :
> ??"...However to support the occasional use of all??
> ??upper-case names, we check if the first two characters of the name are both
> upper case and if??
> ??so leave it alone."??
> but the Instrospection inside those methods return data:
> {code:java}
> BeanIntrospectionData data = getIntrospectionData(bean.getClass()); {code}
> with the PropertyDescriptor:
> {code:java}
> [java.beans.PropertyDescriptor[name=DPropertyName; propertyType=class
> my.package.DPropertyType ; readMethod=public my.package.DPropertyType
> my.package.MyBean.getDPropertyName(); writeMethod=public void
> my.package.MyBean.setDPropertyName(my.package.DPropertyType)]] {code}
> but should be PropertyDescriptor:
> {code:java}
> [java.beans.PropertyDescriptor[name=dPropertyName; ..] {code}
> ?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (BEANUTILS-553) Introspection on lombok Class set first two letters of property name to uppercase in PropertyDescritor when just the second one was uppercase
edward gallego ruano created BEANUTILS-553:
--
Summary: Introspection on lombok Class set first two letters of
property name to uppercase in PropertyDescritor when just the second one was
uppercase
Key: BEANUTILS-553
URL: https://issues.apache.org/jira/browse/BEANUTILS-553
Project: Commons BeanUtils
Issue Type: Bug
Components: Bean / Property Utils
Affects Versions: 1.9.4
Environment: jdk1.8.0_141
lombok 1.18.22
Reporter: edward gallego ruano
with Bean instance from a lombok class the Introspection set first two letters
of property name to uppercase in PropertyDescritor when just the second one was
uppercase:
ej:
{code:java}
@Getter
@Setter
public Class MyBean {
DPropertyType dPropertyName;
}{code}
then if we used de methods :
{code:java}
getPropertyUtils().isReadable(MyBeanInstance,"dPropertyName") or
getPropertyUtils().isWriteable(MyBeanInstance,"dPropertyName")
both return false{code}
the Beans Specification paragraph 8.8 say :
??"...However to support the occasional use of all??
??upper-case names, we check if the first two characters of the name are both
upper case and if??
??so leave it alone."??
but the Instrospection inside those methods return data:
{code:java}
BeanIntrospectionData data = getIntrospectionData(bean.getClass()); {code}
with the PropertyDescriptor:
{code:java}
[java.beans.PropertyDescriptor[name=DPropertyName; propertyType=class
my.package.DPropertyType ; readMethod=public my.package.DPropertyType
my.package.MyBean.getDPropertyName(); writeMethod=public void
my.package.MyBean.setDPropertyName(my.package.DPropertyType)]] {code}
but should be PropertyDescriptor:
{code:java}
[java.beans.PropertyDescriptor[name=dPropertyName; ..] {code}
?
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[GitHub] [commons-vfs] boris-petrov commented on pull request #150: Call `refresh` by default in `AbstractFileObject.onChange`
boris-petrov commented on PR #150: URL: https://github.com/apache/commons-vfs/pull/150#issuecomment-1104793809 Well, as I've said in a [previous](https://github.com/apache/commons-vfs/pull/150#issuecomment-746511940) comment, there is some bug in the `RamFileProvider`. I've forgotten what the problem is. I guess someone would need to debug it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@commons.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
