geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (GERONIMO-4377) Fail to indicate datasource create unsuccessfully in admin console "database pool" porlet when choosing wrong database driver
Date Sun, 09 Nov 2008 15:12:44 GMT

    [ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646078#action_12646078
] 

xuhaihong edited comment on GERONIMO-4377 at 11/9/08 7:11 AM:
---------------------------------------------------------

Sometimes, an exception occurs in the  doRecovery method below.
.....
public void doStart() throws Exception {
        ......        
        // The exception is occured at the line below, but this method's signature does not
contain any throws, so it kept the exception.
        connectionManagerContainer.doRecovery(managedConnectionFactory);        
    }

It seems that this method is used to recovery the status. Since the signature of this method
does not throw any exception. 
So all the exception occurs in this method could be ignored, righ ?

By the way,  I could find the source code for connectionManagerContainer's implementation
org.apache.geronimo.connector.outbound.AbstractConnectionManager, could anyone share me where
it is, Thanks !

      was (Author: xuhaihong):
    It seems that the reason is that the exception is kept by the ManagedConnectionFactory.doStart
method and is not propagated to the method invoker, so that the gbeaninstacestate always thougth
the the gbean is started successfully.
.....
public void doStart() throws Exception {
        ......        
        // The exception is occured at the line below, but this method's signature does not
contain any throws, so it kept the exception.
        connectionManagerContainer.doRecovery(managedConnectionFactory);        
    }

But I could find the source code for org.apache.geronimo.connector.outbound.AbstractConnectionManager,
could anyone share me where it is, 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
>
> 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.


Mime
View raw message