[
https://issues.apache.org/jira/browse/GERONIMO-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466242
]
Paul McMahan commented on GERONIMO-2709:
----------------------------------------
I took a look at the patch and am wondering whether it matters if
WebUserDataPermission is created using the pathInContext passed to the method
instead of letting the WebUserDataPermission constructor determine everything
from the request?
> Database creation pool wizard fails in Jetty
> --------------------------------------------
>
> Key: GERONIMO-2709
> URL: https://issues.apache.org/jira/browse/GERONIMO-2709
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, databases
> Affects Versions: 2.0-M2
> Environment: Jetty Dist. rev #494097 . Related to GERONIMO-2685
> Reporter: Hernan Cunico
> Priority: Critical
> Attachments: G2709.patch
>
>
> DB Pool creation wizard fails on Jetty distribution. It will now list the
> available database types (step 1) but once you click next the console is
> gone.
> The following error is displayed on the terminal. I can't set log to DEBUG,
> if so I loose control on Jetty (wont even pass login screen - different issue)
> 2007-01-08 15:32:21.671::WARN: EXCEPTION
> java.lang.IllegalArgumentException: Qualifier patterns must be present when
> first URLPattern is an exact pattern
> at javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:98)
> at
> javax.security.jacc.WebUserDataPermission.<init>(WebUserDataPermission.java:86)
> at
> org.apache.geronimo.jetty6.handler.JettySecurityHandler.checkSecurityConstraints(JettySecurityHandler.java:183)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:171)
> at
> org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:133)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at
> org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
> at
> org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
> at
> org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
> at
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> at org.mortbay.jetty.Server.handle(Server.java:285)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:751)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:500)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:203)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
> at
> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:217)
> at
> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
> Server shutdown begun
> Server shutdown completed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
