[
https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan updated GERONIMO-4377:
---------------------------
Attachment: Geronimo-4377.patch
I remove the last patch, for it seems that it is not proper to unload the
configuration gbean if its sub-gbeans failes to start.
Turn to another solution, while querying the connector status, if we found the
configuration gbean's state is running, then double check whether its
sub-gbean's status is running too. If not, show the current connector is in
the stopping status.
Please help to review the patch, thanks !
> Fail to indicate datasource create unsuccessfully in admin console "database
> pool" porlet when choosing wrong database driver
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: GERONIMO-4377
> URL: https://issues.apache.org/jira/browse/GERONIMO-4377
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: databases
> Affects Versions: 2.1.3
> Environment: Any plateform(windows or Linux)
> Reporter: viola.lu
> Priority: Minor
> Attachments: Geronimo-4377.patch
>
>
> 1.Login geronimo admin console, go to "database pools" porlet ->"using the
> geronimo database pool wizard"
> ->input datasource name "test", database type"db2 xa" or other type you would
> like.Click "next."
> 2.Choose any jar liseted as db2 xa driver,input other required fileds.Click
> "deploy"
> 3.No hint to indicate it fail or succes.And go to "J2EE Connectors", you will
> find there is a newly created component :"console.dbpool/test/1.0/rar", and
> status is "running" , if you restart this component, error popsup.
> 4.Also go to "$geronimo_install_dir/repository/console/dbpool", a newly
> created folder "test" exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
