Geronimo
  1. Geronimo
  2. GERONIMO-3878

Unable to deploy Postgres Datasource from console dialog "Database Pools" because of missing jar files in jar selection listbox.

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.1
    • Fix Version/s: None
    • Component/s: console
    • Security Level: public (Regular issues)
    • Labels:
      None
    • Environment:

      Windows XP Professional and Ubuntu

      Description

      Trying to deploy a datasource with console dialog "Database Pools".

      • Select link "Console Navigation/Services/Database Pools".
      • Select link "Using the geronimo database pool wizard".
      • Enter some database name like for instance "vesuv" and select as Database Type: "PostgreSQL XA" or "PostgreSQL local".
      • Click the Next button.
      • Now, on the page where you specify the properties of the database pool, the listbox where you can select the driver jar is empty. If you choose another database type (on the previous dialog page), the list is filled with all entries from repository. The same steps have been made with Geronimo 2.02. There the database could be deployed.

        Activity

        Hide
        David Jencks added a comment -

        You have to install the postgres jar yourself. I thought we had fairly clear indications of this. Could you suggest how we can make this clearer?

        Show
        David Jencks added a comment - You have to install the postgres jar yourself. I thought we had fairly clear indications of this. Could you suggest how we can make this clearer?
        Hide
        Ralf Baumhof added a comment -

        As i mentioned in my last sentence "If you choose another database type (on the previous dialog page), the list is filled with all entries from repository". And because i have OF COURSE installed the jdbc driver in the repository, you can see it like all the other jars in repository. This means, if you choose DB2 as database type, you get a lot of entries in the listbox. If you choose Postgres you see really NOTHING ("the listbox where you can select the driver jar is empty")!!!! I'am sorry that i did not mention that i installed the Postgres jar driver, because this seemed to be a clear precondition for me.

        Show
        Ralf Baumhof added a comment - As i mentioned in my last sentence "If you choose another database type (on the previous dialog page), the list is filled with all entries from repository". And because i have OF COURSE installed the jdbc driver in the repository, you can see it like all the other jars in repository. This means, if you choose DB2 as database type, you get a lot of entries in the listbox. If you choose Postgres you see really NOTHING ("the listbox where you can select the driver jar is empty")!!!! I'am sorry that i did not mention that i installed the Postgres jar driver, because this seemed to be a clear precondition for me.
        Hide
        David Jencks added a comment -

        I just tried with trunk and downloaded the postgres 8.1 jar using the wizard and it showed up in the list. The wizard did get seriously confused after the download about what it was trying to build but I started over and saw the jar. I saw postgres/postgres-8.1/404.jdbc3/jar

        Which jar did you download, how, and where is it in the geronimo repository?

        Show
        David Jencks added a comment - I just tried with trunk and downloaded the postgres 8.1 jar using the wizard and it showed up in the list. The wizard did get seriously confused after the download about what it was trying to build but I started over and saw the jar. I saw postgres/postgres-8.1/404.jdbc3/jar Which jar did you download, how, and where is it in the geronimo repository?
        Hide
        David Jencks added a comment -

        btw I opened GERONIMO-3883 about the wizard getting confused about which wrapper it's using.

        Show
        David Jencks added a comment - btw I opened GERONIMO-3883 about the wizard getting confused about which wrapper it's using.
        Hide
        Ralf Baumhof added a comment -

        Yes, that's right. It works if you donwload the driver directly. The dialog first does not work, if you try a test, it fails. But after this first failure, the dialog is ok. It always comes up with the corret postgres specific settings, and more over, the datasource is ok. The application works. But i'am still confused because of the following:

        • Why this strange behaviour - only for Postgres? With geronimo 2.0.2 you could download the driver separately, and then use the common libs dialog (now called repository) to deploy it. Then you will see it in the jars listbox. This still works - if you use another database type (like DB2).
        • This workaround is not suitable for a production system. In production we "NEVER" have a internet connection. People in the production system are used to get a jar, and then they deploy it using the dialoge. So, i could use the dialog of an other system with internet connection to create a plan and advice production to deploy the plan. But this will probably result in editing and changing the plan to the preferences of production systems. And this will result in errors.
        Show
        Ralf Baumhof added a comment - Yes, that's right. It works if you donwload the driver directly. The dialog first does not work, if you try a test, it fails. But after this first failure, the dialog is ok. It always comes up with the corret postgres specific settings, and more over, the datasource is ok. The application works. But i'am still confused because of the following: Why this strange behaviour - only for Postgres? With geronimo 2.0.2 you could download the driver separately, and then use the common libs dialog (now called repository) to deploy it. Then you will see it in the jars listbox. This still works - if you use another database type (like DB2). This workaround is not suitable for a production system. In production we "NEVER" have a internet connection. People in the production system are used to get a jar, and then they deploy it using the dialoge. So, i could use the dialog of an other system with internet connection to create a plan and advice production to deploy the plan. But this will probably result in editing and changing the plan to the preferences of production systems. And this will result in errors.
        Hide
        David Jencks added a comment -

        Yes, that's right. It works if you donwload the driver directly. The dialog first does not work, if you try a test, it fails. But after this first failure, the dialog is ok. It always comes up with the corret postgres specific settings, and more over, the datasource is ok. The application works. But i'am still confused because of the following:

        * Why this strange behaviour - only for Postgres? With geronimo 2.0.2 you could download the driver separately, and then use the common libs dialog (now called repository) to deploy it. Then you will see it in the jars listbox. This still works - if you use another database type (like DB2).

        I installed postgresql/postgresql/8.2-504.jdbc3/jar using the "repository" page and saw it in the wizard. I think I've been getting confused between "postgres" and "postgresql". I notice that my previous post embodied this confusion

        I think two things might help...

        1. a checkbox to show all jars
        2. a page or change to the repository page to copy a jar from a maven repo to the geronimo repo. (part of GERONIMO-3884)

        * This workaround is not suitable for a production system. In production we "NEVER" have a internet connection. People in the production system are used to get a jar, and then they deploy it using the dialoge. So, i could use the dialog of an other system with internet connection to create a plan and advice production to deploy the plan. But this will probably result in editing and changing the plan to the preferences of production systems. And this will result in errors.

        I'm not sure what you mean by a production system. In an even slightly controlled environment I'd expect that you would not use the admin console for anything, and instead would have a project-wide controlled maven repository for approved artifacts and build plugins and assemblies for your apps as described here:
        http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven

        Show
        David Jencks added a comment - Yes, that's right. It works if you donwload the driver directly. The dialog first does not work, if you try a test, it fails. But after this first failure, the dialog is ok. It always comes up with the corret postgres specific settings, and more over, the datasource is ok. The application works. But i'am still confused because of the following: * Why this strange behaviour - only for Postgres? With geronimo 2.0.2 you could download the driver separately, and then use the common libs dialog (now called repository) to deploy it. Then you will see it in the jars listbox. This still works - if you use another database type (like DB2). I installed postgresql/postgresql/8.2-504.jdbc3/jar using the "repository" page and saw it in the wizard. I think I've been getting confused between "postgres" and "postgresql". I notice that my previous post embodied this confusion I think two things might help... a checkbox to show all jars a page or change to the repository page to copy a jar from a maven repo to the geronimo repo. (part of GERONIMO-3884 ) * This workaround is not suitable for a production system. In production we "NEVER" have a internet connection. People in the production system are used to get a jar, and then they deploy it using the dialoge. So, i could use the dialog of an other system with internet connection to create a plan and advice production to deploy the plan. But this will probably result in editing and changing the plan to the preferences of production systems. And this will result in errors. I'm not sure what you mean by a production system. In an even slightly controlled environment I'd expect that you would not use the admin console for anything, and instead would have a project-wide controlled maven repository for approved artifacts and build plugins and assemblies for your apps as described here: http://cwiki.apache.org/confluence/display/GMOxDOC21/Constructing+a+special-purpose+server+using+maven
        Hide
        Ralf Baumhof added a comment -

        Ok, now we have got the things together. It works if:
        1.) The group id of the artifact must be "postgresql".
        2.) The file extension of the driver archive file must be .jar

        My file was a .zip archive file and the group id was DB (not postgresql). This does not matter in Geronimo 2.02. Thanks for your help. Perhaps you should mention this somewhere on the PostgreSQL specific datasource properties page.

        Show
        Ralf Baumhof added a comment - Ok, now we have got the things together. It works if: 1.) The group id of the artifact must be "postgresql". 2.) The file extension of the driver archive file must be .jar My file was a .zip archive file and the group id was DB (not postgresql). This does not matter in Geronimo 2.02. Thanks for your help. Perhaps you should mention this somewhere on the PostgreSQL specific datasource properties page.
        Hide
        Jonathan Chen added a comment -

        I was caught out by this, as I usually install the postgresql drivers with the group "org.postgresql.jdbc", and was surprised when no jars were presented. Thank goodness for Google.

        My preferred "fix" would be for a checkbox to show all available jars.

        Show
        Jonathan Chen added a comment - I was caught out by this, as I usually install the postgresql drivers with the group "org.postgresql.jdbc", and was surprised when no jars were presented. Thank goodness for Google. My preferred "fix" would be for a checkbox to show all available jars.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ralf Baumhof
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Time Tracking

              Estimated:
              Original Estimate - 120h
              120h
              Remaining:
              Remaining Estimate - 120h
              120h
              Logged:
              Time Spent - Not Specified
              Not Specified

                Development