[jira] [Created] (TOMEE-4231) Backport Fix for CVE-2023-28709 in TomEE 9
Cesar Hernandez created TOMEE-4231: -- Summary: Backport Fix for CVE-2023-28709 in TomEE 9 Key: TOMEE-4231 URL: https://issues.apache.org/jira/browse/TOMEE-4231 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 9.1.0 Reporter: Cesar Hernandez https://nvd.nist.gov/vuln/detail/CVE-2023-28709 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (TOMEE-4196) Migrate to Jenkins pipelines
[ https://issues.apache.org/jira/browse/TOMEE-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-4196 started by Cesar Hernandez. -- > Migrate to Jenkins pipelines > > > Key: TOMEE-4196 > URL: https://issues.apache.org/jira/browse/TOMEE-4196 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > > Since the last apache builds upgraded to newestJenkins, we had issues with > tomEE 8 jobs. Richard created freestyle jobs to recover the functionality the > Maven jobs previously had. > We can iterate migration to Jenkins pipelines and open the traceability via > git for the pipelines builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4196) Migrate to Jenkins pipelines
[ https://issues.apache.org/jira/browse/TOMEE-4196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17726006#comment-17726006 ] Cesar Hernandez commented on TOMEE-4196: First PR with the proposed migration from existing Jobs into pipelines: [https://github.com/apache/tomee/pull/1049/] Notice that the type of machine used allows us now to have a full build of 2 hours instead of ~4.5 we currently have. > Migrate to Jenkins pipelines > > > Key: TOMEE-4196 > URL: https://issues.apache.org/jira/browse/TOMEE-4196 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > > Since the last apache builds upgraded to newestJenkins, we had issues with > tomEE 8 jobs. Richard created freestyle jobs to recover the functionality the > Maven jobs previously had. > We can iterate migration to Jenkins pipelines and open the traceability via > git for the pipelines builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TOMEE-4196) Migrate to Jenkins pipelines
Cesar Hernandez created TOMEE-4196: -- Summary: Migrate to Jenkins pipelines Key: TOMEE-4196 URL: https://issues.apache.org/jira/browse/TOMEE-4196 Project: TomEE Issue Type: Task Reporter: Cesar Hernandez Assignee: Cesar Hernandez Since the last apache builds upgraded to newestJenkins, we had issues with tomEE 8 jobs. Richard created freestyle jobs to recover the functionality the Maven jobs previously had. We can iterate migration to Jenkins pipelines and open the traceability via git for the pipelines builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (TOMEE-4193) Website eol pages
[ https://issues.apache.org/jira/browse/TOMEE-4193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-4193: -- Assignee: Cesar Hernandez > Website eol pages > - > > Key: TOMEE-4193 > URL: https://issues.apache.org/jira/browse/TOMEE-4193 > Project: TomEE > Issue Type: Documentation >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > > A follow up task from TOMEE-4186 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TOMEE-4193) Website eol pages
Cesar Hernandez created TOMEE-4193: -- Summary: Website eol pages Key: TOMEE-4193 URL: https://issues.apache.org/jira/browse/TOMEE-4193 Project: TomEE Issue Type: Documentation Reporter: Cesar Hernandez A follow up task from TOMEE-4186 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TOMEE-4186) Update download page for discontinued branches
[ https://issues.apache.org/jira/browse/TOMEE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-4186: --- Fix Version/s: 9.0.1 > Update download page for discontinued branches > -- > > Key: TOMEE-4186 > URL: https://issues.apache.org/jira/browse/TOMEE-4186 > Project: TomEE > Issue Type: Documentation >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TOMEE-4186) Update download page for discontinued branches
[ https://issues.apache.org/jira/browse/TOMEE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-4186. Resolution: Done > Update download page for discontinued branches > -- > > Key: TOMEE-4186 > URL: https://issues.apache.org/jira/browse/TOMEE-4186 > Project: TomEE > Issue Type: Documentation >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (TOMEE-4186) Update download page for discontinued branches
[ https://issues.apache.org/jira/browse/TOMEE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-4186: -- Assignee: Cesar Hernandez > Update download page for discontinued branches > -- > > Key: TOMEE-4186 > URL: https://issues.apache.org/jira/browse/TOMEE-4186 > Project: TomEE > Issue Type: Documentation >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4185) Dependencies cleanup
[ https://issues.apache.org/jira/browse/TOMEE-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17690032#comment-17690032 ] Cesar Hernandez commented on TOMEE-4185: Thank you for the ticket and PR(s) work I see has been doing already for this Jira. I see current PR [https://github.com/apache/tomee/pull/1024] is pointing to 8.0.x branch. I thought this Jira was related to 10.x only. I tried to find more context around this ticket on the mailing list but I didn't succeed. My only comment on doing dependencies cleanup on 8.0.x PR's, reviews, and CI cycles, is about the overall return of investment it would have in comparison to putting our effort into Jakarta EE 10 for 10.0.x branch, based on the latest discussion in the mailing list around branches roadmap: main (10.0.x), 9.0.x, and 8.0.x. > Dependencies cleanup > > > Key: TOMEE-4185 > URL: https://issues.apache.org/jira/browse/TOMEE-4185 > Project: TomEE > Issue Type: Dependency upgrade >Reporter: Gwénaël Ruelland >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > improving pom quality by: > * ordering dependencies > * adding properties for versions > * removing unused dependencies > * upgrading dependencies when there is multiple versions for single > dependency -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4186) Update download page for discontinued branches
[ https://issues.apache.org/jira/browse/TOMEE-4186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17689822#comment-17689822 ] Cesar Hernandez commented on TOMEE-4186: PR available https://github.com/apache/tomee-site-generator/pull/59 > Update download page for discontinued branches > -- > > Key: TOMEE-4186 > URL: https://issues.apache.org/jira/browse/TOMEE-4186 > Project: TomEE > Issue Type: Documentation >Reporter: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TOMEE-4186) Update download page for discontinued branches
Cesar Hernandez created TOMEE-4186: -- Summary: Update download page for discontinued branches Key: TOMEE-4186 URL: https://issues.apache.org/jira/browse/TOMEE-4186 Project: TomEE Issue Type: Documentation Reporter: Cesar Hernandez -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-4178. Resolution: Done > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17688727#comment-17688727 ] Cesar Hernandez commented on TOMEE-4178: I fixed last week [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-owasp-check/] job and today created: [https://ci-builds.apache.org/job/TomEE/job/pull-request-9.x-manual/] Closing now this ticket since 9.x jobs were created and are up and running. > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work stopped] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-4178 stopped by Cesar Hernandez. -- > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17682305#comment-17682305 ] Cesar Hernandez commented on TOMEE-4178: The following Jobs were created for 9.x branch: * [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-sanity-checks/] * [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-build-quick/] * [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-deploy/] * [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-owasp-check/] * [https://ci-builds.apache.org/job/TomEE/job/tomee-9.x-build-full/] I'll check tomorrow how they all run since, currently, there is a queue for available executors. > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-4178 started by Cesar Hernandez. -- > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678959#comment-17678959 ] Cesar Hernandez commented on TOMEE-4178: Thank you for the feedback [~rzo1] . I'll work on the job structure and update the ticket accordingly. > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678445#comment-17678445 ] Cesar Hernandez edited comment on TOMEE-4178 at 1/19/23 1:25 AM: - Hi [~jlmonteiro] , Currently I see the following Jobs for maintenance 8.x: tomee-8.x-build-quick tomee-8.x-deploy tomee-8.x-owasp-check tomee-8.x-sanity-checks And the followings for master: master-build-full master-build-full-arquillian master-build-full-examples master-build-full-itests master-build-full-tck master-build-quick master-deploy master-owasp-check master-pull-request master-sanity-checks Do I create the 9.x jobs taking as a base the number of jobs for current 8.x or master? was (Author: cesarhernandezgt): Hi [~jlmonteiro] , Currently I see the following Jobs for maintenance 8.x: tomee-8.x-build-quick tomee-8.x-deploy tomee-8.x-owasp-check tomee-8.x-sanity-checks And the followings for master: master-build-full master-build-full-arquillian master-build-full-examples master-build-full-itests master-build-full-tck master-build-quick master-deploy master-owasp-check master-pull-request master-sanity-checks Do I create the 9.x jobs takins as a base the number of jobs for current 8.x or master? > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
[ https://issues.apache.org/jira/browse/TOMEE-4178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678445#comment-17678445 ] Cesar Hernandez commented on TOMEE-4178: Hi [~jlmonteiro] , Currently I see the following Jobs for maintenance 8.x: tomee-8.x-build-quick tomee-8.x-deploy tomee-8.x-owasp-check tomee-8.x-sanity-checks And the followings for master: master-build-full master-build-full-arquillian master-build-full-examples master-build-full-itests master-build-full-tck master-build-quick master-deploy master-owasp-check master-pull-request master-sanity-checks Do I create the 9.x jobs takins as a base the number of jobs for current 8.x or master? > create jenkins jobs for TomEE 9.x maintenance > - > > Key: TOMEE-4178 > URL: https://issues.apache.org/jira/browse/TOMEE-4178 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TOMEE-4178) create jenkins jobs for TomEE 9.x maintenance
Cesar Hernandez created TOMEE-4178: -- Summary: create jenkins jobs for TomEE 9.x maintenance Key: TOMEE-4178 URL: https://issues.apache.org/jira/browse/TOMEE-4178 Project: TomEE Issue Type: Task Reporter: Cesar Hernandez Assignee: Cesar Hernandez -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4106) TomEE version no longer appearing at default manager page
[ https://issues.apache.org/jira/browse/TOMEE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17640965#comment-17640965 ] Cesar Hernandez commented on TOMEE-4106: This was addressed via [https://github.com/apache/tomee/commit/1dec9af163383108d24010ebc72c585aa7b21757] and related to https://issues.apache.org/jira/browse/TOMEE-4014. Thank you [~rzo1] ! > TomEE version no longer appearing at default manager page > - > > Key: TOMEE-4106 > URL: https://issues.apache.org/jira/browse/TOMEE-4106 > Project: TomEE > Issue Type: Bug >Affects Versions: 8.0.13 >Reporter: Cesar Hernandez >Priority: Minor > Fix For: 8.0.14 > > Attachments: image-2022-10-31-17-02-37-159.png, > image-2022-10-31-17-02-56-820.png > > > TomEE 8.0.12 : > !image-2022-10-31-17-02-37-159.png! > > TomEE 8.0.13 > !image-2022-10-31-17-02-56-820.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (TOMEE-4106) TomEE version no longer appearing at default manager page
[ https://issues.apache.org/jira/browse/TOMEE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-4106: -- Assignee: Richard Zowalla > TomEE version no longer appearing at default manager page > - > > Key: TOMEE-4106 > URL: https://issues.apache.org/jira/browse/TOMEE-4106 > Project: TomEE > Issue Type: Bug >Affects Versions: 8.0.13 >Reporter: Cesar Hernandez >Assignee: Richard Zowalla >Priority: Minor > Fix For: 8.0.14 > > Attachments: image-2022-10-31-17-02-37-159.png, > image-2022-10-31-17-02-56-820.png > > > TomEE 8.0.12 : > !image-2022-10-31-17-02-37-159.png! > > TomEE 8.0.13 > !image-2022-10-31-17-02-56-820.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TOMEE-4106) TomEE version no longer appearing at default manager page
[ https://issues.apache.org/jira/browse/TOMEE-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-4106. Resolution: Fixed > TomEE version no longer appearing at default manager page > - > > Key: TOMEE-4106 > URL: https://issues.apache.org/jira/browse/TOMEE-4106 > Project: TomEE > Issue Type: Bug >Affects Versions: 8.0.13 >Reporter: Cesar Hernandez >Assignee: Richard Zowalla >Priority: Minor > Fix For: 8.0.14 > > Attachments: image-2022-10-31-17-02-37-159.png, > image-2022-10-31-17-02-56-820.png > > > TomEE 8.0.12 : > !image-2022-10-31-17-02-37-159.png! > > TomEE 8.0.13 > !image-2022-10-31-17-02-56-820.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (TOMEE-4106) TomEE version no longer appearing at default manager page
Cesar Hernandez created TOMEE-4106: -- Summary: TomEE version no longer appearing at default manager page Key: TOMEE-4106 URL: https://issues.apache.org/jira/browse/TOMEE-4106 Project: TomEE Issue Type: Bug Affects Versions: 8.0.13 Reporter: Cesar Hernandez Fix For: 8.0.14 Attachments: image-2022-10-31-17-02-37-159.png, image-2022-10-31-17-02-56-820.png TomEE 8.0.12 : !image-2022-10-31-17-02-37-159.png! TomEE 8.0.13 !image-2022-10-31-17-02-56-820.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (TOMEE-4001) CVE-2022-34305 displaying user provided data without filtering, exposing a XSS vulnerability
[
https://issues.apache.org/jira/browse/TOMEE-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601496#comment-17601496
]
Cesar Hernandez commented on TOMEE-4001:
Thank you [~9177012889] for the reporting and [~rzo1] the patch.
As a side note, notice that this CVE affects the tomcat examples application.
TomEE doesn't provide the examples application.
!image-2022-09-07-13-50-40-452.png!
{code:java}
tree webapps -D -L 1
[Sep 7 13:34] webapps
├── [Jun 28 10:05] ROOT
├── [Jun 28 10:05] docs
├── [Jun 28 10:05] host-manager
└── [Jun 28 10:05] manager{code}
> CVE-2022-34305 displaying user provided data without filtering, exposing a
> XSS vulnerability
>
>
> Key: TOMEE-4001
> URL: https://issues.apache.org/jira/browse/TOMEE-4001
> Project: TomEE
> Issue Type: Dependency upgrade
> Components: TomEE Core Server
>Affects Versions: 9.0.0-M8, 8.0.12
>Reporter: Yugandher reddy vonteddu
>Assignee: Richard Zowalla
>Priority: Major
> Labels: CVE
> Fix For: 9.0.0-M9, 8.0.13
>
> Attachments: image-2022-09-07-13-50-40-452.png
>
>
> In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 to
> 9.0.64 and 8.5.50 to 8.5.81 the Form authentication example in the examples
> web application displayed user provided data without filtering, exposing a
> XSS vulnerability.
> [https://nvd.nist.gov/vuln/detail/CVE-2022-34305]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (TOMEE-4001) CVE-2022-34305 displaying user provided data without filtering, exposing a XSS vulnerability
[ https://issues.apache.org/jira/browse/TOMEE-4001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-4001: --- Attachment: image-2022-09-07-13-50-40-452.png > CVE-2022-34305 displaying user provided data without filtering, exposing a > XSS vulnerability > > > Key: TOMEE-4001 > URL: https://issues.apache.org/jira/browse/TOMEE-4001 > Project: TomEE > Issue Type: Dependency upgrade > Components: TomEE Core Server >Affects Versions: 9.0.0-M8, 8.0.12 >Reporter: Yugandher reddy vonteddu >Assignee: Richard Zowalla >Priority: Major > Labels: CVE > Fix For: 9.0.0-M9, 8.0.13 > > Attachments: image-2022-09-07-13-50-40-452.png > > > In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 to > 9.0.64 and 8.5.50 to 8.5.81 the Form authentication example in the examples > web application displayed user provided data without filtering, exposing a > XSS vulnerability. > [https://nvd.nist.gov/vuln/detail/CVE-2022-34305] > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
[
https://issues.apache.org/jira/browse/TOMEE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez resolved TOMEE-3979.
Fix Version/s: 9.0.0-M8
Resolution: Fixed
> service.bat issue when using JRE_HOME on Windows
> -
>
> Key: TOMEE-3979
> URL: https://issues.apache.org/jira/browse/TOMEE-3979
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 9.0.0-M7, 8.0.11, 8.0.12
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M8, 8.0.13
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Pre requisites to reproduce this issue:
> # Windows environment
> # set JRE_HOME instead of JAVA_HOME
> Example:
>
> {code:java}
> >set JRE_HOME=C:\java\jre-8
> >service.bat install tomee_service
> Installing the service 'tomee_service' ...
> Using CATALINA_HOME:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using CATALINA_BASE:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using JAVA_HOME: ""
> Using JRE_HOME: "C:\java\jre-8"
> Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
> Using Service User: ""
> Installed, will now configure TomEE
> 11 was unexpected at this time. {code}
>
> As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
> The origin of the issue happens in this validation:
> [https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
> because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
> (independently if it's Java 8, 11
> etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Commented] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
[
https://issues.apache.org/jira/browse/TOMEE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17554188#comment-17554188
]
Cesar Hernandez commented on TOMEE-3979:
PRs available:
[https://github.com/apache/tomee/pull/886]
[https://github.com/apache/tomee/pull/887]
> service.bat issue when using JRE_HOME on Windows
> -
>
> Key: TOMEE-3979
> URL: https://issues.apache.org/jira/browse/TOMEE-3979
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 9.0.0-M7, 8.0.11, 8.0.12
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.13
>
>
> Pre requisites to reproduce this issue:
> # Windows environment
> # set JRE_HOME instead of JAVA_HOME
> Example:
>
> {code:java}
> >set JRE_HOME=C:\java\jre-8
> >service.bat install tomee_service
> Installing the service 'tomee_service' ...
> Using CATALINA_HOME:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using CATALINA_BASE:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using JAVA_HOME: ""
> Using JRE_HOME: "C:\java\jre-8"
> Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
> Using Service User: ""
> Installed, will now configure TomEE
> 11 was unexpected at this time. {code}
>
> As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
> The origin of the issue happens in this validation:
> [https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
> because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
> (independently if it's Java 8, 11
> etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
[
https://issues.apache.org/jira/browse/TOMEE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3979:
---
Affects Version/s: 8.0.12
> service.bat issue when using JRE_HOME on Windows
> -
>
> Key: TOMEE-3979
> URL: https://issues.apache.org/jira/browse/TOMEE-3979
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 9.0.0-M7, 8.0.11, 8.0.12
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.13
>
>
> Pre requisites to reproduce this issue:
> # Windows environment
> # set JRE_HOME instead of JAVA_HOME
> Example:
>
> {code:java}
> >set JRE_HOME=C:\java\jre-8
> >service.bat install tomee_service
> Installing the service 'tomee_service' ...
> Using CATALINA_HOME:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using CATALINA_BASE:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using JAVA_HOME: ""
> Using JRE_HOME: "C:\java\jre-8"
> Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
> Using Service User: ""
> Installed, will now configure TomEE
> 11 was unexpected at this time. {code}
>
> As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
> The origin of the issue happens in this validation:
> [https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
> because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
> (independently if it's Java 8, 11
> etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Updated] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
[
https://issues.apache.org/jira/browse/TOMEE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3979:
---
Affects Version/s: 9.0.0-M7
> service.bat issue when using JRE_HOME on Windows
> -
>
> Key: TOMEE-3979
> URL: https://issues.apache.org/jira/browse/TOMEE-3979
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 9.0.0-M7, 8.0.11
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.13
>
>
> Pre requisites to reproduce this issue:
> # Windows environment
> # set JRE_HOME instead of JAVA_HOME
> Example:
>
> {code:java}
> >set JRE_HOME=C:\java\jre-8
> >service.bat install tomee_service
> Installing the service 'tomee_service' ...
> Using CATALINA_HOME:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using CATALINA_BASE:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using JAVA_HOME: ""
> Using JRE_HOME: "C:\java\jre-8"
> Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
> Using Service User: ""
> Installed, will now configure TomEE
> 11 was unexpected at this time. {code}
>
> As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
> The origin of the issue happens in this validation:
> [https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
> because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
> (independently if it's Java 8, 11
> etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Assigned] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
[
https://issues.apache.org/jira/browse/TOMEE-3979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez reassigned TOMEE-3979:
--
Assignee: Cesar Hernandez
> service.bat issue when using JRE_HOME on Windows
> -
>
> Key: TOMEE-3979
> URL: https://issues.apache.org/jira/browse/TOMEE-3979
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 8.0.11
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.13
>
>
> Pre requisites to reproduce this issue:
> # Windows environment
> # set JRE_HOME instead of JAVA_HOME
> Example:
>
> {code:java}
> >set JRE_HOME=C:\java\jre-8
> >service.bat install tomee_service
> Installing the service 'tomee_service' ...
> Using CATALINA_HOME:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using CATALINA_BASE:
> "C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
> Using JAVA_HOME: ""
> Using JRE_HOME: "C:\java\jre-8"
> Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
> Using Service User: ""
> Installed, will now configure TomEE
> 11 was unexpected at this time. {code}
>
> As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
> The origin of the issue happens in this validation:
> [https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
> because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
> (independently if it's Java 8, 11
> etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (TOMEE-3979) service.bat issue when using JRE_HOME on Windows
Cesar Hernandez created TOMEE-3979:
--
Summary: service.bat issue when using JRE_HOME on Windows
Key: TOMEE-3979
URL: https://issues.apache.org/jira/browse/TOMEE-3979
Project: TomEE
Issue Type: Bug
Affects Versions: 8.0.11
Reporter: Cesar Hernandez
Fix For: 8.0.13
Pre requisites to reproduce this issue:
# Windows environment
# set JRE_HOME instead of JAVA_HOME
Example:
{code:java}
>set JRE_HOME=C:\java\jre-8
>service.bat install tomee_service
Installing the service 'tomee_service' ...
Using CATALINA_HOME:
"C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
Using CATALINA_BASE:
"C:\Users\Administrator\Documents\apache-tomee-8.0.11-plus\apache-tomee-plus-8.0.11"
Using JAVA_HOME: ""
Using JRE_HOME: "C:\java\jre-8"
Using JVM: "C:\java\jre-8\bin\server\jvm.dll"
Using Service User: ""
Installed, will now configure TomEE
11 was unexpected at this time. {code}
As part of the work done in https://issues.apache.org/jira/browse/TOMEE-2261,
The origin of the issue happens in this validation:
[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L242-L248]
because `JAVA_MAJOR_VERSION` is note defined when JRE_HOME is used
(independently if it's Java 8, 11
etc.):[https://github.com/apache/tomee/blob/45b1ba51ebfc31691bbf517d9d3d00c7fe86e48f/tomee/apache-tomee/src/main/resources/service.bat#L88-L90]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-3932. Resolution: Done > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > Time Spent: 40m > Remaining Estimate: 0h > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (TOMEE-3931) fix example/cucumber-jvm
[
https://issues.apache.org/jira/browse/TOMEE-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez resolved TOMEE-3931.
Resolution: Fixed
> fix example/cucumber-jvm
> -
>
> Key: TOMEE-3931
> URL: https://issues.apache.org/jira/browse/TOMEE-3931
> Project: TomEE
> Issue Type: Sub-task
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M8
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current Master CI shows this test if failing. I was able to reproduce the
> issue locally too:
> {code:java}
> T E S T S
> ---
> Running org.superbiz.cucumber.CucumberTest
> 0 Scenarios
> 0 Steps
> 0m0.149s
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<<
> FAILURE!
> Feature: Hello Time elapsed: 0.406 sec <<< ERROR!
> java.lang.NoClassDefFoundError: javax/ejb/embeddable/EJBContainer
> at
> cucumber.runtime.java.openejb.OpenEJBObjectFactory.start(OpenEJBObjectFactory.java:32)
> at cucumber.runtime.java.JavaBackend.buildWorld(JavaBackend.java:115)
> at cucumber.runner.Runner.buildBackendWorlds(Runner.java:120)
> at cucumber.runner.Runner.runPickle(Runner.java:38)
> at
> cucumber.runtime.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:146)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.ClassNotFoundException: javax.ejb.embeddable.EJBContainer
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
> ... 37 more
> Results :
> Tests in error:
> Feature: Hello: javax/ejb/embeddable/EJBContainer
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [ERROR] There are test failures.
> Please refer to
> /home/jenkins/jenkins-agent/workspace/Tomee/master-build-full/examples/cucumber-jvm/target/surefire-reports
> for the individual test results.
> [JENKINS] Recording test results {code}
--
[jira] [Updated] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3932: --- Fix Version/s: 9.0.0-M8 > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-3932: -- Assignee: Cesar Hernandez > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17531012#comment-17531012 ] Cesar Hernandez commented on TOMEE-3932: First version of the page is in this PR available for review: https://github.com/apache/tomee/pull/878 > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Reporter: Cesar Hernandez >Priority: Major > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3932: --- Affects Version/s: 9.0.0-M7 > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (TOMEE-3932) Migration tips and tricks
[ https://issues.apache.org/jira/browse/TOMEE-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3932: --- Description: During the namespace migration, there are common patterns, tips and tricks that can be documented to allow more contributors to help on the migration. > Migration tips and tricks > - > > Key: TOMEE-3932 > URL: https://issues.apache.org/jira/browse/TOMEE-3932 > Project: TomEE > Issue Type: Sub-task >Reporter: Cesar Hernandez >Priority: Major > > During the namespace migration, there are common patterns, tips and tricks > that can be documented to allow more contributors to help on the migration. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (TOMEE-3932) Migration tips and tricks
Cesar Hernandez created TOMEE-3932: -- Summary: Migration tips and tricks Key: TOMEE-3932 URL: https://issues.apache.org/jira/browse/TOMEE-3932 Project: TomEE Issue Type: Sub-task Reporter: Cesar Hernandez -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez resolved TOMEE-3927.
Resolution: Fixed
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM
[jira] [Commented] (TOMEE-3931) fix example/cucumber-jvm
[
https://issues.apache.org/jira/browse/TOMEE-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17529742#comment-17529742
]
Cesar Hernandez commented on TOMEE-3931:
PR is available for review: https://github.com/apache/tomee/pull/875
The issue was that io.cucumber:cucumber-openejb:7.3.2 still uses
javax.ejb.embeddable.EJBContainer in OpenEJBObjectFactory.java
Since currently there is no new version compatible with jakarta.ejb [1], I
added a module deps/cucumber-openejb-shade to fix the example and provide the
context in the cucumber-openejb/pom.xml to let people know why we are using a
shade version.
[1] https://github.com/cucumber/cucumber-jvm/issues/2450
> fix example/cucumber-jvm
> -
>
> Key: TOMEE-3931
> URL: https://issues.apache.org/jira/browse/TOMEE-3931
> Project: TomEE
> Issue Type: Sub-task
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M8
>
>
> Current Master CI shows this test if failing. I was able to reproduce the
> issue locally too:
> {code:java}
> T E S T S
> ---
> Running org.superbiz.cucumber.CucumberTest
> 0 Scenarios
> 0 Steps
> 0m0.149s
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<<
> FAILURE!
> Feature: Hello Time elapsed: 0.406 sec <<< ERROR!
> java.lang.NoClassDefFoundError: javax/ejb/embeddable/EJBContainer
> at
> cucumber.runtime.java.openejb.OpenEJBObjectFactory.start(OpenEJBObjectFactory.java:32)
> at cucumber.runtime.java.JavaBackend.buildWorld(JavaBackend.java:115)
> at cucumber.runner.Runner.buildBackendWorlds(Runner.java:120)
> at cucumber.runner.Runner.runPickle(Runner.java:38)
> at
> cucumber.runtime.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:146)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
> at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
> at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
> at
> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
> at
> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
> Caused by: java.lang.ClassNotFoundException: javax.ejb.embeddable.EJBContainer
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
>
[jira] [Updated] (TOMEE-3931) fix example/cucumber-jvm
[
https://issues.apache.org/jira/browse/TOMEE-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3931:
---
Description:
Current Master CI shows this test if failing. I was able to reproduce the issue
locally too:
{code:java}
T E S T S
---
Running org.superbiz.cucumber.CucumberTest
0 Scenarios
0 Steps
0m0.149s
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.411 sec <<<
FAILURE!
Feature: Hello Time elapsed: 0.406 sec <<< ERROR!
java.lang.NoClassDefFoundError: javax/ejb/embeddable/EJBContainer
at
cucumber.runtime.java.openejb.OpenEJBObjectFactory.start(OpenEJBObjectFactory.java:32)
at cucumber.runtime.java.JavaBackend.buildWorld(JavaBackend.java:115)
at cucumber.runner.Runner.buildBackendWorlds(Runner.java:120)
at cucumber.runner.Runner.runPickle(Runner.java:38)
at
cucumber.runtime.junit.PickleRunners$NoStepDescriptions.run(PickleRunners.java:146)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:68)
at cucumber.runtime.junit.FeatureRunner.runChild(FeatureRunner.java:23)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at cucumber.runtime.junit.FeatureRunner.run(FeatureRunner.java:73)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:122)
at cucumber.api.junit.Cucumber.runChild(Cucumber.java:64)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at cucumber.api.junit.Cucumber$1.evaluate(Cucumber.java:131)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75)
Caused by: java.lang.ClassNotFoundException: javax.ejb.embeddable.EJBContainer
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 37 more
Results :
Tests in error:
Feature: Hello: javax/ejb/embeddable/EJBContainer
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
[ERROR] There are test failures.
Please refer to
/home/jenkins/jenkins-agent/workspace/Tomee/master-build-full/examples/cucumber-jvm/target/surefire-reports
for the individual test results.
[JENKINS] Recording test results {code}
> fix example/cucumber-jvm
> -
>
> Key: TOMEE-3931
> URL: https://issues.apache.org/jira/browse/TOMEE-3931
> Project: TomEE
> Issue Type: Sub-task
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M8
>
>
> Current Master CI shows this test if failing. I was able to reproduce the
> issue locally too:
> {code:java}
> T E S T S
>
[jira] [Closed] (TOMEE-3930) fix arquillian-tomee-moviefun-example
[ https://issues.apache.org/jira/browse/TOMEE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez closed TOMEE-3930. -- Resolution: Fixed > fix arquillian-tomee-moviefun-example > - > > Key: TOMEE-3930 > URL: https://issues.apache.org/jira/browse/TOMEE-3930 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (TOMEE-3931) fix example/cucumber-jvm
Cesar Hernandez created TOMEE-3931: -- Summary: fix example/cucumber-jvm Key: TOMEE-3931 URL: https://issues.apache.org/jira/browse/TOMEE-3931 Project: TomEE Issue Type: Sub-task Affects Versions: 9.0.0-M7 Reporter: Cesar Hernandez Assignee: Cesar Hernandez Fix For: 9.0.0-M8 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (TOMEE-3930) fix arquillian-tomee-moviefun-example
[ https://issues.apache.org/jira/browse/TOMEE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17528498#comment-17528498 ] Cesar Hernandez commented on TOMEE-3930: PR available: [https://github.com/apache/tomee/pull/872] > fix arquillian-tomee-moviefun-example > - > > Key: TOMEE-3930 > URL: https://issues.apache.org/jira/browse/TOMEE-3930 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (TOMEE-3930) fix arquillian-tomee-moviefun-example
[ https://issues.apache.org/jira/browse/TOMEE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3930: --- Fix Version/s: 9.0.0-M8 > fix arquillian-tomee-moviefun-example > - > > Key: TOMEE-3930 > URL: https://issues.apache.org/jira/browse/TOMEE-3930 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (TOMEE-3930) fix arquillian-tomee-moviefun-example
[ https://issues.apache.org/jira/browse/TOMEE-3930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3930: --- Affects Version/s: 9.0.0-M7 > fix arquillian-tomee-moviefun-example > - > > Key: TOMEE-3930 > URL: https://issues.apache.org/jira/browse/TOMEE-3930 > Project: TomEE > Issue Type: Sub-task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (TOMEE-3930) fix arquillian-tomee-moviefun-example
Cesar Hernandez created TOMEE-3930: -- Summary: fix arquillian-tomee-moviefun-example Key: TOMEE-3930 URL: https://issues.apache.org/jira/browse/TOMEE-3930 Project: TomEE Issue Type: Sub-task Reporter: Cesar Hernandez Assignee: Cesar Hernandez -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (TOMEE-2770) ActiveMQ dynamic producer not destroyed
[ https://issues.apache.org/jira/browse/TOMEE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-2770. Resolution: Fixed > ActiveMQ dynamic producer not destroyed > --- > > Key: TOMEE-2770 > URL: https://issues.apache.org/jira/browse/TOMEE-2770 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 8.0.0-Final, 8.0.1 >Reporter: François Courtault >Priority: Blocker > Fix For: 8.0.5 > > > Hello, > In an stateless EJB, I inject JMSContext (working) and in a method, I have > the following code: > *jmsContext*.createProducer().send(*messageQueue*, > *jmsContext*.createTextMessage(*"Test"*)); > The issue I have is that each time I send a text message a DynamicProducer is > created which could be the root cause of a memory leak. > I don’t get that because, according to the JMS 2.0 specification, the > JMSContext injected has a Transaction scope => this mean that after the end > of the method, the JMSContext should be closed so that the dynamic producer: > this is not I am seing :( > > Best Regards. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (TOMEE-2770) ActiveMQ dynamic producer not destroyed
[ https://issues.apache.org/jira/browse/TOMEE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-2770: --- Fix Version/s: 8.0.5 > ActiveMQ dynamic producer not destroyed > --- > > Key: TOMEE-2770 > URL: https://issues.apache.org/jira/browse/TOMEE-2770 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 8.0.0-Final, 8.0.1 >Reporter: François Courtault >Priority: Blocker > Fix For: 8.0.5 > > > Hello, > In an stateless EJB, I inject JMSContext (working) and in a method, I have > the following code: > *jmsContext*.createProducer().send(*messageQueue*, > *jmsContext*.createTextMessage(*"Test"*)); > The issue I have is that each time I send a text message a DynamicProducer is > created which could be the root cause of a memory leak. > I don’t get that because, according to the JMS 2.0 specification, the > JMSContext injected has a Transaction scope => this mean that after the end > of the method, the JMSContext should be closed so that the dynamic producer: > this is not I am seing :( > > Best Regards. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (TOMEE-2770) ActiveMQ dynamic producer not destroyed
[ https://issues.apache.org/jira/browse/TOMEE-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527846#comment-17527846 ] Cesar Hernandez commented on TOMEE-2770: I see this solved since tomee-8.0.2 via: [https://github.com/apache/tomee/commit/cedcf5714344969ba86149cc8501c240e2232f05] > ActiveMQ dynamic producer not destroyed > --- > > Key: TOMEE-2770 > URL: https://issues.apache.org/jira/browse/TOMEE-2770 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 8.0.0-Final, 8.0.1 >Reporter: François Courtault >Priority: Blocker > > Hello, > In an stateless EJB, I inject JMSContext (working) and in a method, I have > the following code: > *jmsContext*.createProducer().send(*messageQueue*, > *jmsContext*.createTextMessage(*"Test"*)); > The issue I have is that each time I send a text message a DynamicProducer is > created which could be the root cause of a memory leak. > I don’t get that because, according to the JMS 2.0 specification, the > JMSContext injected has a Transaction scope => this mean that after the end > of the method, the JMSContext should be closed so that the dynamic producer: > this is not I am seing :( > > Best Regards. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Work stopped] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TOMEE-3927 stopped by Cesar Hernandez.
--
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default
[jira] [Commented] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527793#comment-17527793
]
Cesar Hernandez commented on TOMEE-3927:
In a local environment, the test fails 1 out of 5 times when the machine is
under load.
I initially tried to add more configuration via properties:
{code:java}
.p("mdbs.InstanceLimit", "30")
.p("mdbs.activation.maxSessions", "50") {code}
But still had random failures (1 out of 10 approx).
After looking on how the rest of the test were developed, with the following PR
I manage to get a stable success of the test. Looking forward to see how the
test behaves in CI environment:
https://github.com/apache/tomee/pull/871
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM
[jira] [Work started] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TOMEE-3927 started by Cesar Hernandez.
--
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default
[jira] [Updated] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3927:
---
Fix Version/s: 9.0.0-M9
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default
[jira] [Updated] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3927:
---
Affects Version/s: 9.0.0-M8
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Transaction Manager,
>
[jira] [Updated] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3927:
---
Affects Version/s: 9.0.0-M7
(was: 9.0.0-M8)
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Affects Versions: 9.0.0-M7
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 9.0.0-M9
>
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM
[jira] [Assigned] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
[
https://issues.apache.org/jira/browse/TOMEE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez reassigned TOMEE-3927:
--
Assignee: Cesar Hernandez
> Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
>
>
> Key: TOMEE-3927
> URL: https://issues.apache.org/jira/browse/TOMEE-3927
> Project: TomEE
> Issue Type: Test
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
>
> The test
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has
> random failures both locally and in CI.
>
> {code:java}
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.junit.Assert.fail(Assert.java:89)
> at org.junit.Assert.failNotEquals(Assert.java:835)
> at org.junit.Assert.assertEquals(Assert.java:647)
> at org.junit.Assert.assertEquals(Assert.java:633)
> at
> org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
> at
> org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
> at
> org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
> at
> org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
> at
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
> at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
> at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
> at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
> Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync
> run
> INFO: Created new singletonService
> org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Succeeded in installing singleton service
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
> create one for the beans deployed.
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Security Service, type=SecurityService,
> provider-id=Default Security Service)
> Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
> INFO: Configuring Service(id=Default Transaction Manager,
> type=TransactionManager,
[jira] [Created] (TOMEE-3927) Fix random failure for: JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
Cesar Hernandez created TOMEE-3927:
--
Summary: Fix random failure for:
JMS2AMQTest#sendToMdbWithTxAndCheckLeaks
Key: TOMEE-3927
URL: https://issues.apache.org/jira/browse/TOMEE-3927
Project: TomEE
Issue Type: Test
Reporter: Cesar Hernandez
The test
org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks has random
failures both locally and in CI.
{code:java}
java.lang.AssertionError: expected:<0> but was:<1>
at org.junit.Assert.fail(Assert.java:89)
at org.junit.Assert.failNotEquals(Assert.java:835)
at org.junit.Assert.assertEquals(Assert.java:647)
at org.junit.Assert.assertEquals(Assert.java:633)
at
org.apache.openejb.activemq.JMS2AMQTest.sendToMdbWithTxAndCheckLeaks(JMS2AMQTest.java:309)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
at
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:44)
at
org.apache.openejb.junit.DeployApplication$1.call(DeployApplication.java:40)
at
org.apache.openejb.testing.ApplicationComposers.evaluate(ApplicationComposers.java:1075)
at
org.apache.openejb.junit.DeployApplication.evaluate(DeployApplication.java:40)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:364)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:237)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:158)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:428)
at
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
at
org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:562)
at
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:548)
Standard ErrorApr 25, 2022 3:38:44 PM org.apache.openejb.util.LogStreamAsync run
INFO: Created new singletonService
org.apache.openejb.cdi.ThreadSingletonServiceImpl@22bac7bc
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Succeeded in installing singleton service
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Cannot find the configuration file [conf/openejb.xml]. Will attempt to
create one for the beans deployed.
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Configuring Service(id=Default Security Service, type=SecurityService,
provider-id=Default Security Service)
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Configuring Service(id=Default Transaction Manager,
type=TransactionManager, provider-id=Default Transaction Manager)
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Configuring Service(id=xaCf, type=Resource, provider-id=xaCf)
Apr 25, 2022 3:38:45 PM org.apache.openejb.util.LogStreamAsync run
INFO: Configuring Service(id=amq, type=Resource, provider-id=Default JMS
Resource Adapter)
Apr 25, 2022 3:38:45 PM
[jira] [Work started] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-3647 started by Cesar Hernandez. -- > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[jira] [Closed] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez closed TOMEE-3905. -- Resolution: Done Closing this ticket since PR was already reviewed and merged. Thanks! > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-3905: -- Assignee: Cesar Hernandez > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-3905 started by Cesar Hernandez. -- > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[
https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523821#comment-17523821
]
Cesar Hernandez commented on TOMEE-3905:
Thank you for the review and follow up [~rzo1] .
{quote}Question: Shall we close this issue and open a new one to track the
analysis / digging regarding the release plugin bug, so we keep it in our
memory ?
{quote}
Sure thing, I created: https://issues.apache.org/jira/browse/TOMEE-3916
{quote}Perhaps we should also "port" the non-version related changes to master
(new issue?) to prevent it there, too? wdyt?
{quote}
Yes, that's why I made a reference to the branch for the ticket name. Now that
my PR worked I created https://issues.apache.org/jira/browse/TOMEE-3915 to
track the port into master.
> Fix Post release pom versioning for tomee-8.x branch
>
>
> Key: TOMEE-3905
> URL: https://issues.apache.org/jira/browse/TOMEE-3905
> Project: TomEE
> Issue Type: Task
>Affects Versions: 8.0.10
>Reporter: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, there are a couple of examples that after each release their
> pom.xml version isn't updated.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-3905: -- Assignee: (was: Cesar Hernandez) > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3916) maven-release-plugin issue
Cesar Hernandez created TOMEE-3916: -- Summary: maven-release-plugin issue Key: TOMEE-3916 URL: https://issues.apache.org/jira/browse/TOMEE-3916 Project: TomEE Issue Type: Task Reporter: Cesar Hernandez As documented in https://issues.apache.org/jira/browse/TOMEE-3905 and https://issues.apache.org/jira/browse/TOMEE-3915 , there is a bug in maven release plugin that is the root cause of having to fix some TomEE examples pom version number after each release. Once https://issues.apache.org/jira/browse/MRELEASE-932 (and child tickets) gets solved in the plugin, we can go back to TomEE branches and use the tomee.version maven properties for Tomee dependencies management as part of an example project, in the meantime, using the full version for each dependency in examples pom.xml files is advisable to prevent post-release maven version cleanups in TomEE branches. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3915) Fix Post release pom versioning for Master branch
[ https://issues.apache.org/jira/browse/TOMEE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3915: --- Description: Currently, there are a couple of examples that after each release their pom.xml version isn't updated. There is a bug in the maven release plugin that is the root cause of having to fix some TomEE examples pom version number after each release: https://issues.apache.org/jira/browse/MRELEASE-932 was:Currently, there are a couple of examples that after each release their pom.xml version isn't updated. > Fix Post release pom versioning for Master branch > - > > Key: TOMEE-3915 > URL: https://issues.apache.org/jira/browse/TOMEE-3915 > Project: TomEE > Issue Type: Task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. > There is a bug in the maven release plugin that is the root cause of having > to fix some TomEE examples pom version number after each release: > https://issues.apache.org/jira/browse/MRELEASE-932 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3915) Fix Post release pom versioning for Master branch
[ https://issues.apache.org/jira/browse/TOMEE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3915: --- Affects Version/s: 9.0.0-M7 (was: 8.0.10) > Fix Post release pom versioning for Master branch > - > > Key: TOMEE-3915 > URL: https://issues.apache.org/jira/browse/TOMEE-3915 > Project: TomEE > Issue Type: Task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3915) Fix Post release pom versioning for Master branch
[ https://issues.apache.org/jira/browse/TOMEE-3915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3915: --- Fix Version/s: 9.0.0-M8 (was: 8.0.12) > Fix Post release pom versioning for Master branch > - > > Key: TOMEE-3915 > URL: https://issues.apache.org/jira/browse/TOMEE-3915 > Project: TomEE > Issue Type: Task >Affects Versions: 9.0.0-M7 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3915) Fix Post release pom versioning for Master branch
Cesar Hernandez created TOMEE-3915: -- Summary: Fix Post release pom versioning for Master branch Key: TOMEE-3915 URL: https://issues.apache.org/jira/browse/TOMEE-3915 Project: TomEE Issue Type: Task Affects Versions: 8.0.10 Reporter: Cesar Hernandez Assignee: Cesar Hernandez Fix For: 8.0.12 Currently, there are a couple of examples that after each release their pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522576#comment-17522576 ] Cesar Hernandez commented on TOMEE-3905: So far and according to Github actions for tomee-8.x branch, the overall build is back to green (excluding tests) [https://github.com/apache/tomee/actions/runs/2169982256 :)|https://github.com/apache/tomee/actions/runs/2169982256] > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3905: --- Affects Version/s: (was: 9.0.0-M7) > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522573#comment-17522573 ] Cesar Hernandez commented on TOMEE-3905: PR available for review: https://github.com/apache/tomee/pull/853 > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3905: --- Affects Version/s: 8.0.10 9.0.0-M7 > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Affects Versions: 9.0.0-M7, 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17522568#comment-17522568 ] Cesar Hernandez commented on TOMEE-3905: I discovered that there is a bug in maven release plugin that is the root cause of having to fix some TomEE examples pom version number after each release: https://issues.apache.org/jira/browse/MRELEASE-932 The PR I'm creating for TOMEE-3905 will prevent this issue for 8 examples, except for the following two that currently are out of the reactor since the issue is the example code itself: * examples/applet/ https://issues.apache.org/jira/browse/TOMEE-3906 * examples/mbean-auto-registration https://issues.apache.org/jira/browse/TOMEE-3907 > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3907) fix example mbean-auto-registration project
Cesar Hernandez created TOMEE-3907: -- Summary: fix example mbean-auto-registration project Key: TOMEE-3907 URL: https://issues.apache.org/jira/browse/TOMEE-3907 Project: TomEE Issue Type: Task Affects Versions: 8.0.10, 9.0.0-M7 Reporter: Cesar Hernandez The examples/mbean-auto-registrationproject is commented out of the examples/pom.xml because it needs fixes that currently prevent the examples/mbean-auto-registration project to build successfully if Java version is >= 9 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3906) example applet project needs fix
Cesar Hernandez created TOMEE-3906: -- Summary: example applet project needs fix Key: TOMEE-3906 URL: https://issues.apache.org/jira/browse/TOMEE-3906 Project: TomEE Issue Type: Task Affects Versions: 8.0.10, 9.0.0-M7 Reporter: Cesar Hernandez The examples/applet project is commented out of the examples/pom.xml because it needs fixes that currently prevent the examples/applet project to build successfully. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
[ https://issues.apache.org/jira/browse/TOMEE-3905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-3905: -- Assignee: Cesar Hernandez > Fix Post release pom versioning for tomee-8.x branch > > > Key: TOMEE-3905 > URL: https://issues.apache.org/jira/browse/TOMEE-3905 > Project: TomEE > Issue Type: Task >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.12 > > > Currently, there are a couple of examples that after each release their > pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3905) Fix Post release pom versioning for tomee-8.x branch
Cesar Hernandez created TOMEE-3905: -- Summary: Fix Post release pom versioning for tomee-8.x branch Key: TOMEE-3905 URL: https://issues.apache.org/jira/browse/TOMEE-3905 Project: TomEE Issue Type: Task Reporter: Cesar Hernandez Fix For: 8.0.12 Currently, there are a couple of examples that after each release their pom.xml version isn't updated. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3893) Upgrade to jackson 2.13.2.2
[ https://issues.apache.org/jira/browse/TOMEE-3893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17520815#comment-17520815 ] Cesar Hernandez commented on TOMEE-3893: [~rzo1] Thank you for the update on tomee-8.x branch!, I cherry picked your commit into current master. [https://github.com/apache/tomee/pull/850] > Upgrade to jackson 2.13.2.2 > --- > > Key: TOMEE-3893 > URL: https://issues.apache.org/jira/browse/TOMEE-3893 > Project: TomEE > Issue Type: Dependency upgrade > Components: TomEE Core Server >Affects Versions: 8.0.10 >Reporter: Richard Zowalla >Assignee: Richard Zowalla >Priority: Major > Labels: CVE > Fix For: 8.0.11 > > > https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.13 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3860) Upgrade jackson-databind for CVE-2020-36518
[ https://issues.apache.org/jira/browse/TOMEE-3860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17514873#comment-17514873 ] Cesar Hernandez commented on TOMEE-3860: Hi [~9177012889] , I'm not aware of a potential release date for 8.0.11. If not already, I'll suggest you subscribe to TomEE mailing list to follow up over release dates: [https://tomee.apache.org/mailing-lists.html] Have a nice day! > Upgrade jackson-databind for CVE-2020-36518 > --- > > Key: TOMEE-3860 > URL: https://issues.apache.org/jira/browse/TOMEE-3860 > Project: TomEE > Issue Type: Bug >Affects Versions: 8.0.10 >Reporter: Yugandher reddy vonteddu >Priority: Critical > Labels: CVE > Fix For: 8.0.11 > > > jackson-databind-2.13.0-rc2.jar is vulnerable and should be upgraded. > [https://nvd.nist.gov/vuln/detail/CVE-2020-36518] > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3883) Update example 'mvc-resteasy' to use Server/API Bom - master branch
[ https://issues.apache.org/jira/browse/TOMEE-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3883: --- Affects Version/s: 9.0.0-M7 (was: 8.0.6) > Update example 'mvc-resteasy' to use Server/API Bom - master branch > --- > > Key: TOMEE-3883 > URL: https://issues.apache.org/jira/browse/TOMEE-3883 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 9.0.0-M7 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.11 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3883) Update example 'mvc-resteasy' to use Server/API Bom - master branch
[ https://issues.apache.org/jira/browse/TOMEE-3883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3883: --- Fix Version/s: 9.0.0-M8 (was: 8.0.11) > Update example 'mvc-resteasy' to use Server/API Bom - master branch > --- > > Key: TOMEE-3883 > URL: https://issues.apache.org/jira/browse/TOMEE-3883 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 9.0.0-M7 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > Fix For: 9.0.0-M8 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (TOMEE-3883) Update example 'mvc-resteasy' to use Server/API Bom - master branch
Cesar Hernandez created TOMEE-3883: -- Summary: Update example 'mvc-resteasy' to use Server/API Bom - master branch Key: TOMEE-3883 URL: https://issues.apache.org/jira/browse/TOMEE-3883 Project: TomEE Issue Type: Sub-task Components: Examples and Documentation Affects Versions: 8.0.6 Reporter: Richard Zowalla Assignee: Cesar Hernandez Fix For: 8.0.11 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez updated TOMEE-3647: --- Fix Version/s: 8.0.11 > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.11 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17512801#comment-17512801 ] Cesar Hernandez commented on TOMEE-3647: Currently, this example is failing in the tomee-8.x because the arquillian resolver was still trying to resolve via maven HTTP instead of HTTPS. I fixed this example and also applied the migration to use Server/API Bom. PR available: https://github.com/apache/tomee/pull/830 > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.11 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work stopped] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-3647 stopped by Cesar Hernandez. -- > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Work started] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-3647 started by Cesar Hernandez. -- > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (TOMEE-3647) Update example 'mvc-resteasy' to use Server/API Bom
[ https://issues.apache.org/jira/browse/TOMEE-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez reassigned TOMEE-3647: -- Assignee: Cesar Hernandez > Update example 'mvc-resteasy' to use Server/API Bom > --- > > Key: TOMEE-3647 > URL: https://issues.apache.org/jira/browse/TOMEE-3647 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation >Affects Versions: 8.0.6 >Reporter: Richard Zowalla >Assignee: Cesar Hernandez >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (TOMEE-3856) Uprade to jackson 2.13.2
[ https://issues.apache.org/jira/browse/TOMEE-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cesar Hernandez resolved TOMEE-3856. Resolution: Done > Uprade to jackson 2.13.2 > > > Key: TOMEE-3856 > URL: https://issues.apache.org/jira/browse/TOMEE-3856 > Project: TomEE > Issue Type: Dependency upgrade >Affects Versions: 8.0.10 >Reporter: Cesar Hernandez >Assignee: Cesar Hernandez >Priority: Major > Fix For: 8.0.11 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3814:
---
Fix Version/s: 8.0.11
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Fix For: 8.0.11
>
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez resolved TOMEE-3814.
Resolution: Done
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Work started] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on TOMEE-3814 started by Cesar Hernandez.
--
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (TOMEE-3856) Uprade to jackson 2.13.2
Cesar Hernandez created TOMEE-3856: -- Summary: Uprade to jackson 2.13.2 Key: TOMEE-3856 URL: https://issues.apache.org/jira/browse/TOMEE-3856 Project: TomEE Issue Type: Dependency upgrade Affects Versions: 8.0.10 Reporter: Cesar Hernandez Assignee: Cesar Hernandez Fix For: 8.0.11 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493462#comment-17493462
]
Cesar Hernandez edited comment on TOMEE-3814 at 2/16/22, 7:38 PM:
--
I closed [https://github.com/apache/tomee/pull/815] since the root cause of the
error in the commented configuration is fixed here:
[https://github.com/apache/tomee/pull/816]
The attached screenshot shows the end result server.xml get from PR 816 once
the boom generation takes place
Screen Shot 2022-02-16 at 13.27.14
was (Author: cesarhernandezgt):
I closed [https://github.com/apache/tomee/pull/815] since the root cause of the
error in the commented configuration is fixed here:
[https://github.com/apache/tomee/pull/816]
The attached screenshot shows the end result server.xml get from PR 816 once
the boom generation takes place
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493462#comment-17493462
]
Cesar Hernandez commented on TOMEE-3814:
I closed [https://github.com/apache/tomee/pull/815] since the root cause of the
error in the commented configuration is fixed here:
[https://github.com/apache/tomee/pull/816]
The attached screenshot shows the end result server.xml get from PR 816 once
the boom generation takes place
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml
[
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Hernandez updated TOMEE-3814:
---
Attachment: Screen Shot 2022-02-16 at 13.27.14.png
> Commented SSL Connector fix for tomee server.xml
> -
>
> Key: TOMEE-3814
> URL: https://issues.apache.org/jira/browse/TOMEE-3814
> Project: TomEE
> Issue Type: Documentation
>Affects Versions: 8.0.8
>Reporter: Cesar Hernandez
>Assignee: Cesar Hernandez
>Priority: Major
> Attachments: Screen Shot 2022-02-16 at 13.27.14.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Current server.xml contains the following commented out SSL connector:
>
> {code:java}
>
> {code}
>
>
> The configuration for
> {code:java}
> xpoweredBy="false" server="Apache TomEE{code}
> is misleading since for this to work needs to be set in the "Connector" tag:
>
>
> {code:java}
>
> {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
