geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anita kulshreshtha <a_kuls...@yahoo.com>
Subject Re: [jira] Commented: (GERONIMO-2320) New DB pool didn't show up until restarted
Date Thu, 05 Oct 2006 16:41:20 GMT
I do not see this problem on the trunk. This morning  I also deployed a MYSQL DBPool on tomcat-j2ee
using 
.... Download Driver --> Skip Test and Show Plan --> Deploy Pool 
and it worked fine. The pool was listed in 'Database Pools'.

Thanks
Anita

----- Original Message ----
From: Aaron Mulder (JIRA) <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Sent: Thursday, October 5, 2006 11:23:20 AM
Subject: [jira] Commented: (GERONIMO-2320) New DB pool didn't show up until restarted

    [ http://issues.apache.org/jira/browse/GERONIMO-2320?page=comments#action_12440162 ] 
            
Aaron Mulder commented on GERONIMO-2320:
----------------------------------------

Just had it happen on the Jetty build with a PostgreSQL pool (likewise when I just downloaded
the driver, though I haven't tried it with a pre-existing driver).

> New DB pool didn't show up until restarted
> ------------------------------------------
>
>                 Key: GERONIMO-2320
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2320
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: console, databases, deployment
>    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: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        







Mime
View raw message