geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2709) Database creation pool wizard fails in Jetty
Date Sun, 21 Jan 2007 09:09:30 GMT


David Jencks commented on GERONIMO-2709:

1. I can't reproduce this problem, the wizard seems to work fine for me.  Is this perhaps
a windows problem?

2. The patch is wrong.  WebUserDataPermission has no way to determine if the request is integral
but not confidential from the request.  We have to use jetty specific methods to do this and
pass in the transport type.

Since the constructor we use for WebUserDataPermission needs to NOT escape colons, since they
are used for qualifying patterns, I think we need to escape the colons in the JettySecurityHandler
code.  I'll attach a patch... I'll apply it if someone can verify it fixes the problem which
(see 1) I don't see.

> Database creation pool wizard fails in Jetty
> --------------------------------------------
>                 Key: GERONIMO-2709
>                 URL:
>             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-2.patch, 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<init>(
>         at<init>(
>         at org.apache.geronimo.jetty6.handler.JettySecurityHandler.checkSecurityConstraints(
>         at
>         at org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(
>         at org.mortbay.jetty.servlet.SessionHandler.handle(
>         at org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(
>         at org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(
>         at org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(
>         at org.mortbay.jetty.handler.ContextHandler.handle(
>         at org.mortbay.jetty.webapp.WebAppContext.handle(
>         at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
>         at org.mortbay.jetty.handler.HandlerCollection.handle(
>         at org.mortbay.jetty.handler.HandlerWrapper.handle(
>         at org.mortbay.jetty.Server.handle(
>         at org.mortbay.jetty.HttpConnection.handleRequest(
>         at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
>         at org.mortbay.jetty.HttpParser.parseNext(
>         at org.mortbay.jetty.HttpParser.parseAvailable(
>         at org.mortbay.jetty.HttpConnection.handle(
>         at$
>         at org.mortbay.thread.BoundedThreadPool$
> 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:
For more information on JIRA, see:


View raw message