geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <>
Subject [jira] Commented: (GERONIMO-1421) DB portlet failure in Tomcat only
Date Sat, 07 Jan 2006 23:37:45 GMT
    [ ] 

Aaron Mulder commented on GERONIMO-1421:

Here's what I found:

If you follow the procedure above and click "Test Connection", it gets to DatabasePoolPortlet
line 332 which calls ActionResponse.setRenderParameter("mode", "test").

Then the subsequent render request gets to DatabasePoolPortlet line 603 which calls RenderRequest.getParameter("mode").
 Here it gets null, which is an error, since we previously set a value for "mode".

This only seems to happen if the database URL (render parameter "url") ends in ;create=true
(e.g. "jdbc:derby:TestDatabase;create=true").  If the URL is the same but does not end in
;create=true then this does not happen.

I think this is a problem in Tomcat.  The same thing does not happen with Jetty.  Though it
could also be that Pluto is doing something non-standard that the two web containers handle

> DB portlet failure in Tomcat only
> ---------------------------------
>          Key: GERONIMO-1421
>          URL:
>      Project: Geronimo
>         Type: Bug
>   Components: console, Tomcat
>     Versions: 1.0
>     Reporter: Aaron Mulder
>      Fix For: 1.1

>  - create a new database pool using the DB portlet
>  - select the "Derby Embedded" type
>  - pick the derby or derby-client JAR
>  - give it a new or existing database name
>  - add ;create=true to the end of the generated URL
>  - click test
> This procedure works in the Jetty build but does not work in the Tomcat build.  In Tomcat,
it just redirects to the main screen for that portlet without any error message.  The database
is actually created (visible in the DB Manager portlet).  This does not happen if you remove
;create=true from the URL and use an existing database.

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