buildbot failure in on tomee-trunk-ubuntu-jvm8
The Buildbot has detected a new failure on builder tomee-trunk-ubuntu-jvm8 while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/521 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-jvm8-commit' triggered this build Build Source Stamp: [branch master] 4e1571d098c078bdeac97abef0c948237a4c8a9b Blamelist: rmannibucau BUILD FAILED: failed compile Sincerely, -The Buildbot
buildbot failure in on tomee-trunk-ubuntu
The Buildbot has detected a new failure on builder tomee-trunk-ubuntu while building tomee. Full details are available at: https://ci.apache.org/builders/tomee-trunk-ubuntu/builds/586 Buildbot URL: https://ci.apache.org/ Buildslave for this Build: hemera_ubuntu Build Reason: The SingleBranchScheduler scheduler named 'on-tomee-trunk-ubuntu-commit' triggered this build Build Source Stamp: [branch master] 4e1571d098c078bdeac97abef0c948237a4c8a9b Blamelist: rmannibucau BUILD FAILED: failed compile Sincerely, -The Buildbot
[jira] [Updated] (TOMEE-1864) tomcat 8.5.6
[ https://issues.apache.org/jira/browse/TOMEE-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated TOMEE-1864: -- Summary: tomcat 8.5.6 (was: tomcat 8.5.5) > tomcat 8.5.6 > > > Key: TOMEE-1864 > URL: https://issues.apache.org/jira/browse/TOMEE-1864 > Project: TomEE > Issue Type: Dependency upgrade >Reporter: Romain Manni-Bucau >Assignee: Romain Manni-Bucau > Fix For: 7.0.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
tomee git commit: tomcat 8.5.6
Repository: tomee Updated Branches: refs/heads/master 14c7483b9 -> 4e1571d09 tomcat 8.5.6 Project: http://git-wip-us.apache.org/repos/asf/tomee/repo Commit: http://git-wip-us.apache.org/repos/asf/tomee/commit/4e1571d0 Tree: http://git-wip-us.apache.org/repos/asf/tomee/tree/4e1571d0 Diff: http://git-wip-us.apache.org/repos/asf/tomee/diff/4e1571d0 Branch: refs/heads/master Commit: 4e1571d098c078bdeac97abef0c948237a4c8a9b Parents: 14c7483 Author: rmannibucau Authored: Tue Oct 11 22:34:13 2016 +0200 Committer: rmannibucau Committed: Tue Oct 11 22:34:13 2016 +0200 -- pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/tomee/blob/4e1571d0/pom.xml -- diff --git a/pom.xml b/pom.xml index 782ed64..5fc5677 100644 --- a/pom.xml +++ b/pom.xml @@ -127,7 +127,7 @@ 2.0.0-alpha-7 1.2.2 -8.5.5 +8.5.6 3.1.7 2.9.0
[jira] [Commented] (TOMEE-1956) Security Permission "doAsPrivileged"
[
https://issues.apache.org/jira/browse/TOMEE-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15564997#comment-15564997
]
Magesh commented on TOMEE-1956:
---
If we don't provide java.security.AllPermission to tomee we are not getting any
log and tomee is not getting deployed properly.
> Security Permission "doAsPrivileged"
>
>
> Key: TOMEE-1956
> URL: https://issues.apache.org/jira/browse/TOMEE-1956
> Project: TomEE
> Issue Type: Bug
>Affects Versions: 7.0.0-M1
> Environment: Tomcat 8.0.36
>Reporter: Magesh
> Labels: security
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Hi,
> We are using tomee 7.0.0-M1 plugin war in our Tomcat 8 server for EJB
> application deployment.
> We are not facing any issue if we start the tomcat server normally and all
> our EJB applications are getting deployed properly.
> If we start the tomcat server with security mode enabled -security, while
> accessing some modules in our application we are getting the below exception
> to add "doAsPrivileged" security permission in policy file.
> permission javax.security.auth.AuthPermission "doAsPrivileged";
> Log:
>
> ---
> org.apache.openejb.core.ThreadContext.enter ThreadContextListener threw
> an exception
> java.security.AccessControlException: access denied
> ("javax.security.auth.AuthPermission" "doAsPrivileged")
> at
> java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
> at
> java.security.AccessController.checkPermission(AccessController.java:884)
> at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
> at javax.security.auth.Subject.doAsPrivileged(Subject.java:467)
> at
> org.apache.openejb.core.security.AbstractSecurityService$SecurityContext.(AbstractSecurityService.java:408)
> at
> org.apache.openejb.core.security.AbstractSecurityService.contextEntered(AbstractSecurityService.java:167)
> at org.apache.openejb.core.ThreadContext.enter(ThreadContext.java:60)
> at
> org.apache.openejb.core.stateless.StatelessContainer.invoke(StatelessContainer.java:169)
> at
> org.apache.openejb.core.ivm.EjbHomeProxyHandler.create(EjbHomeProxyHandler.java:343)
> at
> org.apache.openejb.core.ivm.EjbHomeProxyHandler._invoke(EjbHomeProxyHandler.java:196)
> at
> org.apache.openejb.core.ivm.BaseEjbProxyHandler.invoke(BaseEjbProxyHandler.java:319)
> at com.sun.proxy.$Proxy51.create(Unknown Source)
> at
> org.apache.openejb.core.ivm.naming.BusinessLocalReference.getObject(BusinessLocalReference.java:36)
> at
> org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:175)
> at
> org.apache.openejb.core.ivm.naming.IvmContext.lookup(IvmContext.java:291)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:829)
> at org.apache.naming.NamingContext.lookup(NamingContext.java:166)
> at org.apache.naming.SelectorContext.lookup(SelectorContext.java:157)
> at javax.naming.InitialContext.lookup(InitialContext.java:417)
>
>
> But as per our policy they wont provide this permission. Could you please
> let us know whether this issue is fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
