Uploaded image for project: 'Pentaho Data Integration - Kettle'
  1. Pentaho Data Integration - Kettle
  2. PDI-8788

Instaview cannot open saved view, and analyzer seems to get into a non-recoverable state (RC2)

    Details

    • Type: Bug
    • Status: Closed
    • Severity: High
    • Resolution: Fixed
    • Affects Version/s: 4.4.0 GA (4.8.0 GA Suite Release)
    • Component/s: Instaview
    • Labels:
      None
    • Environment:
      OS X
    • Notice:
      When an issue is open, the "Fix Version/s" field conveys a target, not necessarily a commitment. When an issue is closed, the "Fix Version/s" field conveys the version that the issue was fixed in.

      Description

      Steps to reproduce (see attached clip):

      1. Create New -> Samples -> Apache Weblog
      2. OK ETL
      3. Drag together some view (I got Year, Month, Page hits)
      4. Exit and Save
      6. Open Existing View -> Error
      7. Exit

      Repeat from 1, and there will be a failure on step 3 with another exception (you can save a failed view still)

      1. insta.mov
        5.34 MB
        Slawomir Chodnicki
      1. reopen_view.jpg
        121 kB
      2. Screen Shot 2012-10-24 at 10.54.07 AM.png
        538 kB
      3. Screen Shot 2012-10-24 at 10.54.20 AM.png
        738 kB

        Activity

        Hide
        rfellows Rob Fellows added a comment -

        verified in CI, should be available in the 4.4-GA RC3 of PDI-EE

        Show
        rfellows Rob Fellows added a comment - verified in CI, should be available in the 4.4-GA RC3 of PDI-EE
        Hide
        rfellows Rob Fellows added a comment -

        This was the result of a combination of factors.

        First, we stop monetdb on Instaview project close and start monetdb when a new Instaview project is created or an existing one is opened up.
        Second, we recently started Pooling our monetdb connections in agile-bi for analyzer/mondrian. However, the configuration of the pool was such that it didn't do a validationCheck of the connections before handing them out. So, as one could imagine, when you walk through a project and get into analyzer the connection pool is created for the first time and all connections are good. as soon as you close that project, the monetdb service is stopped and that forces all connections in the pool to no longer function. Subsequent requests for connections from the connection pool would just blindly hand these invalid connection back out.

        The fix was to add a validationQuery to the PoolableConnectionFactory used as well as set the testOnBorrow flag of the GenericObjectPool. This in effect makes the connection pool "test" the connection it has before handing it out with the validationQuery (in this case it is simple "SELECT 1"). if it fails, it creates a new connection.

        Show
        rfellows Rob Fellows added a comment - This was the result of a combination of factors. First, we stop monetdb on Instaview project close and start monetdb when a new Instaview project is created or an existing one is opened up. Second, we recently started Pooling our monetdb connections in agile-bi for analyzer/mondrian. However, the configuration of the pool was such that it didn't do a validationCheck of the connections before handing them out. So, as one could imagine, when you walk through a project and get into analyzer the connection pool is created for the first time and all connections are good. as soon as you close that project, the monetdb service is stopped and that forces all connections in the pool to no longer function. Subsequent requests for connections from the connection pool would just blindly hand these invalid connection back out. The fix was to add a validationQuery to the PoolableConnectionFactory used as well as set the testOnBorrow flag of the GenericObjectPool. This in effect makes the connection pool "test" the connection it has before handing it out with the validationQuery (in this case it is simple "SELECT 1"). if it fails, it creates a new connection.
        Hide
        gdavid Golda Thomas added a comment - - edited

        Tested this issue using the PDI 4.4 installer from 10/25/2012.
        With the latest installer opening a report loads the report without any issues.
        No more non-recoverable state in RC3 build.
        This issue is resolved.Tested this in both windows 7 and ubuntu 12 64 bit

        Show
        gdavid Golda Thomas added a comment - - edited Tested this issue using the PDI 4.4 installer from 10/25/2012. With the latest installer opening a report loads the report without any issues. No more non-recoverable state in RC3 build. This issue is resolved.Tested this in both windows 7 and ubuntu 12 64 bit
        Hide
        gdavid Golda Thomas added a comment -

        Tested this issue in Windows 7 and UBuntu 12

        Show
        gdavid Golda Thomas added a comment - Tested this issue in Windows 7 and UBuntu 12

          People

          • Assignee:
            gdavid Golda Thomas
            Reporter:
            schodnicki Slawomir Chodnicki (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: