应用程序引擎上的slf4j AccessControlException [英] slf4j AccessControlException on app engine
问题描述
我试图做的是使用 luceneappengine's GaeDirectory 。显然它需要有slf4j。所以我在我的项目中添加了jar slf4j-api-1.7.12.jar
。现在我收到以下错误跟踪。所以luceneappengine是为GAE明确创建的。那么为什么在这个世界上它需要一个当Java本身带有一个记录器时不易支持的记录器呢?
com.google.api.server.spi.SystemService invokeServiceMethod:调用备用方法时发生异常
java.lang.ExceptionInInitializerError
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:149)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:120)
在org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:331)
在org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
在org.slf4j.LoggerFactory.getLogger(LoggerFactory.java :304)
at com.googlecode.luceneappengine.GaeDirectory。< clinit>(GaeDirectory.java:56)
...
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)$ b $ at java.lang.reflect.Method.invoke (Method.java:45)
在com.google.api.server.spi.SystemService.invokeServiceMethod(SystemService.java:359)
的com.google.api.server.spi.SystemServiceServlet.execute(SystemServiceServlet.java:160)
com.google.api.server.spi.SystemServiceServlet.doPost(SystemServiceServlet.java:118)
位于javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
位于javax.servlet .http.HttpServlet.service(HttpServlet.java:717)在org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1166)
在com.googlecode.objectify.ObjectifyFilter.doFilter(ObjectifyFilter.java:48)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter (ServletHandler.java:1157)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter (ServletHandler.java:1157)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
在org.mortbay.jetty.servlet.ServletHandler $ CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay .jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server .handle(Server.java:326)
在org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)在org.mortbay.jetty.HttpConnection $ RequestHandler.headerComplete
(HttpConnection.java :923)
在org.mortbay.jetty.HttpConnection。处理(HttpConnection.java:404)
,位于com.google.tracing.TraceContext $ TraceContextRunnable.runInContext(TraceContext.java:437)
,位于com.google.tracing.TraceContext $ TraceContextRunnable $ 1.run(TraceContext的.java:444)在com.google.tracing.CurrentContext.runInContext(CurrentContext.java:220
)
在com.google.tracing.TraceContext $ AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308)
at com.google.tracing.TraceContext $ AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300)
at com.google.tracing.TraceContext $ TraceContextRunnable.run(TraceContext.java:441)
at java.lang.Thread.run(Thread.java:745)
导致:java.security.AccessControlException:在java.security中访问被拒绝(java.lang.RuntimePermissioncreateSecurityManager)
。 AccessControlContext.checkPermission(AccessControlContext.java:382)
在java.security.AccessController.checkPermission(AccessController.java:572)在java.lang.SecurityManager.checkPermission(SecurityManager.java:549)上
;在java.lang.SecurityManager上
。< init>(SecurityManager.java:299)
at org.slf4j。 < init>(Util.java:43)
at org.slf4j.helpers.Util $ ClassContextSecurityManager。< init>(Util.java:43)
at org。 slf4j.helpers.Util。< clinit>(Util.java:49)
... 42 more
>
导致:java.security.AccessControlException:访问被拒绝(java.lang.RuntimePermissioncreateSecurityManager)$ b $在java.security.AccessControlContext.checkPermission(AccessControlContext.java:382)
at java.security.AccessController.checkPermission(AccessController.java:572)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.SecurityManager。< init>(Util.java:43)
at org.slf4j.helpers.Util $ ClassContextSecurityManager。< init>(Security.java:299) < init>(Util.java:43)
at org.slf4j.helpers.Util。< clinit>(Util.java:49)
$ slf4j.helpers.Util $ ClassContextSecurityManager。 c $ c>
特定于slf4j-api版本 1.7.9至1.7.12 。它在昨天发布的版本 1.7.13 中修复,以解决这个问题。
All I am trying to do is use luceneappengine's GaeDirectory. Apparently it needed to have slf4j. So I added the jar slf4j-api-1.7.12.jar
to my project. Now I am getting the following error trace. So luceneappengine is created expressly for GAE. So why in the world would it require a logger that is not readily supported when Java itself comes with a logger? What am I missing here?
com.google.api.server.spi.SystemService invokeServiceMethod: exception occurred while calling backed method
java.lang.ExceptionInInitializerError
at org.slf4j.LoggerFactory.bind(LoggerFactory.java:149)
at org.slf4j.LoggerFactory.performInitialization(LoggerFactory.java:120)
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:331)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:304)
at com.googlecode.luceneappengine.GaeDirectory.<clinit>(GaeDirectory.java:56)
…
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:45)
at com.google.api.server.spi.SystemService.invokeServiceMethod(SystemService.java:359)
at com.google.api.server.spi.SystemServiceServlet.execute(SystemServiceServlet.java:160)
at com.google.api.server.spi.SystemServiceServlet.doPost(SystemServiceServlet.java:118)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.googlecode.objectify.ObjectifyFilter.doFilter(ObjectifyFilter.java:48)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at com.google.tracing.TraceContext$TraceContextRunnable.runInContext(TraceContext.java:437)
at com.google.tracing.TraceContext$TraceContextRunnable$1.run(TraceContext.java:444)
at com.google.tracing.CurrentContext.runInContext(CurrentContext.java:220)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContextNoUnref(TraceContext.java:308)
at com.google.tracing.TraceContext$AbstractTraceContextCallback.runInInheritedContext(TraceContext.java:300)
at com.google.tracing.TraceContext$TraceContextRunnable.run(TraceContext.java:441)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "createSecurityManager")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:382)
at java.security.AccessController.checkPermission(AccessController.java:572)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.SecurityManager.<init>(SecurityManager.java:299)
at org.slf4j.helpers.Util$ClassContextSecurityManager.<init>(Util.java:43)
at org.slf4j.helpers.Util$ClassContextSecurityManager.<init>(Util.java:43)
at org.slf4j.helpers.Util.<clinit>(Util.java:49)
... 42 more
The problem you encounter identified by the following exception (same as the root cause given above)
Caused by: java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "createSecurityManager")
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:382)
at java.security.AccessController.checkPermission(AccessController.java:572)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.lang.SecurityManager.<init>(SecurityManager.java:299)
at org.slf4j.helpers.Util$ClassContextSecurityManager.<init>(Util.java:43)
at org.slf4j.helpers.Util$ClassContextSecurityManager.<init>(Util.java:43)
at org.slf4j.helpers.Util.<clinit>(Util.java:49)
is specific to slf4j-api versions 1.7.9 to 1.7.12. It is fixed in version 1.7.13 which was released yesterday to fix this same issue.
这篇关于应用程序引擎上的slf4j AccessControlException的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!