[jira] [Commented] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Richard Zowalla (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493736#comment-17493736
 ] 

Richard Zowalla commented on TOMEE-3843:


Thanks for reporting [~rene_b] 

Will be fixed in the next tomee 9 release.

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 9.0.0, 9.0.0-M8
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (TOMEE-3842) GitHub Actions fails for PullRequest Builds due to BOM auto generation

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-3842.

Fix Version/s: 9.0.0-M8
   8.0.11
   Resolution: Fixed

> GitHub Actions fails for PullRequest Builds due to BOM auto generation
> --
>
> Key: TOMEE-3842
> URL: https://issues.apache.org/jira/browse/TOMEE-3842
> Project: TomEE
>  Issue Type: Improvement
>  Components: TomEE Build
>Reporter: Richard Zowalla
>Assignee: Richard Zowalla
>Priority: Major
> Fix For: 9.0.0-M8, 8.0.11
>
>
> Current BOM auto generation via GitHub actions is also triggered for PR 
> Builds. However, creating a PR for a PR does not work and the workflow fails.
> Solution would be to separate between PR and Push triggered actions. The 
> latter should do the PR creation after BOM generation. The first case does 
> not need it.
> We can fix it by applying a similar approach as Apache Camel..
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-3843.

Resolution: Fixed

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 9.0.0, 9.0.0-M8
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla updated TOMEE-3843:
---
Fix Version/s: 9.0.0-M8

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 9.0.0, 9.0.0-M8
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla updated TOMEE-3843:
---
Fix Version/s: 9.0.0

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 9.0.0
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[tomee] branch tomee-9.x-initial updated (b26e9e6 -> 5f61e95)

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a change to branch tomee-9.x-initial
in repository https://gitbox.apache.org/repos/asf/tomee.git.


from b26e9e6  Move some more APIs, packages and relocate SXC
 add 81a357a  Test TomEE version replacement
 add 3a8603c  Merge branch 'master' of github.com:jgallimore/tomee
 add 813aebe  Merge remote-tracking branch 'apache/master'
 add a2360a8  TOMEE-3839 update to ActiveMQ 5.16.4
 add 71bb193  Minor: Regenerated BOMs for 
a2360a80193693dc63bf4b1973f0e4f9512023ba
 add 18f174b  TOMEE-3840 - Fix TomEE does not start with security enabled
 add d2873e0  TOMEE-3841 - Upgrades slf4j
 add 4cb9f8b  Revert "TOMEE-3840 - Fix TomEE does not start with security 
enabled"
 add 4b009f1  TOMEE-3840 - Adds TomEE specific policies to catalina.policy 
config file to allow startup with enabled security
 add 30a937b  TOMEE-3842 - Separates GitHub actions in (a) push (b) pull 
requests configurations to allow for PRs targeting master created via automatic 
BOM generation
 add 5f61e95  Merge remote-tracking branch 'origin/master' into 
tomee-9.x-initial

No new revisions were added by this update.

Summary of changes:
 .../{main.yml => main-pull-request-build.yml}  | 29 ++---
 .../workflows/{main.yml => main-push-build.yml}|  3 --
 boms/tomee-microprofile/pom.xml|  4 +--
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 boms/tomee-plume/pom.xml   | 16 -
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 boms/tomee-plus/pom.xml| 16 -
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 boms/tomee-webprofile/pom.xml  |  4 +--
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 pom.xml|  4 +--
 .../java/org/apache/tomee/installer/Installer.java | 38 ++
 .../java/org/apache/tomee/installer/Paths.java |  9 +
 .../org/apache/tomee/installer/PathsInterface.java |  2 ++
 14 files changed, 93 insertions(+), 52 deletions(-)
 copy .github/workflows/{main.yml => main-pull-request-build.yml} (59%)
 rename .github/workflows/{main.yml => main-push-build.yml} (98%)

[jira] [Work logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3814?focusedWorklogId=728745=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728745
 ]

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 17/Feb/22 07:48
Start Date: 17/Feb/22 07:48
Worklog Time Spent: 10m 
  Work Description: rzo1 edited a comment on pull request #816:
URL: https://github.com/apache/tomee/pull/816#issuecomment-1042134139


   @cesarhernandezgt lgtm. 
   
   ~~GitHub actions are failing due to TOMEE-3842. I will provide a related fix 
for it soon.~~
   
   I pushed a fix for TOMEE-3842 - so GitHub actions should work fine now.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 728745)
Time Spent: 40m  (was: 0.5h)

> 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: 40m
>  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)

[tomee] 02/03: TOMEE-3840 - Adds TomEE specific policies to catalina.policy config file to allow startup with enabled security

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git

commit 4b009f18bd2adb61053ee55d2411ba1b84e089b1
Author: Richard Zowalla 
AuthorDate: Thu Feb 17 08:43:31 2022 +0100

TOMEE-3840 - Adds TomEE specific policies to catalina.policy config file to 
allow startup with enabled security

Reverted the previous fix for TOMEE-3840 in favour of this Installer-based 
approach, so we do not need to update a sole config file in TomEE for every 
Tomcat update.
---
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 .../src/main/resources/tomee/conf/catalina.policy  |  5 +++
 .../java/org/apache/tomee/installer/Installer.java | 38 ++
 .../java/org/apache/tomee/installer/Paths.java |  9 +
 .../org/apache/tomee/installer/PathsInterface.java |  2 ++
 7 files changed, 69 insertions(+)

diff --git 
a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..748ba1c 100644
--- a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,11 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..748ba1c 100644
--- a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,11 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..748ba1c 100644
--- a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,11 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git 
a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..748ba1c 100644
--- a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,11 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git 

[tomee] 03/03: TOMEE-3842 - Separates GitHub actions in (a) push (b) pull requests configurations to allow for PRs targeting master created via automatic BOM generation

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git

commit 30a937b3fbc1a4bd0c86962f71b0cefb2ca57b20
Author: Richard Zowalla 
AuthorDate: Thu Feb 17 08:46:49 2022 +0100

TOMEE-3842 - Separates GitHub actions in (a) push (b) pull requests 
configurations to allow for PRs targeting master created via automatic BOM 
generation
---
 .../{main.yml => main-pull-request-build.yml}  | 29 ++
 .../workflows/{main.yml => main-push-build.yml}|  3 ---
 2 files changed, 2 insertions(+), 30 deletions(-)

diff --git a/.github/workflows/main.yml 
b/.github/workflows/main-pull-request-build.yml
similarity index 59%
copy from .github/workflows/main.yml
copy to .github/workflows/main-pull-request-build.yml
index df019ab..7920f98 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main-pull-request-build.yml
@@ -1,9 +1,6 @@
-name: CI Master
+name: CI Pull Request Master
 
 on:
-  push:
-branches:
-  - master
   pull_request:
 branches:
   - master
@@ -33,26 +30,4 @@ jobs:
 - name: Compile with Sanity checks
   run: mvn help:system -U --show-version --fail-at-end clean install 
-DfailIfNoTests=false -DskipTests -Pstyle,rat
   env:
-MAVEN_OPTS: -Xmx2048m
-
-  # We have some LF vs CRLF files from the Tomcat ZIPs, so we need to 
convert them to avoid diffs in git
-- name: Convert Config Files in BOM Module from CRLF to LF
-  run: find ./boms -type f -exec sed -i -e 's/\r$//' {} \;
-
-- name: Create Pull Request after BOM Regeneration
-  uses: peter-evans/create-pull-request@v3
-  with:
-base: master
-token: ${{ secrets.GITHUB_TOKEN }}
-commit-message: "Minor: Regenerated BOMs for ${{ github.sha }}"
-committer: GitHub 
-author: ${{ github.actor }} <${{ github.actor 
}}@users.noreply.github.com>
-signoff: true
-branch: regenerate_boms_after_dep_upgrade
-delete-branch: true
-title: "Regenerated BOMs after dependency upgrades"
-body: |
-  Found some uncommited changes (from BOM regeneration) after running 
build on TomEE master
-labels: |
-  dependencies
-assignees: cesarhernandezgt,dblevins,jeanouii,jgallimore,rzo1
\ No newline at end of file
+MAVEN_OPTS: -Xmx2048m
\ No newline at end of file
diff --git a/.github/workflows/main.yml b/.github/workflows/main-push-build.yml
similarity index 98%
rename from .github/workflows/main.yml
rename to .github/workflows/main-push-build.yml
index df019ab..94f747a 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main-push-build.yml
@@ -4,9 +4,6 @@ on:
   push:
 branches:
   - master
-  pull_request:
-branches:
-  - master
   workflow_dispatch:
 
 jobs:

[tomee] branch master updated (d2873e0 -> 30a937b)

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git.


from d2873e0  TOMEE-3841 - Upgrades slf4j
 new 4cb9f8b  Revert "TOMEE-3840 - Fix TomEE does not start with security 
enabled"
 new 4b009f1  TOMEE-3840 - Adds TomEE specific policies to catalina.policy 
config file to allow startup with enabled security
 new 30a937b  TOMEE-3842 - Separates GitHub actions in (a) push (b) pull 
requests configurations to allow for PRs targeting master created via automatic 
BOM generation

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../{main.yml => main-pull-request-build.yml}  |  29 +--
 .../workflows/{main.yml => main-push-build.yml}|   3 -
 .../src/main/resources/tomee/conf/catalina.policy  |   1 +
 .../src/main/resources/tomee/conf/catalina.policy  |   1 +
 .../src/main/resources/tomee/conf/catalina.policy  |   1 +
 .../src/main/resources/tomee/conf/catalina.policy  |   1 +
 tomee/apache-tomee/pom.xml |   3 -
 .../src/main/assembly/tomee-microprofile.xml   |   8 -
 .../apache-tomee/src/main/assembly/tomee-plume.xml |   8 -
 .../apache-tomee/src/main/assembly/tomee-plus.xml  |   8 -
 .../src/main/assembly/tomee-webprofile.xml |   8 -
 .../src/main/resources/catalina.policy | 268 -
 .../java/org/apache/tomee/installer/Installer.java |  38 +++
 .../java/org/apache/tomee/installer/Paths.java |   9 +
 .../org/apache/tomee/installer/PathsInterface.java |   2 +
 15 files changed, 55 insertions(+), 333 deletions(-)
 copy .github/workflows/{main.yml => main-pull-request-build.yml} (59%)
 rename .github/workflows/{main.yml => main-push-build.yml} (98%)
 delete mode 100644 tomee/apache-tomee/src/main/resources/catalina.policy

[tomee] 01/03: Revert "TOMEE-3840 - Fix TomEE does not start with security enabled"

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git

commit 4cb9f8b90ad7728454e20a448dd739a372714620
Author: Richard Zowalla 
AuthorDate: Thu Feb 17 08:36:15 2022 +0100

Revert "TOMEE-3840 - Fix TomEE does not start with security enabled"

This reverts commit 18f174b6acb6873c41f7da73f8a1cd952be95e87.
---
 .../src/main/resources/tomee/conf/catalina.policy  |   4 -
 .../src/main/resources/tomee/conf/catalina.policy  |   4 -
 .../src/main/resources/tomee/conf/catalina.policy  |   4 -
 .../src/main/resources/tomee/conf/catalina.policy  |   4 -
 tomee/apache-tomee/pom.xml |   3 -
 .../src/main/assembly/tomee-microprofile.xml   |   8 -
 .../apache-tomee/src/main/assembly/tomee-plume.xml |   8 -
 .../apache-tomee/src/main/assembly/tomee-plus.xml  |   8 -
 .../src/main/assembly/tomee-webprofile.xml |   8 -
 .../src/main/resources/catalina.policy | 268 -
 10 files changed, 319 deletions(-)

diff --git 
a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
index 1a081a3..7aab95d 100644
--- a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,10 +94,6 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
-// TOMEE-3840
-permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
-permission java.lang.RuntimePermission "accessDeclaredMembers";
-
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
index 1a081a3..7aab95d 100644
--- a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
@@ -94,10 +94,6 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
-// TOMEE-3840
-permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
-permission java.lang.RuntimePermission "accessDeclaredMembers";
-
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
index 1a081a3..7aab95d 100644
--- a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
@@ -94,10 +94,6 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
-// TOMEE-3840
-permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
-permission java.lang.RuntimePermission "accessDeclaredMembers";
-
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git 
a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
index 1a081a3..7aab95d 100644
--- a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,10 +94,6 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
-// TOMEE-3840
-permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
-permission java.lang.RuntimePermission "accessDeclaredMembers";
-
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git 

[jira] [Commented] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Richard Zowalla (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493727#comment-17493727
 ] 

Richard Zowalla commented on TOMEE-3843:


TomEE 8.0.x and 9.0.x share the same code base due to byte code transformation 
to the jakarataee namespace. We are currently in the process of working on M8, 
which will be build from a "standalone" code base. As we are based upon the 
same code base, the related fix will be contained in the next 9.0.x release.

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493719#comment-17493719
 ] 

Rene Bangemann commented on TOMEE-3840:
---

TomEE 9.0.0-M7 is also affected from this topic.

See TOMEE-3843.

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rene Bangemann updated TOMEE-3843:
--
Fix Version/s: (was: 8.0.11)

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493718#comment-17493718
 ] 

Rene Bangemann commented on TOMEE-3843:
---

The following changes in catalina.policy are necessary to start TomEE 9.0.0-M7 
successfully with security enabled:

grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
    ...
{color:#00875a}    permission java.util.PropertyPermission 
"tomee.skip-tomcat-log", "read";{color}
{color:#00875a}    {color}{color:#00875a}permission java.lang.RuntimePermission 
"accessDeclaredMembers";{color}
};

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493716#comment-17493716
 ] 

Rene Bangemann commented on TOMEE-3843:
---

TomEE 9.0.0-M7 is also affected from TOMEE-3840.

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#de350b}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rene Bangemann updated TOMEE-3843:
--
Affects Version/s: 9.0.0-M7
   (was: 8.0.9)

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 9.0.0-M7
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rene Bangemann updated TOMEE-3843:
--
Description: 
Start TomEE via "catalina.sh start -security"

The start of TomEE fails with the following exception:

_NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 
--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
_va.util.concurrent=ALL-UNNAMED 
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
_Exception in thread "main" java.lang.ExceptionInInitializerError_
_Caused by: org.apache.juli.logging.LogConfigurationException: 
java.lang.reflect.InvocationTargetException_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
        _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
        _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
_Caused by: java.lang.reflect.InvocationTargetException_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
        _at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
        _at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
        _... 3 more_
{color:#de350b}_Caused by: java.security.AccessControlException: access denied 
("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
        _at 
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
        _at 
java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
        _at 
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
        _at 
java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
        _at java.base/java.lang.System.getProperty(System.java:816)_
        _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
        _... 8 more_

 

  was:
Start TomEE via "catalina.sh start -security"

The start of TomEE fails with the following exception:

_NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 
--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
_va.util.concurrent=ALL-UNNAMED 
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
_Exception in thread "main" java.lang.ExceptionInInitializerError_
_Caused by: org.apache.juli.logging.LogConfigurationException: 
java.lang.reflect.InvocationTargetException_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
        _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
        _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
_Caused by: java.lang.reflect.InvocationTargetException_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
        _at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
        _at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
        _... 3 more_
{color:#FF}_Caused by: java.security.AccessControlException: access denied 
("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
        _at 
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
        _at 
java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
        _at 
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
        _at 
java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
        _at java.base/java.lang.System.getProperty(System.java:816)_
        _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
        _... 8 more_

 


> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> 

[jira] [Updated] (TOMEE-3843) TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rene Bangemann updated TOMEE-3843:
--
Summary: TomEE WebProfile 9.0.0-M7 does not start with security enabled  
(was: CLONE - TomEE WebProfile 9.0.0-M7 does not start with security enabled)

> TomEE WebProfile 9.0.0-M7 does not start with security enabled
> --
>
> Key: TOMEE-3843
> URL: https://issues.apache.org/jira/browse/TOMEE-3843
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (TOMEE-3843) CLONE - TomEE WebProfile 9.0.0-M7 does not start with security enabled

[Rene Bangemann (Jira)]

Rene Bangemann created TOMEE-3843:
-

 Summary: CLONE - TomEE WebProfile 9.0.0-M7 does not start with 
security enabled
 Key: TOMEE-3843
 URL: https://issues.apache.org/jira/browse/TOMEE-3843
 Project: TomEE
  Issue Type: Bug
  Components: TomEE Core Server
Affects Versions: 8.0.9
 Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) 
x86_64 GNU/Linux
Reporter: Rene Bangemann
Assignee: Richard Zowalla
 Fix For: 8.0.11


Start TomEE via "catalina.sh start -security"

The start of TomEE fails with the following exception:

_NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 
--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
_va.util.concurrent=ALL-UNNAMED 
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
_Exception in thread "main" java.lang.ExceptionInInitializerError_
_Caused by: org.apache.juli.logging.LogConfigurationException: 
java.lang.reflect.InvocationTargetException_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
        _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
        _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
_Caused by: java.lang.reflect.InvocationTargetException_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
        _at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
        _at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
        _... 3 more_
{color:#FF}_Caused by: java.security.AccessControlException: access denied 
("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
        _at 
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
        _at 
java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
        _at 
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
        _at 
java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
        _at java.base/java.lang.System.getProperty(System.java:816)_
        _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
        _... 8 more_

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Jenkins build is back to normal : TomEE » jakarta-deploy » TomEE :: TomEE :: Plus Webapp #839

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » jakarta-deploy » TomEE :: TomEE :: MicroProfile Webapp #839

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » jakarta-deploy #839

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » jakarta-deploy » TomEE :: TomEE :: Plume Webapp #839

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » jakarta-deploy » TomEE :: TomEE :: WebProfile Webapp #839

[Apache Jenkins Server]

See 

Jenkins build is back to normal : TomEE » pull-request #192

[Apache Jenkins Server]

See 

[jira] [Work logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3814?focusedWorklogId=728497=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728497
 ]

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 16/Feb/22 20:16
Start Date: 16/Feb/22 20:16
Worklog Time Spent: 10m 
  Work Description: rzo1 commented on pull request #816:
URL: https://github.com/apache/tomee/pull/816#issuecomment-1042134139


   @cesarhernandezgt lgtm. 
   
   GitHub actions are failing due to TOMEE-3842. I will provide a related fix 
for it soon.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 728497)
Time Spent: 0.5h  (was: 20m)

> 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: 0.5h
>  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-3842) GitHub Actions fails for PullRequest Builds due to BOM auto generation

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-3842:
--

 Summary: GitHub Actions fails for PullRequest Builds due to BOM 
auto generation
 Key: TOMEE-3842
 URL: https://issues.apache.org/jira/browse/TOMEE-3842
 Project: TomEE
  Issue Type: Improvement
  Components: TomEE Build
Reporter: Richard Zowalla
Assignee: Richard Zowalla


Current BOM auto generation via GitHub actions is also triggered for PR Builds. 
However, creating a PR for a PR does not work and the workflow fails.

Solution would be to separate between PR and Push triggered actions. The latter 
should do the PR creation after BOM generation. The first case does not need it.

We can fix it by applying a similar approach as Apache Camel..

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[Cesar Hernandez (Jira)]

[ 
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

[Cesar Hernandez (Jira)]

[ 
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

[Cesar Hernandez (Jira)]

 [ 
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)

[jira] [Work logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3814?focusedWorklogId=728467=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728467
 ]

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 16/Feb/22 19:35
Start Date: 16/Feb/22 19:35
Worklog Time Spent: 10m 
  Work Description: cesarhernandezgt closed pull request #815:
URL: https://github.com/apache/tomee/pull/815


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 728467)
Remaining Estimate: 0h
Time Spent: 10m

> 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
>  Time Spent: 10m
>  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 logged] (TOMEE-3814) Commented SSL Connector fix for tomee server.xml

[ASF GitHub Bot (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3814?focusedWorklogId=728468=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728468
 ]

ASF GitHub Bot logged work on TOMEE-3814:
-

Author: ASF GitHub Bot
Created on: 16/Feb/22 19:35
Start Date: 16/Feb/22 19:35
Worklog Time Spent: 10m 
  Work Description: cesarhernandezgt commented on pull request #815:
URL: https://github.com/apache/tomee/pull/815#issuecomment-1042090656


   Thank you @rzo1  for the review. I discovered that this server.xml's are 
part of the boom generation. So I'll close this PR in favor of 
https://github.com/apache/tomee/pull/816 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@tomee.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
---

Worklog Id: (was: 728468)
Time Spent: 20m  (was: 10m)

> 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
>  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

[Cesar Hernandez (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493381#comment-17493381
 ] 

Cesar Hernandez commented on TOMEE-3814:


I opened the following PR with the proposed change: 

https://github.com/apache/tomee/pull/815

> 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
>
> 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)

Build failed in Jenkins: TomEE » master-build-quick-9.x #1

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 600.20 KB...]
[ERROR] 
:[69,58]
 cannot find symbol
[ERROR] symbol:   class Provider
[ERROR] location: class org.apache.openejb.client.JaxWsProviderWrapper
[ERROR] 
:[126,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[128,9]
 cannot find symbol
[ERROR] symbol:   class ServiceDelegate
[ERROR] location: class org.apache.openejb.client.JaxWsProviderWrapper
[ERROR] 
:[133,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[138,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[143,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[160,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[165,5]
 method does not override or implement a method from a supertype
[ERROR] 
:[179,9]
 method does not override or implement a method from a supertype
[ERROR] 
:[182,28]
 cannot find symbol
[ERROR] symbol:   class BindingProvider
[ERROR] location: class 
org.apache.openejb.client.JaxWsProviderWrapper.ServiceDelegateWrapper
[ERROR] 
:[186,9]
 method does not override or implement a method from a supertype
[ERROR] 
:[191,62]
 cannot find symbol
[ERROR] symbol:   class WebService
[ERROR] location: class 
org.apache.openejb.client.JaxWsProviderWrapper.ServiceDelegateWrapper
[ERROR] 
:[192,23]
 cannot find symbol
[ERROR] symbol:   class WebService
[ERROR] location: class 
org.apache.openejb.client.JaxWsProviderWrapper.ServiceDelegateWrapper
[ERROR] 
:[192,86]
 cannot find symbol
[ERROR] symbol:   class WebService
[ERROR] location: class 
org.apache.openejb.client.JaxWsProviderWrapper.ServiceDelegateWrapper
[ERROR] 
:[200,28]
 cannot find symbol
[ERROR] symbol:   class BindingProvider
[ERROR] location: class 
org.apache.openejb.client.JaxWsProviderWrapper.ServiceDelegateWrapper
[ERROR] 
:[204,9]
 method does not override or implement a method from a supertype
[ERROR] 
:[209,9]
 method does not override or implement a method from a supertype
[ERROR] 

Build failed in Jenkins: TomEE » master-build-quick-9.x » TomEE :: Server :: Client #1

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] --< org.apache.tomee:openejb-client >---
[INFO] Building TomEE :: Server :: Client 9.0.0-M8-SNAPSHOT [22/59]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ openejb-client ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
openejb-client ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ openejb-client ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
openejb-client ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 4 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:compile (default-compile) @ 
openejb-client ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 150 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
:[23,22]
 cannot find symbol
  symbol:   class Service
  location: package jakarta.xml.ws
[ERROR] 
:[24,30]
 package jakarta.xml.ws.handler does not exist
[ERROR] 
:[22,19]
 package jakarta.jws does not exist
[ERROR] 
:[26,22]
 cannot find symbol
  symbol:   class BindingProvider
  location: package jakarta.xml.ws
[ERROR] 
:[27,22]
 cannot find symbol
  symbol:   class Dispatch
  location: package jakarta.xml.ws
[ERROR] 
:[28,22]
 cannot find symbol
  symbol:   class Endpoint
  location: package jakarta.xml.ws
[ERROR] 
:[30,22]
 cannot find symbol
  symbol:   class Service
  location: package jakarta.xml.ws
[ERROR] 
:[31,22]
 cannot find symbol
  symbol:   class WebServiceException
  location: package jakarta.xml.ws
[ERROR] 
:[33,30]
 package jakarta.xml.ws.handler does not exist
[ERROR] 
:[34,27]
 package jakarta.xml.ws.soap does not exist
[ERROR] 
:[35,26]
 package 

Jenkins build is unstable: TomEE » master-build-quick-9.x » TomEE :: Container :: Java EE #1

[Apache Jenkins Server]

See 

Build failed in Jenkins: TomEE » master-build-quick-9.x » TomEE :: iTests :: Servlets #1

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] --< org.apache.tomee:openejb-itests-servlets >--
[INFO] Building TomEE :: iTests :: Servlets 9.0.0-M8-SNAPSHOT   [19/59]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
openejb-itests-servlets ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
openejb-itests-servlets ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ openejb-itests-servlets ---
[INFO] 
[INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ 
openejb-itests-servlets ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.6.2:compile (default-compile) @ 
openejb-itests-servlets ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 13 source files to 

[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
:[36,23]
 package jakarta.servlet does not exist
[ERROR] 
:[37,23]
 package jakarta.servlet does not exist
[ERROR] 
:[38,28]
 package jakarta.servlet.http does not exist
[ERROR] 
:[39,28]
 package jakarta.servlet.http does not exist
[ERROR] 
:[40,28]
 package jakarta.servlet.http does not exist
[ERROR] 
:[52,39]
 cannot find symbol
  symbol: class HttpServlet
[ERROR] 
:[98,34]
 cannot find symbol
  symbol:   class HttpServletRequest
  location: class org.apache.openejb.test.servlet.AnnotatedServlet
[ERROR] 
:[98,68]
 cannot find symbol
  symbol:   class HttpServletResponse
  location: class org.apache.openejb.test.servlet.AnnotatedServlet
[ERROR] 
:[98,105]
 cannot find symbol
  symbol:   class ServletException
  location: class org.apache.openejb.test.servlet.AnnotatedServlet
[ERROR] 
:[20,19]
 package jakarta.jws does not exist
[ERROR] 
:[20,19]
 package jakarta.jws does not exist
[ERROR] 
:[22,2]
 cannot find symbol
  symbol: class WebService
[ERROR] 
:[22,2]
 cannot find symbol
  symbol: class WebService
[ERROR] 

Build failed in Jenkins: TomEE » jakarta-deploy » TomEE :: TomEE :: Plume Webapp #838

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] < org.apache.tomee:tomee-plume-webapp >-
[INFO] Building TomEE :: TomEE :: Plume Webapp 9.0.0-M8-SNAPSHOT  [8/9]
[INFO] [ jar ]-
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-core-eclipselink/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-core-eclipselink/8.0.10-SNAPSHOT/maven-metadata.xml
 (796 B at 1.6 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
 (602 B at 1.8 kB/s)
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ tomee-plume-webapp 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
tomee-plume-webapp ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ tomee-plume-webapp ---
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 
https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
 (602 B at 1.9 kB/s)
[INFO] Downloaded from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml
 (602 B at 1.6 kB/s)
[WARNING] Could not transfer metadata 
org.apache.tomee:utils:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/utils/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[INFO] Failure detected.

Build failed in Jenkins: TomEE » jakarta-deploy » TomEE :: TomEE :: MicroProfile Webapp #838

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] -< org.apache.tomee:tomee-microprofile-webapp >-
[INFO] Building TomEE :: TomEE :: MicroProfile Webapp 9.0.0-M8-SNAPSHOT   [6/9]
[INFO] [ jar ]-
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/mp-common/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/mp-common/8.0.10-SNAPSHOT/maven-metadata.xml
 (781 B at 2.3 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/tomee-microprofile/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/tomee-microprofile/8.0.10-SNAPSHOT/maven-metadata.xml
 (615 B at 1.8 kB/s)
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 
https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
 (778 B at 2.4 kB/s)
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
 (778 B at 2.1 kB/s)
[INFO] Downloaded from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml
 (778 B at 2.1 kB/s)
[WARNING] Could not transfer metadata 
org.apache.tomee:mp-jwt:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[WARNING] org.apache.tomee:mp-jwt:8.0.10-SNAPSHOT/maven-metadata.xmlfailed to 
transfer from https://oss.sonatype.org/content/repositories/snapshots during a 
previous attempt. This failure was cached in the local repository and 
resolution will not be reattempted until the update interval of 
sonatype-snapshots has elapsed or updates are forced. Original error: Could not 
transfer metadata org.apache.tomee:mp-jwt:8.0.10-SNAPSHOT/maven-metadata.xml 
from/to sonatype-snapshots 
(https://oss.sonatype.org/content/repositories/snapshots): authorization failed 
for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-cxf/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-cxf/8.0.10-SNAPSHOT/maven-metadata.xml
 (783 B at 2.2 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 
https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (791 B at 2.5 kB/s)
[INFO] Downloaded from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (791 B at 2.4 kB/s)
[INFO] Downloaded from Nexus: 

Build failed in Jenkins: TomEE » jakarta-deploy #838

[Apache Jenkins Server]

See 


Changes:


--
[...truncated 119.12 KB...]
[WARNING] org.apache.tomee:mp-jwt:8.0.10-SNAPSHOT/maven-metadata.xmlfailed to 
transfer from https://oss.sonatype.org/content/repositories/snapshots during a 
previous attempt. This failure was cached in the local repository and 
resolution will not be reattempted until the update interval of 
sonatype-snapshots has elapsed or updates are forced. Original error: Could not 
transfer metadata org.apache.tomee:mp-jwt:8.0.10-SNAPSHOT/maven-metadata.xml 
from/to sonatype-snapshots 
(https://oss.sonatype.org/content/repositories/snapshots): authorization failed 
for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/mp-jwt/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-cxf/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-cxf/8.0.10-SNAPSHOT/maven-metadata.xml
 (783 B at 2.2 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 
https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (791 B at 2.5 kB/s)
[INFO] Downloaded from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (791 B at 2.4 kB/s)
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (791 B at 1.6 kB/s)
[WARNING] Could not transfer metadata 
org.apache.tomee:openejb-webservices:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[WARNING] 
org.apache.tomee:openejb-webservices:8.0.10-SNAPSHOT/maven-metadata.xmlfailed 
to transfer from https://oss.sonatype.org/content/repositories/snapshots during 
a previous attempt. This failure was cached in the local repository and 
resolution will not be reattempted until the update interval of 
sonatype-snapshots has elapsed or updates are forced. Original error: Could not 
transfer metadata 
org.apache.tomee:openejb-webservices:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-webservices/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/tomee-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/tomee-webservices/8.0.10-SNAPSHOT/maven-metadata.xml
 (789 B at 2.4 kB/s)
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ 
tomee-microprofile-webapp ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
tomee-microprofile-webapp ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ tomee-microprofile-webapp ---
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/tomee-microprofile/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/tomee-microprofile/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/tomee-microprofile/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 

Build failed in Jenkins: TomEE » jakarta-deploy » TomEE :: TomEE :: WebProfile Webapp #838

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] --< org.apache.tomee:tomee-webprofile-webapp >--
[INFO] Building TomEE :: TomEE :: WebProfile Webapp 9.0.0-M8-SNAPSHOT [5/9]
[INFO] [ jar ]-
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/taglibs-shade/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/taglibs-shade/8.0.10-SNAPSHOT/maven-metadata.xml
 (1.0 kB at 1.7 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/deps/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/deps/8.0.10-SNAPSHOT/maven-metadata.xml
 (601 B at 1.7 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-client/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-client/8.0.10-SNAPSHOT/maven-metadata.xml
 (786 B at 2.2 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/server/8.0.10-SNAPSHOT/maven-metadata.xml
 (603 B at 1.6 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-ejbd/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-ejbd/8.0.10-SNAPSHOT/maven-metadata.xml
 (784 B at 2.1 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from sonatype-snapshots: 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloading from JBoss Repository: 
https://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Apache Snapshots: 
https://repository.apache.org/content/repositories/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
 (786 B at 691 B/s)
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
 (786 B at 176 B/s)
[INFO] Downloaded from apache-snapshots: 
https://repository.apache.org/content/groups/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml
 (786 B at 161 B/s)
[WARNING] Could not transfer metadata 
org.apache.tomee:openejb-server:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[WARNING] 
org.apache.tomee:openejb-server:8.0.10-SNAPSHOT/maven-metadata.xmlfailed to 
transfer from https://oss.sonatype.org/content/repositories/snapshots during a 
previous attempt. This failure was cached in the local repository and 
resolution will not be reattempted until the update interval of 
sonatype-snapshots has elapsed or updates are forced. Original error: Could not 
transfer metadata 
org.apache.tomee:openejb-server:8.0.10-SNAPSHOT/maven-metadata.xml from/to 
sonatype-snapshots (https://oss.sonatype.org/content/repositories/snapshots): 
authorization failed for 
https://oss.sonatype.org/content/repositories/snapshots/org/apache/tomee/openejb-server/8.0.10-SNAPSHOT/maven-metadata.xml,
 status: 403 Forbidden
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-hsql/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-hsql/8.0.10-SNAPSHOT/maven-metadata.xml
 (784 B at 2.1 kB/s)
[INFO] Downloading from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-http/8.0.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded from Nexus: 
http://repository.apache.org/snapshots/org/apache/tomee/openejb-http/8.0.10-SNAPSHOT/maven-metadata.xml
 (784 B at 1.3 kB/s)
[INFO] Downloading from Nexus: 

Build failed in Jenkins: TomEE » jakarta-deploy » TomEE :: TomEE :: Plus Webapp #838

[Apache Jenkins Server]

See 


Changes:


--
[INFO] 
[INFO] -< org.apache.tomee:tomee-plus-webapp >-
[INFO] Building TomEE :: TomEE :: Plus Webapp 9.0.0-M8-SNAPSHOT   [7/9]
[INFO] [ jar ]-
[INFO] 
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ tomee-plus-webapp 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ 
tomee-plus-webapp ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ tomee-plus-webapp ---
[INFO] Failure detected.

Build failed in Jenkins: TomEE » pull-request #191

[Apache Jenkins Server]

See 


Changes:


--
GitHub pull request #814 to apache/tomee
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on builds31 (ubuntu) in workspace 

The recommended git tool is: NONE
No credentials specified
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository https://github.com/apache/tomee
 > git init  # 
 > timeout=10
Fetching upstream changes from https://github.com/apache/tomee
 > git --version # timeout=10
 > git --version # 'git version 2.17.1'
 > git fetch --tags --progress -- https://github.com/apache/tomee 
 > +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/apache/tomee # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # 
 > timeout=10
Avoid second fetch
 > git config core.sparsecheckout # timeout=10
 > git checkout -f origin/master # timeout=10
 > git branch -a -v --no-abbrev # timeout=10
 > git checkout -b master origin/master # timeout=10
  Opening connection
Done: 0
  Counting objects
Done: 20551
  Finding sources
Done: 0
  Writing objects
Done: 0
  remote: Updating references
Merging refs/tags/changes/191
 > git rev-parse refs/tags/changes/191^{commit} # timeout=10
 > git remote # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git merge b26e9e640e8f305519b86515300b17d98d00ad23 # timeout=10
FATAL: Command "git merge b26e9e640e8f305519b86515300b17d98d00ad23" returned 
status code 1:
stdout: Removing tomee/build.xml
Auto-merging tomee/apache-tomee/pom.xml
Auto-merging pom.xml
CONFLICT (content): Merge conflict in pom.xml
Removing examples/websocket-jms/build.xml
Removing examples/webservice-holder/build.xml
Removing examples/webservice-handlerchain/build.xml
Removing examples/webservice-attachments/build.xml
Removing examples/troubleshooting/build.xml
Removing examples/transaction-rollback/build.xml
Removing examples/testing-transactions/build.xml
Removing examples/testing-transactions-bmt/build.xml
Removing examples/testing-security/build.xml
Removing examples/testing-security-meta/build.xml
Removing examples/testing-security-3/build.xml
Removing examples/testing-security-2/build.xml
Removing examples/testcase-injection/build.xml
Removing examples/telephone-stateful/build.xml
Removing examples/simple-webservice/build.xml
Removing examples/simple-stateless/build.xml
Removing examples/simple-stateless-with-descriptor/build.xml
Removing examples/simple-stateless-callbacks/build.xml
Removing examples/simple-stateful/build.xml
Removing examples/simple-stateful-callbacks/build.xml
Removing examples/simple-singleton/build.xml
Removing examples/simple-mdb/build.xml
Removing examples/simple-mdb-with-descriptor/build.xml
Removing examples/simple-mdb-and-cdi/build.xml
Removing examples/simple-jms/build.xml
Removing examples/simple-jms-context/build.xml
Removing examples/schedule-methods/build.xml
Removing examples/schedule-methods-meta/build.xml
Removing examples/schedule-expression/build.xml
Removing examples/movies-complete/build.xml
Removing examples/movies-complete-meta/build.xml
Removing examples/lookup-of-ejbs/build.xml
Removing examples/lookup-of-ejbs-with-descriptor/build.xml
Removing examples/jpa-enumerated/build.xml
Removing examples/interceptors/build.xml
Removing examples/injection-of-env-entry/build.xml
Removing examples/injection-of-entitymanager/build.xml
Removing examples/injection-of-ejbs/build.xml
Removing examples/injection-of-datasource/build.xml
Removing examples/injection-of-connectionfactory/build.xml
Removing examples/helloworld-weblogic/build.xml
Removing examples/custom-injection/build.xml
Removing examples/component-interfaces/build.xml
Removing examples/async-postconstruct/build.xml
Removing examples/async-methods/build.xml
Removing examples/applicationexception/build.xml
Removing examples/application-composer/build.xml
Removing examples/alternate-descriptors/build.xml
Removing examples/access-timeout/build.xml
Removing examples/access-timeout-meta/build.xml
Auto-merging boms/tomee-webprofile/pom.xml
Auto-merging boms/tomee-plus/pom.xml
Auto-merging boms/tomee-plume/pom.xml
Auto-merging boms/tomee-microprofile/pom.xml
Removing assembly/test/build.xml
Automatic merge failed; fix conflicts and then commit the result.

stderr: 
Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to builds31
at 
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1800)
at 
hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)
at hudson.remoting.Channel.call(Channel.java:1001)
at 
hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:286)
   

[jira] [Commented] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493202#comment-17493202
 ] 

Rene Bangemann commented on TOMEE-3840:
---

Thanks for the soon reply and fix! :)

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (TOMEE-3841) Upgrade SLF4J to 1.7.36

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-3841.

Fix Version/s: 8.0.11
   Resolution: Fixed

> Upgrade SLF4J to 1.7.36
> ---
>
> Key: TOMEE-3841
> URL: https://issues.apache.org/jira/browse/TOMEE-3841
> Project: TomEE
>  Issue Type: Dependency upgrade
>Affects Versions: 8.0.9, 8.0.10
>Reporter: Richard Zowalla
>Assignee: Richard Zowalla
>Priority: Minor
> Fix For: 8.0.11
>
>
> h3. https://www.slf4j.org/news.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[tomee] branch master updated: TOMEE-3841 - Upgrades slf4j

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git


The following commit(s) were added to refs/heads/master by this push:
 new d2873e0  TOMEE-3841 - Upgrades slf4j
d2873e0 is described below

commit d2873e0513fe68994455e85116a1444b648fcd47
Author: Richard Zowalla 
AuthorDate: Wed Feb 16 12:03:28 2022 +0100

TOMEE-3841 - Upgrades slf4j
---
 boms/tomee-microprofile/pom.xml | 4 ++--
 boms/tomee-plume/pom.xml| 4 ++--
 boms/tomee-plus/pom.xml | 4 ++--
 boms/tomee-webprofile/pom.xml   | 4 ++--
 pom.xml | 2 +-
 5 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/boms/tomee-microprofile/pom.xml b/boms/tomee-microprofile/pom.xml
index 891a35b..ba964d5 100644
--- a/boms/tomee-microprofile/pom.xml
+++ b/boms/tomee-microprofile/pom.xml
@@ -2083,7 +2083,7 @@
 
   org.slf4j
   slf4j-api
-  1.7.21
+  1.7.36
   
 
   *
@@ -2094,7 +2094,7 @@
 
   org.slf4j
   slf4j-jdk14
-  1.7.21
+  1.7.36
   
 
   *
diff --git a/boms/tomee-plume/pom.xml b/boms/tomee-plume/pom.xml
index 13dd2d4..3ada1ea 100644
--- a/boms/tomee-plume/pom.xml
+++ b/boms/tomee-plume/pom.xml
@@ -2182,7 +2182,7 @@
 
   org.slf4j
   slf4j-api
-  1.7.21
+  1.7.36
   
 
   *
@@ -2193,7 +2193,7 @@
 
   org.slf4j
   slf4j-jdk14
-  1.7.21
+  1.7.36
   
 
   *
diff --git a/boms/tomee-plus/pom.xml b/boms/tomee-plus/pom.xml
index 7b82e26..2023ca3 100644
--- a/boms/tomee-plus/pom.xml
+++ b/boms/tomee-plus/pom.xml
@@ -2215,7 +2215,7 @@
 
   org.slf4j
   slf4j-api
-  1.7.21
+  1.7.36
   
 
   *
@@ -2226,7 +2226,7 @@
 
   org.slf4j
   slf4j-jdk14
-  1.7.21
+  1.7.36
   
 
   *
diff --git a/boms/tomee-webprofile/pom.xml b/boms/tomee-webprofile/pom.xml
index e29481c..cbb0790 100644
--- a/boms/tomee-webprofile/pom.xml
+++ b/boms/tomee-webprofile/pom.xml
@@ -1313,7 +1313,7 @@
 
   org.slf4j
   slf4j-api
-  1.7.21
+  1.7.36
   
 
   *
@@ -1324,7 +1324,7 @@
 
   org.slf4j
   slf4j-jdk14
-  1.7.21
+  1.7.36
   
 
   *
diff --git a/pom.xml b/pom.xml
index dcd6f69..98c5613 100644
--- a/pom.xml
+++ b/pom.xml
@@ -199,7 +199,7 @@
 1.1
 2.3.9
 2.3.15
-1.7.21
+1.7.36
 1.2.17
 2.17.1
 4.2.0

[jira] [Created] (TOMEE-3841) Upgrade SLF4J to 1.7.36

[Richard Zowalla (Jira)]

Richard Zowalla created TOMEE-3841:
--

 Summary: Upgrade SLF4J to 1.7.36
 Key: TOMEE-3841
 URL: https://issues.apache.org/jira/browse/TOMEE-3841
 Project: TomEE
  Issue Type: Dependency upgrade
Affects Versions: 8.0.9, 8.0.10
Reporter: Richard Zowalla
Assignee: Richard Zowalla


h3. https://www.slf4j.org/news.html



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Richard Zowalla (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493172#comment-17493172
 ] 

Richard Zowalla commented on TOMEE-3840:


[~rene_b] Thanks for reporting. I could reproduce it for MP, Plus, Plume as 
well and just pushed a fix, which should fix this in 8.0.11 (as 8.0.10 is 
already under vote atm)

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Resolved] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla resolved TOMEE-3840.

Fix Version/s: 8.0.11
   Resolution: Fixed

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
> Fix For: 8.0.11
>
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[tomee] branch master updated: TOMEE-3840 - Fix TomEE does not start with security enabled

[rzo1]

This is an automated email from the ASF dual-hosted git repository.

rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git


The following commit(s) were added to refs/heads/master by this push:
 new 18f174b  TOMEE-3840 - Fix TomEE does not start with security enabled
18f174b is described below

commit 18f174b6acb6873c41f7da73f8a1cd952be95e87
Author: Richard Zowalla 
AuthorDate: Wed Feb 16 11:52:58 2022 +0100

TOMEE-3840 - Fix TomEE does not start with security enabled
---
 .../src/main/resources/tomee/conf/catalina.policy | 4 
 boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy| 4 
 boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy | 4 
 .../src/main/resources/tomee/conf/catalina.policy | 4 
 tomee/apache-tomee/pom.xml| 3 +++
 tomee/apache-tomee/src/main/assembly/tomee-microprofile.xml   | 8 
 tomee/apache-tomee/src/main/assembly/tomee-plume.xml  | 8 
 tomee/apache-tomee/src/main/assembly/tomee-plus.xml   | 8 
 tomee/apache-tomee/src/main/assembly/tomee-webprofile.xml | 8 
 .../apache-tomee/src/main/resources}/catalina.policy  | 4 
 10 files changed, 55 insertions(+)

diff --git 
a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..1a081a3 100644
--- a/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-microprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,10 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..1a081a3 100644
--- a/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plume/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,10 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..1a081a3 100644
--- a/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-plus/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,10 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission "accessDeclaredMembers";
+
 // Note: To enable per context logging configuration, permit read 
access to
 // the appropriate file. Be sure that the logging configuration is
 // secure before enabling such access.
diff --git 
a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy 
b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
index 7aab95d..1a081a3 100644
--- a/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
+++ b/boms/tomee-webprofile/src/main/resources/tomee/conf/catalina.policy
@@ -94,6 +94,10 @@ grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
 permission java.util.PropertyPermission 
"org.apache.juli.ClassLoaderLogManager.debug", "read";
 permission java.util.PropertyPermission "catalina.base", "read";
 
+// TOMEE-3840
+permission java.util.PropertyPermission "tomee.skip-tomcat-log", 
"read";
+permission java.lang.RuntimePermission 

[jira] [Assigned] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Richard Zowalla (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Richard Zowalla reassigned TOMEE-3840:
--

Assignee: Richard Zowalla

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Assignee: Richard Zowalla
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Comment Edited] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493113#comment-17493113
 ] 

Rene Bangemann edited comment on TOMEE-3840 at 2/16/22, 9:42 AM:
-

The following changes in catalina.policy are necessary to start TomEE 
successfully with security enabled:

grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
    ...
{color:#00875a}    permission java.util.PropertyPermission 
"tomee.skip-tomcat-log", "read";{color}
{color:#00875a}    {color}{color:#00875a}permission java.lang.RuntimePermission 
"accessDeclaredMembers";{color}
};


was (Author: JIRAUSER285303):
The following changes in catalina.policy are neccessary to start TomEE 
successfully with security enabled:

grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
    ...
{color:#00875a}    permission java.util.PropertyPermission 
"tomee.skip-tomcat-log", "read";{color}
{color:#00875a}    {color}{color:#00875a}permission java.lang.RuntimePermission 
"accessDeclaredMembers";{color}
};

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

 [ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rene Bangemann updated TOMEE-3840:
--
Component/s: TomEE Core Server

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>  Components: TomEE Core Server
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Commented] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

[ 
https://issues.apache.org/jira/browse/TOMEE-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17493113#comment-17493113
 ] 

Rene Bangemann commented on TOMEE-3840:
---

The following changes in catalina.policy are neccessary to start TomEE 
successfully with security enabled:

grant codeBase "file:${catalina.home}/bin/tomcat-juli.jar" {
    ...
{color:#00875a}    permission java.util.PropertyPermission 
"tomee.skip-tomcat-log", "read";{color}
{color:#00875a}    {color}{color:#00875a}permission java.lang.RuntimePermission 
"accessDeclaredMembers";{color}
};

> TomEE WebProfile 8.0.9 does not start with security enabled
> ---
>
> Key: TOMEE-3840
> URL: https://issues.apache.org/jira/browse/TOMEE-3840
> Project: TomEE
>  Issue Type: Bug
>Affects Versions: 8.0.9
> Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 
> (2021-08-03) x86_64 GNU/Linux
>Reporter: Rene Bangemann
>Priority: Major
>  Labels: catalina.policy
>
> Start TomEE via "catalina.sh start -security"
> The start of TomEE fails with the following exception:
> _NOTE: Picked up JDK_JAVA_OPTIONS:  
> --add-opens=java.base/java.lang=ALL-UNNAMED 
> --add-opens=java.base/java.io=ALL-UNNAMED 
> --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
> _va.util.concurrent=ALL-UNNAMED 
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
> _Exception in thread "main" java.lang.ExceptionInInitializerError_
> _Caused by: org.apache.juli.logging.LogConfigurationException: 
> java.lang.reflect.InvocationTargetException_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
>         _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
>         _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
> _Caused by: java.lang.reflect.InvocationTargetException_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>  Method)_
>         _at 
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
>         _at 
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
>         _at 
> java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
>         _at 
> org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
>         _... 3 more_
> {color:#FF}_Caused by: java.security.AccessControlException: access 
> denied ("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
>         _at 
> java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
>         _at 
> java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
>         _at 
> java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
>         _at 
> java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
>         _at java.base/java.lang.System.getProperty(System.java:816)_
>         _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
>         _at 
> org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
>         _... 8 more_
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Created] (TOMEE-3840) TomEE WebProfile 8.0.9 does not start with security enabled

[Rene Bangemann (Jira)]

Rene Bangemann created TOMEE-3840:
-

 Summary: TomEE WebProfile 8.0.9 does not start with security 
enabled
 Key: TOMEE-3840
 URL: https://issues.apache.org/jira/browse/TOMEE-3840
 Project: TomEE
  Issue Type: Bug
Affects Versions: 8.0.9
 Environment: Linux 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) 
x86_64 GNU/Linux
Reporter: Rene Bangemann


Start TomEE via "catalina.sh start -security"

The start of TomEE fails with the following exception:

_NOTE: Picked up JDK_JAVA_OPTIONS:  --add-opens=java.base/java.lang=ALL-UNNAMED 
--add-opens=java.base/java.io=ALL-UNNAMED 
--add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/ja_
_va.util.concurrent=ALL-UNNAMED 
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED_
_Exception in thread "main" java.lang.ExceptionInInitializerError_
_Caused by: org.apache.juli.logging.LogConfigurationException: 
java.lang.reflect.InvocationTargetException_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:139)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:156)_
        _at org.apache.juli.logging.LogFactory.getLog(LogFactory.java:211)_
        _at org.apache.catalina.startup.Bootstrap.(Bootstrap.java:50)_
_Caused by: java.lang.reflect.InvocationTargetException_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
 Method)_
        _at 
java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)_
        _at 
java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)_
        _at 
java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)_
        _at org.apache.juli.logging.LogFactory.getInstance(LogFactory.java:137)_
        _... 3 more_
{color:#FF}_Caused by: java.security.AccessControlException: access denied 
("java.util.PropertyPermission" "tomee.skip-tomcat-log" "read")_{color}
        _at 
java.base/java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)_
        _at 
java.base/java.security.AccessController.checkPermission(AccessController.java:897)_
        _at 
java.base/java.lang.SecurityManager.checkPermission(SecurityManager.java:322)_
        _at 
java.base/java.lang.SecurityManager.checkPropertyAccess(SecurityManager.java:1066)_
        _at java.base/java.lang.System.getProperty(System.java:816)_
        _at java.base/java.lang.Boolean.getBoolean(Boolean.java:265)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.initialize(TomEELog.java:33)_
        _at 
org.apache.tomee.jul.formatter.log.TomEELog.(TomEELog.java:78)_
        _... 8 more_

 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)