You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "viola.lu (JIRA)" <ji...@apache.org> on 2008/10/24 05:05:44 UTC
[jira] Created: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
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.
[jira] Updated: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ 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
Try to provide a patch for this JIRA.
Two modification are made :
1. Catch all the exception/Error in the portlet, for if the NoClassDefError is threw, an tomcat error page will show to the end user.
2. Stop the configuration while its sub-gbeans failed to start.
Please help to review it, and thanks for any comment !
> 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.
[jira] Updated: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated GERONIMO-4377:
---------------------------
Attachment: Geronimo-4377-11-17.patch
The file is recreated from the root folder. The console-testsuite has been run on the patch, and all passed.
Could anyone help to review it, 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-11-17.patch, 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.
[jira] Issue Comment Edited: (GERONIMO-4377) Fail to indicate
datasource create unsuccessfully in admin console "database pool" porlet
when choosing wrong database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ 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 not 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):
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 !
> 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.
[jira] Closed: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-4377.
----------------------------------
Resolution: Fixed
Rev718343 in branches/2.1 (2.1.4-SNAPSHOT)
Rev718344 in trunk (2.2-SNAPSHOT)
Thanks Ivan for the patch.
> 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
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4377-11-17.patch, 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.
[jira] Updated: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4377) Fail to indicate datasource
create unsuccessfully in admin console "database pool" porlet when
choosing wrong database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646167#action_12646167 ]
Ivan commented on GERONIMO-4377:
--------------------------------
Please ignore my comments below.
After checking with the reporter, I found the issue is that while we list the RAR modules in the portlets, we only check that whether the configuration gbean is running and list their states.
Although one of the sub-gbean is occurpted, for it will not affect the configuration gbean.
My suggestion is that we should also stop the Configuration GBean while its sub-gbean failed.
Please help to give any comment, 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.
[jira] Commented: (GERONIMO-4377) Fail to indicate datasource
create unsuccessfully in admin console "database pool" porlet when
choosing wrong database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646078#action_12646078 ]
Ivan commented on GERONIMO-4377:
--------------------------------
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.
[jira] Updated: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-4377:
-----------------------------------
Patch Info: [Patch Available]
Fix Version/s: 2.2
2.1.4
Assignee: Donald Woods
> 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
> Assignee: Donald Woods
> Priority: Minor
> Fix For: 2.1.4, 2.2
>
> Attachments: Geronimo-4377-11-17.patch, 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.
[jira] Issue Comment Edited: (GERONIMO-4377) Fail to indicate
datasource create unsuccessfully in admin console "database pool" porlet
when choosing wrong database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Issue Comment Edited: (GERONIMO-4377) Fail to indicate
datasource create unsuccessfully in admin console "database pool" porlet
when choosing wrong database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646167#action_12646167 ]
xuhaihong edited comment on GERONIMO-4377 at 11/9/08 8:58 PM:
---------------------------------------------------------
Please ignore my comments above.
After checking with the reporter, I found the issue is that while we list the RAR modules in the portlets, we only check that whether the configuration gbean is running and list their states.
Although one of the sub-gbean is occurpted, for it will not affect the configuration gbean.
My suggestion is that we should also stop the Configuration GBean while its sub-gbean failed.
Please help to give any comment, thanks !
was (Author: xuhaihong):
Please ignore my comments below.
After checking with the reporter, I found the issue is that while we list the RAR modules in the portlets, we only check that whether the configuration gbean is running and list their states.
Although one of the sub-gbean is occurpted, for it will not affect the configuration gbean.
My suggestion is that we should also stop the Configuration GBean while its sub-gbean failed.
Please help to give any comment, 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.
[jira] Updated: (GERONIMO-4377) Fail to indicate datasource create
unsuccessfully in admin console "database pool" porlet when choosing wrong
database driver
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated GERONIMO-4377:
---------------------------
Attachment: (was: Geronimo-4377.patch)
> 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.