geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <>
Subject [jira] Resolved: (GERONIMO-2320) New DB pool didn't show up until restarted
Date Mon, 27 Nov 2006 07:50:21 GMT
     [ ]

Vamsavardhana Reddy resolved GERONIMO-2320.

    Resolution: Fixed

I have tried to re-create the problem in Tomcat server built from branches\1.1 rev 477080
.  I have successfully created a new database pool for Postgre SQL including the driver download
step.  The newly created pool showed in the listing without having to restart the server etc.
 Please reopen the issue if the problem still exists.

Console output given below:
13:11:04,891 INFO  [DWRServlet] retrieved system configuration file: java.util.z
13:11:05,852 INFO  [DatabasePoolPortlet] Downloading postgresql/postgresql-7.3/7
13:11:56,986 INFO  [DatabasePoolPortlet] Finished downloading 184505 b
Deployment completed successfully!

> New DB pool didn't show up until restarted
> ------------------------------------------
>                 Key: GERONIMO-2320
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment, console, databases
>    Affects Versions: 1.1
>         Environment: Geronimo 1.1 Tomcat
>            Reporter: Aaron Mulder
>             Fix For: 1.1.2
> Deployed a new MySQL database pool using the console wizard in the Geronimo 1.1 Tomcat
J2EE distribution (including downloading a driver for it).  When it finished, the stdout said
"Deployment completed successfully!" but the new pool did not show up in the list in the Database
Pools portlet.  I stopped and started the module using the J2EE Connectors screen and then
it showed up in the Database Pools list.  Haven't seen this in the Jetty build.  Need to try
to reproduce on a totally clean 1.1 and 1.1.1 Tomcat/J2EE build.

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