Child pages
  • Removing database pools
Skip to end of metadata
Go to start of metadata

You have two alternatives for removing database pools. You can use either the Installed J2EE Connectors portlet available from the administration console or the command line Deployer tool.

If you choose to use the Installed J2EE Connectors portlet, click J2EE Connectors from the Administration Console to access the portlet.

This portlet lists all the available connectors and you can stop, start, and uninstall any of those J2EE connectors. To remove a database pool, click the Uninstall link for that database pool.

You can also remove the database pools by using the Deployer tool. Among other things, you can use this tool to remove the available modules. The connection pools are listed by moduleID. On the administration console, the moduleID is listed in the Component Name column.

For example, to remove the Derby_Test connection pool, type the following command from the <geronimo_home>\bin directory:

deploy --user system --password manager undeploy console.dbpool/Derby_Test/1.0/rar

You will see a list similar to the following example, indicating that the Derby_Test database pool is removed from the server:

>deploy --user system --password manager undeploy console.dbpool/Derby_Test/1.0/rar
Using GERONIMO_BASE:   E:\g\server\branches\2.2\assemblies\geronimo-tomcat6-javaee5\target\assembly
Using GERONIMO_HOME:   E:\g\server\branches\2.2\assemblies\geronimo-tomcat6-javaee5\target\assembly
Using GERONIMO_TMPDIR: var\temp
Using JRE_HOME:        d:\sunsdk160\jre
    Module console.dbpool/Derby_Test/1.0/rar unloaded.
    Module console.dbpool/Derby_Test/1.0/rar uninstalled.

    Undeployed console.dbpool/Derby_Test/1.0/rar
  • No labels