[GitHub] [commons-cli] coveralls commented on pull request #85: Bump spotbugs-maven-plugin from 4.5.0.0 to 4.5.2.0
coveralls commented on pull request #85: URL: https://github.com/apache/commons-cli/pull/85#issuecomment-999346143 [](https://coveralls.io/builds/45180013) Coverage remained the same at 96.195% when pulling **df0745d42ac62f8a8206101e5a5d2143b725e3d9 on dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.5.2.0** into **0dfd09b047a7af80b557fe1ba8da43ea37d10568 on master**. -- 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-cli] dependabot[bot] opened a new pull request #85: Bump spotbugs-maven-plugin from 4.5.0.0 to 4.5.2.0
dependabot[bot] opened a new pull request #85: URL: https://github.com/apache/commons-cli/pull/85 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.5.0.0 to 4.5.2.0. Release notes Sourced from https://github.com/spotbugs/spotbugs-maven-plugin/releases;>spotbugs-maven-plugin's releases. Spotbugs-maven-plugin 4.5.2.0 Support spotbugs 4.5.2 Fix deprecations from spotbugs 4.5.0 Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/31d625f335d5403908b17b6a8d1957136f8f6bf3;>31d625f [maven-release-plugin] prepare release spotbugs-maven-plugin-4.5.2.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/3ed11ee444ee998431873eac82dd9a4b25e30afc;>3ed11ee Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/382;>#382 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/e047ca3d6b3c00c844eccebb443048ee0a5cc822;>e047ca3 [alignment] Update deprecated output argument for spotbugs 4.5.x https://github.com/spotbugs/spotbugs-maven-plugin/commit/e142e08dab1646b827dfd02373c733f33dfb4ec3;>e142e08 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/381;>#381 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/ad7e95d3ed6ed689f83a676a09239511f194be42;>ad7e95d [pom] Bump junit to 5.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/845c31b342c201c9c4db01c8b9a4f7322d7ad421;>845c31b [pom] Bump spotbugs to 4.5.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/2d5eecac972f34d6e1a61c0a84ea0f489fdb5b76;>2d5eeca [pom] Drop jgit back to 5.13.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/2ecb2776ea53173562002d5fa8da7b72b7caa9f9;>2ecb277 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/380;>#380 from spotbugs/dependabot/maven/doxiaSiteToolsVersion-... https://github.com/spotbugs/spotbugs-maven-plugin/commit/eaf27b75d2a10c861051e01a31cef9e784d202d5;>eaf27b7 Bump doxiaSiteToolsVersion from 1.10 to 1.11.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/39c92ba283dbcecc09268505ac54ce9cf06790f3;>39c92ba Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/379;>#379 from spotbugs/dependabot/maven/com.github.spotbugs-sp... Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.5.0.0...spotbugs-maven-plugin-4.5.2.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] [Closed] (DAEMON-436) jsvc Boot failure
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed DAEMON-436. - Fix Version/s: (was: 1.2.4) Resolution: Invalid As I have assumed you have obtained a stoneage executable from somewhere. You must compare from source on the same platform your JVM runs. Additional questions go to the mailing list. > jsvc Boot failure > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work logged] (LANG-1677) It should be possible to exclude fields in ReflectionDiffBuilder
[ https://issues.apache.org/jira/browse/LANG-1677?focusedWorklogId=699821=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-699821 ] ASF GitHub Bot logged work on LANG-1677: Author: ASF GitHub Bot Created on: 22/Dec/21 07:12 Start Date: 22/Dec/21 07:12 Worklog Time Spent: 10m Work Description: debae commented on pull request #838: URL: https://github.com/apache/commons-lang/pull/838#issuecomment-999338912 > See my previous comment. Hi @garydgregory , extra testcases have been added. -- 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 Issue Time Tracking --- Worklog Id: (was: 699821) Time Spent: 1h 20m (was: 1h 10m) > It should be possible to exclude fields in ReflectionDiffBuilder > > > Key: LANG-1677 > URL: https://issues.apache.org/jira/browse/LANG-1677 > Project: Commons Lang > Issue Type: Wish > Components: lang.builder.* >Affects Versions: 3.12.0 >Reporter: Dennis Baerten >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > When using ReflectionDiffBuilder to make a diff between two object it will be > default include all fields. As stated in the documentation static and > transient fields are excluded. > Using the transient modifier in combination with other frameworks ( such as > Hibernate ) also has a side affect that those fields are not persisted. > The use case I'm trying to solve it making a diff of an object that get's > updated and has a LastModificationDate and LastModificationUser and thus will > always be a field in the diff. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [commons-lang] debae commented on pull request #838: LANG-1677 : Add ReflectionDiffBuilder.setExcludeFieldNames(...) and DiffExclude a…
debae commented on pull request #838: URL: https://github.com/apache/commons-lang/pull/838#issuecomment-999338912 > See my previous comment. Hi @garydgregory , extra testcases have been added. -- 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 #56: Bump spotbugs-maven-plugin from 4.5.0.0 to 4.5.2.0
dependabot[bot] opened a new pull request #56: URL: https://github.com/apache/commons-build-plugin/pull/56 Bumps [spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 4.5.0.0 to 4.5.2.0. Release notes Sourced from https://github.com/spotbugs/spotbugs-maven-plugin/releases;>spotbugs-maven-plugin's releases. Spotbugs-maven-plugin 4.5.2.0 Support spotbugs 4.5.2 Fix deprecations from spotbugs 4.5.0 Commits https://github.com/spotbugs/spotbugs-maven-plugin/commit/31d625f335d5403908b17b6a8d1957136f8f6bf3;>31d625f [maven-release-plugin] prepare release spotbugs-maven-plugin-4.5.2.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/3ed11ee444ee998431873eac82dd9a4b25e30afc;>3ed11ee Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/382;>#382 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/e047ca3d6b3c00c844eccebb443048ee0a5cc822;>e047ca3 [alignment] Update deprecated output argument for spotbugs 4.5.x https://github.com/spotbugs/spotbugs-maven-plugin/commit/e142e08dab1646b827dfd02373c733f33dfb4ec3;>e142e08 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/381;>#381 from hazendaz/spotbugs https://github.com/spotbugs/spotbugs-maven-plugin/commit/ad7e95d3ed6ed689f83a676a09239511f194be42;>ad7e95d [pom] Bump junit to 5.8.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/845c31b342c201c9c4db01c8b9a4f7322d7ad421;>845c31b [pom] Bump spotbugs to 4.5.2 https://github.com/spotbugs/spotbugs-maven-plugin/commit/2d5eecac972f34d6e1a61c0a84ea0f489fdb5b76;>2d5eeca [pom] Drop jgit back to 5.13.0 https://github.com/spotbugs/spotbugs-maven-plugin/commit/2ecb2776ea53173562002d5fa8da7b72b7caa9f9;>2ecb277 Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/380;>#380 from spotbugs/dependabot/maven/doxiaSiteToolsVersion-... https://github.com/spotbugs/spotbugs-maven-plugin/commit/eaf27b75d2a10c861051e01a31cef9e784d202d5;>eaf27b7 Bump doxiaSiteToolsVersion from 1.10 to 1.11.1 https://github.com/spotbugs/spotbugs-maven-plugin/commit/39c92ba283dbcecc09268505ac54ce9cf06790f3;>39c92ba Merge pull request https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/379;>#379 from spotbugs/dependabot/maven/com.github.spotbugs-sp... Additional commits viewable in https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.5.0.0...spotbugs-maven-plugin-4.5.2.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-dbcp] dependabot[bot] commented on pull request #146: Bump mockito-core from 4.0.0 to 4.1.0
dependabot[bot] commented on pull request #146: URL: https://github.com/apache/commons-dbcp/pull/146#issuecomment-999278819 Superseded by #152. -- 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-dbcp] dependabot[bot] opened a new pull request #152: Bump mockito-core from 4.0.0 to 4.2.0
dependabot[bot] opened a new pull request #152: URL: https://github.com/apache/commons-dbcp/pull/152 Bumps [mockito-core](https://github.com/mockito/mockito) from 4.0.0 to 4.2.0. Release notes Sourced from https://github.com/mockito/mockito/releases;>mockito-core's releases. v4.2.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 4.2.0 2021-12-16 - https://github.com/mockito/mockito/compare/v4.1.0...v4.2.0;>21 commit(s) by Liam Miller-Cushon, Rafael Winterhalter, Tim van der Lippe, dependabot[bot], temp-droid Update ByteBuddy to 1.12.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2515;>#2515)](https://github-redirect.dependabot.com/mockito/mockito/pull/2515;>mockito/mockito#2515) Bump kotlinVersion from 1.6.0 to 1.6.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2514;>#2514)](https://github-redirect.dependabot.com/mockito/mockito/pull/2514;>mockito/mockito#2514) Add DoNotMock mention to main JavaDoc [(https://github-redirect.dependabot.com/mockito/mockito/issues/2512;>#2512)](https://github-redirect.dependabot.com/mockito/mockito/pull/2512;>mockito/mockito#2512) Replace ExpectedException in MissingInvocationInOrderCheckerTest [(https://github-redirect.dependabot.com/mockito/mockito/issues/2511;>#2511)](https://github-redirect.dependabot.com/mockito/mockito/pull/2511;>mockito/mockito#2511) Update Gradle to version 7.3.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2509;>#2509)](https://github-redirect.dependabot.com/mockito/mockito/pull/2509;>mockito/mockito#2509) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>#2497: Throw exception on invalid matchers for mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2506;>#2506)](https://github-redirect.dependabot.com/mockito/mockito/pull/2506;>mockito/mockito#2506) Make sure interface types are initialized before inline mocking to avoid blocking code of static initializers. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2505;>#2505)](https://github-redirect.dependabot.com/mockito/mockito/pull/2505;>mockito/mockito#2505) Bump org.eclipse.osgi from 3.17.0 to 3.17.100 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2504;>#2504)](https://github-redirect.dependabot.com/mockito/mockito/pull/2504;>mockito/mockito#2504) Bump com.diffplug.spotless from 6.0.2 to 6.0.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2501;>#2501)](https://github-redirect.dependabot.com/mockito/mockito/pull/2501;>mockito/mockito#2501) Bump com.diffplug.spotless from 6.0.1 to 6.0.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2498;>#2498)](https://github-redirect.dependabot.com/mockito/mockito/pull/2498;>mockito/mockito#2498) ArgumentMatchers not working for Mockito.mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>#2497)](https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>mockito/mockito#2497) Bump versions.bytebuddy from 1.12.2 to 1.12.3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2496;>#2496)](https://github-redirect.dependabot.com/mockito/mockito/pull/2496;>mockito/mockito#2496) Bump com.diffplug.spotless from 6.0.0 to 6.0.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2495;>#2495)](https://github-redirect.dependabot.com/mockito/mockito/pull/2495;>mockito/mockito#2495) Remove the recommendation to import ArgumentMatchers methods using Mockito [(https://github-redirect.dependabot.com/mockito/mockito/issues/2494;>#2494)](https://github-redirect.dependabot.com/mockito/mockito/pull/2494;>mockito/mockito#2494) Bump versions.junitJupiter from 5.8.1 to 5.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2491;>#2491)](https://github-redirect.dependabot.com/mockito/mockito/pull/2491;>mockito/mockito#2491) Bump junit-platform-launcher from 1.8.1 to 1.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2490;>#2490)](https://github-redirect.dependabot.com/mockito/mockito/pull/2490;>mockito/mockito#2490) Fix typo 'DoNoMock' should be 'DoNotMock' [(https://github-redirect.dependabot.com/mockito/mockito/issues/2487;>#2487)](https://github-redirect.dependabot.com/mockito/mockito/pull/2487;>mockito/mockito#2487) Bump biz.aQute.bnd.gradle from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2486;>#2486)](https://github-redirect.dependabot.com/mockito/mockito/pull/2486;>mockito/mockito#2486) Bump biz.aQute.bnd.builder from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2485;>#2485)](https://github-redirect.dependabot.com/mockito/mockito/pull/2485;>mockito/mockito#2485) Bump versions.bytebuddy from 1.12.1 to 1.12.2
[GitHub] [commons-dbcp] dependabot[bot] closed pull request #146: Bump mockito-core from 4.0.0 to 4.1.0
dependabot[bot] closed pull request #146: URL: https://github.com/apache/commons-dbcp/pull/146 -- 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] (DAEMON-436) jsvc Boot failure
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sunly updated DAEMON-436: - Summary: jsvc Boot failure (was: jsvc 启动失败) > jsvc Boot failure > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463556#comment-17463556 ] sunly edited comment on DAEMON-436 at 12/22/21, 3:10 AM: - Please see this is my output following your guidance： # file jsvc jsvc: executable (RISC System/6000) or object module not stripped # file /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so: 64-bit XCOFF executable or object module not stripped was (Author: JIRAUSER282374): # file jsvc jsvc: executable (RISC System/6000) or object module not stripped # file /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so: 64-bit XCOFF executable or object module not stripped > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463558#comment-17463558 ] sunly commented on DAEMON-436: -- 我非常感谢楼上帮我解答，我很抱歉我不会说英语，现在我用翻译软件翻译出来，请您继续为我解答。谢谢。 > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436 ] sunly deleted comment on DAEMON-436: -- was (Author: JIRAUSER282374): 我非常感谢楼上帮我解答，我很抱歉我不会说英语，现在我用翻译软件翻译出来，请您继续为我解答。谢谢。 > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463559#comment-17463559 ] sunly commented on DAEMON-436: -- Thank you very much for your help. I'm sorry that I can't speak English. Now I will use the translation software to translate it. thank you > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463556#comment-17463556 ] sunly commented on DAEMON-436: -- # file jsvc jsvc: executable (RISC System/6000) or object module not stripped # file /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so: 64-bit XCOFF executable or object module not stripped > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [commons-vfs] XenoAmess commented on a change in pull request #228: [VFS-812] fix bug about closing file content output stream when using BufferedOutputStream
XenoAmess commented on a change in pull request #228:
URL: https://github.com/apache/commons-vfs/pull/228#discussion_r773362057
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
So I don't think we really need to forbidden **flush** after **close**.
Just do nothing and return should be fine IMO
--
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-vfs] XenoAmess commented on a change in pull request #228: [VFS-812] fix bug about closing file content output stream when using BufferedOutputStream
XenoAmess commented on a change in pull request #228:
URL: https://github.com/apache/commons-vfs/pull/228#discussion_r773360784
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
I think it can be fixed this way because:
1. we will invoke **flush** when **close**.
2. after invoke **close**, every operations that will try to add something
to the buffer would cause a FileSystemException
3. then if invoke **flush** after **close**, there should be actually
nothing to flush
--
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-vfs] XenoAmess commented on a change in pull request #228: [VFS-812] fix bug about closing file content output stream when using BufferedOutputStream
XenoAmess commented on a change in pull request #228:
URL: https://github.com/apache/commons-vfs/pull/228#discussion_r773360784
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
I think it can be fixed this way because:
1. we will invoke **flush** when **close**.
2. after invoke **close**, every operations that will try to add something
to the buffer would cause a FileSystemException
3. then if invoke **flush** after **close**, there shouold actually nothing
to flush
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
I think it can be fixed this way because:
1. we will invoke **flush** when **close**.
2. after invoke **close**, every operations that will try to add something
to the buffer would cause a FileSystemException
3. then if invoke **flush** after **close**, there should actually nothing
to flush
--
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-vfs] XenoAmess commented on a change in pull request #228: fix bug about closing file content output stream when using BufferedOutputStream
XenoAmess commented on a change in pull request #228:
URL: https://github.com/apache/commons-vfs/pull/228#discussion_r773360784
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
I think it can be fixed this way because:
1. we will invoke **flush** when **close**.
2. after invoke **close**, every operations that will try to add something
to the buffer would cause a FileSystemException
3. then if invoke **flush** after close, there shouold actually nothing to
flush
--
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-vfs] garydgregory commented on a change in pull request #228: fix bug about closing file content output stream when using BufferedOutputStream
garydgregory commented on a change in pull request #228:
URL: https://github.com/apache/commons-vfs/pull/228#discussion_r773360575
##
File path:
commons-vfs2/src/main/java/org/apache/commons/vfs2/util/MonitorOutputStream.java
##
@@ -121,7 +121,9 @@ public void close() throws IOException {
*/
@Override
public synchronized void flush() throws IOException {
-assertOpen();
Review comment:
Why was the open check completely removed?
--
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] (VFS-812) fix bug about closing file content output stream when using BufferedOutputStream
[ https://issues.apache.org/jira/browse/VFS-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jin Xu updated VFS-812: --- Description: fix bug about closing file content output stream when using BufferedOutputStream see the test for details. https://github.com/apache/commons-vfs/pull/228 was: fix bug about closing file content output stream when using BufferedOutputStream see the test for details. > fix bug about closing file content output stream when using > BufferedOutputStream > > > Key: VFS-812 > URL: https://issues.apache.org/jira/browse/VFS-812 > Project: Commons VFS > Issue Type: Improvement >Reporter: Jin Xu >Priority: Minor > > fix bug about closing file content output stream when using > BufferedOutputStream > see the test for details. > https://github.com/apache/commons-vfs/pull/228 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (VFS-812) fix bug about closing file content output stream when using BufferedOutputStream
Jin Xu created VFS-812: -- Summary: fix bug about closing file content output stream when using BufferedOutputStream Key: VFS-812 URL: https://issues.apache.org/jira/browse/VFS-812 Project: Commons VFS Issue Type: Improvement Reporter: Jin Xu fix bug about closing file content output stream when using BufferedOutputStream see the test for details. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (COMPRESS-602) Migrate zip package to java.nio.file.Path usage
[ https://issues.apache.org/jira/browse/COMPRESS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463352#comment-17463352 ] Gary D. Gregory commented on COMPRESS-602: -- Keep in mind that IO and NIO have some differences which might be tricky to account for, at least that is based on experience in Apache Commons IO. > Migrate zip package to java.nio.file.Path usage > --- > > Key: COMPRESS-602 > URL: https://issues.apache.org/jira/browse/COMPRESS-602 > Project: Commons Compress > Issue Type: Sub-task >Reporter: Postelnicu George >Priority: Major > > Migrate the core functionality of org/apache/commons/compress/archivers/zip > package to run with java.nio.file.Path instead of java.io.File -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (COMPRESS-602) Migrate zip package to java.nio.file.Path usage
[ https://issues.apache.org/jira/browse/COMPRESS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463336#comment-17463336 ] Postelnicu George commented on COMPRESS-602: [~ggregory] thank you, I will create the PR when I have covered most of the classes, at the moment I migrated the ZipSplitOutputStream without breaking backwards compatibility and added Memory filesystem tests for all types of constructors from ZipOutputStream. > Migrate zip package to java.nio.file.Path usage > --- > > Key: COMPRESS-602 > URL: https://issues.apache.org/jira/browse/COMPRESS-602 > Project: Commons Compress > Issue Type: Sub-task >Reporter: Postelnicu George >Priority: Major > > Migrate the core functionality of org/apache/commons/compress/archivers/zip > package to run with java.nio.file.Path instead of java.io.File -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (COMPRESS-602) Migrate zip package to java.nio.file.Path usage
[ https://issues.apache.org/jira/browse/COMPRESS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=1746#comment-1746 ] Gary D. Gregory commented on COMPRESS-602: -- Sounds reasonable. Feel free to provide a PR on GitHub, just don't break binary compatibility, the default Maven build should tell you. > Migrate zip package to java.nio.file.Path usage > --- > > Key: COMPRESS-602 > URL: https://issues.apache.org/jira/browse/COMPRESS-602 > Project: Commons Compress > Issue Type: Sub-task >Reporter: Postelnicu George >Priority: Major > > Migrate the core functionality of org/apache/commons/compress/archivers/zip > package to run with java.nio.file.Path instead of java.io.File -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (COMPRESS-602) Migrate zip package to java.nio.file.Path usage
Postelnicu George created COMPRESS-602: -- Summary: Migrate zip package to java.nio.file.Path usage Key: COMPRESS-602 URL: https://issues.apache.org/jira/browse/COMPRESS-602 Project: Commons Compress Issue Type: Sub-task Reporter: Postelnicu George Migrate the core functionality of org/apache/commons/compress/archivers/zip package to run with java.nio.file.Path instead of java.io.File -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [commons-jcs] garydgregory merged pull request #79: Bump log4j-api from 2.16.0 to 2.17.0
garydgregory merged pull request #79: URL: https://github.com/apache/commons-jcs/pull/79 -- 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] (FILEUPLOAD-309) Release version 2.0.0
[ https://issues.apache.org/jira/browse/FILEUPLOAD-309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463250#comment-17463250 ] Martin Tzvetanov Grigorov commented on FILEUPLOAD-309: -- [~basil] https://repository.apache.org/content/repositories/snapshots/org/apache/commons/commons-fileupload2/2.0-SNAPSHOT/ > Release version 2.0.0 > - > > Key: FILEUPLOAD-309 > URL: https://issues.apache.org/jira/browse/FILEUPLOAD-309 > Project: Commons FileUpload > Issue Type: Wish >Reporter: Thiago Henrique Hupner >Priority: Major > > At Piranha, we've migrated to use the new Jakarta namespace. > One of our dependencies is the Commons File Upload, but the latest version > available is 1.4. > Looking around at the source code, I've found that the code is already > prepared for the new Jakarta namespace. > So, I want to know if there's a plan to release a new version soon. Or at > least a 2.0.0 milestone. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[
https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463158#comment-17463158
]
Michael Osipov commented on DAEMON-436:
---
It is every likely, but jvsc and the JVM are in different arch formats.
Please provide the output of:
{noformat}
$ file jsvc
$ file /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
{noformat}
> jsvc 启动失败
> -
>
> Key: DAEMON-436
> URL: https://issues.apache.org/jira/browse/DAEMON-436
> Project: Commons Daemon
> Issue Type: Bug
> Components: Jsvc
>Affects Versions: 1.2.4
> Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link
> to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version
> "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed
> References 20211022_15212 (JIT enabled, AOT enabled)
>Reporter: sunly
>Priority: Major
> Labels: patch
> Fix For: 1.2.4
>
> Attachments: minion_jsvc.sh
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题：
> Switching umask from 022 to 022
> Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so.
> System error: Exec format error
> java_init failed
> remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3
> Service exit with a return value of 1
> 这是启动脚本：请看附件
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463157#comment-17463157 ] Michael Osipov commented on DAEMON-436: --- [~markt], no doubt, but we can expect people at least tell that they barely or don't speak English. > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[
https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463151#comment-17463151
]
Mark Thomas commented on DAEMON-436:
Translation of the description:
{code:java}
For java applications, the jsvc application fails to start on aix7.1.3, and the
following problems occur:
Switching umask from 022 to 022
Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so.
System error: Exec format error
java_init failed
remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3
Service exit with a return value of 1
This is the startup script: please see the attachment {code}
> jsvc 启动失败
> -
>
> Key: DAEMON-436
> URL: https://issues.apache.org/jira/browse/DAEMON-436
> Project: Commons Daemon
> Issue Type: Bug
> Components: Jsvc
>Affects Versions: 1.2.4
> Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link
> to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version
> "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed
> References 20211022_15212 (JIT enabled, AOT enabled)
>Reporter: sunly
>Priority: Major
> Labels: patch
> Fix For: 1.2.4
>
> Attachments: minion_jsvc.sh
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题：
> Switching umask from 022 to 022
> Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so
> Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so.
> System error: Exec format error
> java_init failed
> remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3
> Service exit with a return value of 1
> 这是启动脚本：请看附件
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463149#comment-17463149 ] Mark Thomas commented on DAEMON-436: There is no need for that sort of attitude. Not everyone speaks English. Google translate usually provides a good enough translation to figure out what the problem is. > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (DAEMON-436) jsvc 启动失败
[ https://issues.apache.org/jira/browse/DAEMON-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463097#comment-17463097 ] Michael Osipov commented on DAEMON-436: --- Write in English or I will close the issue. > jsvc 启动失败 > - > > Key: DAEMON-436 > URL: https://issues.apache.org/jira/browse/DAEMON-436 > Project: Commons Daemon > Issue Type: Bug > Components: Jsvc >Affects Versions: 1.2.4 > Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link > to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version > "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed > References 20211022_15212 (JIT enabled, AOT enabled) >Reporter: sunly >Priority: Major > Labels: patch > Fix For: 1.2.4 > > Attachments: minion_jsvc.sh > > Original Estimate: 12h > Remaining Estimate: 12h > > java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： > Switching umask from 022 to 022 > Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so > Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. > System error: Exec format error > java_init failed > remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 > Service exit with a return value of 1 > 这是启动脚本：请看附件 > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [commons-dbutils] dependabot[bot] opened a new pull request #97: Bump mockito-core from 3.7.0 to 4.2.0
dependabot[bot] opened a new pull request #97: URL: https://github.com/apache/commons-dbutils/pull/97 Bumps [mockito-core](https://github.com/mockito/mockito) from 3.7.0 to 4.2.0. Release notes Sourced from https://github.com/mockito/mockito/releases;>mockito-core's releases. v4.2.0 Changelog generated by https://github.com/shipkit/shipkit-changelog;>Shipkit Changelog Gradle Plugin 4.2.0 2021-12-16 - https://github.com/mockito/mockito/compare/v4.1.0...v4.2.0;>21 commit(s) by Liam Miller-Cushon, Rafael Winterhalter, Tim van der Lippe, dependabot[bot], temp-droid Update ByteBuddy to 1.12.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2515;>#2515)](https://github-redirect.dependabot.com/mockito/mockito/pull/2515;>mockito/mockito#2515) Bump kotlinVersion from 1.6.0 to 1.6.10 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2514;>#2514)](https://github-redirect.dependabot.com/mockito/mockito/pull/2514;>mockito/mockito#2514) Add DoNotMock mention to main JavaDoc [(https://github-redirect.dependabot.com/mockito/mockito/issues/2512;>#2512)](https://github-redirect.dependabot.com/mockito/mockito/pull/2512;>mockito/mockito#2512) Replace ExpectedException in MissingInvocationInOrderCheckerTest [(https://github-redirect.dependabot.com/mockito/mockito/issues/2511;>#2511)](https://github-redirect.dependabot.com/mockito/mockito/pull/2511;>mockito/mockito#2511) Update Gradle to version 7.3.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2509;>#2509)](https://github-redirect.dependabot.com/mockito/mockito/pull/2509;>mockito/mockito#2509) Fixes https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>#2497: Throw exception on invalid matchers for mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2506;>#2506)](https://github-redirect.dependabot.com/mockito/mockito/pull/2506;>mockito/mockito#2506) Make sure interface types are initialized before inline mocking to avoid blocking code of static initializers. [(https://github-redirect.dependabot.com/mockito/mockito/issues/2505;>#2505)](https://github-redirect.dependabot.com/mockito/mockito/pull/2505;>mockito/mockito#2505) Bump org.eclipse.osgi from 3.17.0 to 3.17.100 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2504;>#2504)](https://github-redirect.dependabot.com/mockito/mockito/pull/2504;>mockito/mockito#2504) Bump com.diffplug.spotless from 6.0.2 to 6.0.4 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2501;>#2501)](https://github-redirect.dependabot.com/mockito/mockito/pull/2501;>mockito/mockito#2501) Bump com.diffplug.spotless from 6.0.1 to 6.0.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2498;>#2498)](https://github-redirect.dependabot.com/mockito/mockito/pull/2498;>mockito/mockito#2498) ArgumentMatchers not working for Mockito.mockStatic [(https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>#2497)](https://github-redirect.dependabot.com/mockito/mockito/issues/2497;>mockito/mockito#2497) Bump versions.bytebuddy from 1.12.2 to 1.12.3 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2496;>#2496)](https://github-redirect.dependabot.com/mockito/mockito/pull/2496;>mockito/mockito#2496) Bump com.diffplug.spotless from 6.0.0 to 6.0.1 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2495;>#2495)](https://github-redirect.dependabot.com/mockito/mockito/pull/2495;>mockito/mockito#2495) Remove the recommendation to import ArgumentMatchers methods using Mockito [(https://github-redirect.dependabot.com/mockito/mockito/issues/2494;>#2494)](https://github-redirect.dependabot.com/mockito/mockito/pull/2494;>mockito/mockito#2494) Bump versions.junitJupiter from 5.8.1 to 5.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2491;>#2491)](https://github-redirect.dependabot.com/mockito/mockito/pull/2491;>mockito/mockito#2491) Bump junit-platform-launcher from 1.8.1 to 1.8.2 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2490;>#2490)](https://github-redirect.dependabot.com/mockito/mockito/pull/2490;>mockito/mockito#2490) Fix typo 'DoNoMock' should be 'DoNotMock' [(https://github-redirect.dependabot.com/mockito/mockito/issues/2487;>#2487)](https://github-redirect.dependabot.com/mockito/mockito/pull/2487;>mockito/mockito#2487) Bump biz.aQute.bnd.gradle from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2486;>#2486)](https://github-redirect.dependabot.com/mockito/mockito/pull/2486;>mockito/mockito#2486) Bump biz.aQute.bnd.builder from 6.0.0 to 6.1.0 [(https://github-redirect.dependabot.com/mockito/mockito/issues/2485;>#2485)](https://github-redirect.dependabot.com/mockito/mockito/pull/2485;>mockito/mockito#2485) Bump versions.bytebuddy from 1.12.1 to 1.12.2
[GitHub] [commons-dbutils] dependabot[bot] commented on pull request #95: Bump mockito-core from 3.7.0 to 4.1.0
dependabot[bot] commented on pull request #95: URL: https://github.com/apache/commons-dbutils/pull/95#issuecomment-998627432 Superseded by #97. -- 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-dbutils] dependabot[bot] closed pull request #95: Bump mockito-core from 3.7.0 to 4.1.0
dependabot[bot] closed pull request #95: URL: https://github.com/apache/commons-dbutils/pull/95 -- 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] [Created] (DAEMON-436) jsvc 启动失败
sunly created DAEMON-436: Summary: jsvc 启动失败 Key: DAEMON-436 URL: https://issues.apache.org/jira/browse/DAEMON-436 Project: Commons Daemon Issue Type: Bug Components: Jsvc Affects Versions: 1.2.4 Environment: 在aix7.1.3环境上编译jsvc通过了，但是启动的时候出现在Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so，我使用的java version "1.8.0_311"，IBM J9 VM (build 2.9, JRE 1.8.0 AIX ppc64-64-Bit Compressed References 20211022_15212 (JIT enabled, AOT enabled) Reporter: sunly Fix For: 1.2.4 Attachments: minion_jsvc.sh java应用，在aix7.1.3上启动jsvc应用失败，出现一下问题： Switching umask from 022 to 022 Using default JVM in /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so Attemtping to load library /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so Cannot dynamically link to /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so Could not load module /usr/java8_64/jre/lib/ppc64/j9vm/libjvm.so. System error: Exec format error java_init failed remove_pid_file: open /home/minion/cc-product-minion/temp/miniond.pid: fd=3 Service exit with a return value of 1 这是启动脚本：请看附件 -- This message was sent by Atlassian Jira (v8.20.1#820001)
