Hitachi Vantara Pentaho Community Forums
Results 1 to 6 of 6

Thread: [Mondrian] DynamicDatasourcesXmlaServlet

  1. #1
    Patrick Leckey Guest

    Default [Mondrian] DynamicDatasourcesXmlaServlet

    Hi,

    We're working with the latest 3.2-SNAPSHOT in a testing environment and noticed that the DynamicDatasourcesXmlaServlet no longer works, while the one in 3.2.1.13885 did.

    Delving into the source, a lot has changed in this area. Background scheduling the updates so it doesn't use up time on each request - tres cool. Hugely useful for us.

    However, I noticed in both DynamicContentFinder and FileRepository, where the scheduled executions are setup, both thread pools are being initialized with a pool size of 0 - so the background threads never actually get executed, and thus the datasource never gets checked for changes.

    In our testing environment I set both thread pools to initialize the pool size to 1 instead, and now everything seems to work beautifully.

    I'm just curious if this functionality was disabled for a reason I haven't hit yet, or if this was merely an oversight?

    Testing environment is:
    - CentOS 5.6
    - Tomcat 5.5.23
    - OpenJDK 1.6_21

    Pat
    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  2. #2
    Julian Hyde Guest

    Default Re: [Mondrian] DynamicDatasourcesXmlaServlet

    An oversight. (We're human too!)

    Please contribute your fix. And if you contribute a test case, we can keep
    it working in the future...

    Julian

    > -----Original Message-----
    > From: mondrian-bounces (AT) pentaho (DOT) org
    > [mailto:mondrian-bounces (AT) pentaho (DOT) org] On Behalf Of Patrick Leckey
    > Sent: Friday, July 15, 2011 12:10 PM
    > To: Mondrian developer mailing list
    > Subject: [Mondrian] DynamicDatasourcesXmlaServlet
    >
    > Hi,
    >
    > We're working with the latest 3.2-SNAPSHOT in a testing
    > environment and noticed that the
    > DynamicDatasourcesXmlaServlet no longer works, while the one
    > in 3.2.1.13885 did.
    >
    > Delving into the source, a lot has changed in this area.
    > Background scheduling the updates so it doesn't use up time
    > on each request - tres cool. Hugely useful for us.
    >
    > However, I noticed in both DynamicContentFinder and
    > FileRepository, where the scheduled executions are setup,
    > both thread pools are being initialized with a pool size of 0
    > - so the background threads never actually get executed, and
    > thus the datasource never gets checked for changes.
    >
    > In our testing environment I set both thread pools to
    > initialize the pool size to 1 instead, and now everything
    > seems to work beautifully.
    >
    > I'm just curious if this functionality was disabled for a
    > reason I haven't hit yet, or if this was merely an oversight?
    >
    > Testing environment is:
    > - CentOS 5.6
    > - Tomcat 5.5.23
    > - OpenJDK 1.6_21
    >
    > Pat
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  3. #3
    Luc Boudreau Guest

    Default Re: [Mondrian] DynamicDatasourcesXmlaServlet

    Patrick,

    Thanks for reporting this. I have fixed the issue and it will be resolved as
    of change 14462. It will be included in our next release, Mondrian 3.3.0.

    As a side note, the 3.2-SNAPSHOT builds are from a dead branch that we do
    not maintain nor test anymore. There might be some weird stuff in there. I
    suggest switching to either 3.3-SNAPSHOT or stick to 3.2.1.13885 to prevent
    any problems.

    Cheers!

    Luc

    On Fri, Jul 15, 2011 at 7:15 PM, Julian Hyde <jhyde (AT) pentaho (DOT) com> wrote:

    > An oversight. (We're human too!)
    >
    > Please contribute your fix. And if you contribute a test case, we can keep
    > it working in the future...
    >
    > Julian
    >
    > > -----Original Message-----
    > > From: mondrian-bounces (AT) pentaho (DOT) org
    > > [mailto:mondrian-bounces (AT) pentaho (DOT) org] On Behalf Of Patrick Leckey
    > > Sent: Friday, July 15, 2011 12:10 PM
    > > To: Mondrian developer mailing list
    > > Subject: [Mondrian] DynamicDatasourcesXmlaServlet
    > >
    > > Hi,
    > >
    > > We're working with the latest 3.2-SNAPSHOT in a testing
    > > environment and noticed that the
    > > DynamicDatasourcesXmlaServlet no longer works, while the one
    > > in 3.2.1.13885 did.
    > >
    > > Delving into the source, a lot has changed in this area.
    > > Background scheduling the updates so it doesn't use up time
    > > on each request - tres cool. Hugely useful for us.
    > >
    > > However, I noticed in both DynamicContentFinder and
    > > FileRepository, where the scheduled executions are setup,
    > > both thread pools are being initialized with a pool size of 0
    > > - so the background threads never actually get executed, and
    > > thus the datasource never gets checked for changes.
    > >
    > > In our testing environment I set both thread pools to
    > > initialize the pool size to 1 instead, and now everything
    > > seems to work beautifully.
    > >
    > > I'm just curious if this functionality was disabled for a
    > > reason I haven't hit yet, or if this was merely an oversight?
    > >
    > > Testing environment is:
    > > - CentOS 5.6
    > > - Tomcat 5.5.23
    > > - OpenJDK 1.6_21
    > >
    > > Pat
    > > _______________________________________________
    > > Mondrian mailing list
    > > Mondrian (AT) pentaho (DOT) org
    > > http://lists.pentaho.org/mailman/listinfo/mondrian
    > >

    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  4. #4
    Patrick Leckey Guest

    Default Re: [Mondrian] DynamicDatasourcesXmlaServlet

    Luc & Julian,

    Thanks, I'll update our testing environment to 3.3-SNAPSHOT. We can't use 3.2.1.13885 as it has a problem with some NON EMPTY queries (IIRC, MONDRIAN-942 but that's just off the top of my head) which seems to have been fixed in the 3.2-SNAPSHOT. We're rolling out 1.0 in early August, and that was a show-stopper for us, so we're playing with all the dev builds to see which is the best to go to production with.

    So far 4.0.0.13695 seems to be the lead horse, and the same change fixes the DynamicDatasourcesXmlaServlet in that build too.

    Other than the fact that's not an officially stable release, and assuming we're willing to take our chances, any reason we shouldn't use that build over the current 3.3 builds?

    Thanks,
    Pat

    On 2011-07-16, at 10:26 AM, Luc Boudreau wrote:

    >
    > Patrick,
    >
    > Thanks for reporting this. I have fixed the issue and it will be resolved as of change 14462. It will be included in our next release, Mondrian 3.3.0.
    >
    > As a side note, the 3.2-SNAPSHOT builds are from a dead branch that we do not maintain nor test anymore. There might be some weird stuff in there. I suggest switching to either 3.3-SNAPSHOT or stick to 3.2.1.13885 to prevent any problems.
    >
    > Cheers!
    >
    > Luc
    >
    > On Fri, Jul 15, 2011 at 7:15 PM, Julian Hyde <jhyde (AT) pentaho (DOT) com> wrote:
    > An oversight. (We're human too!)
    >
    > Please contribute your fix. And if you contribute a test case, we can keep
    > it working in the future...
    >
    > Julian
    >
    > > -----Original Message-----
    > > From: mondrian-bounces (AT) pentaho (DOT) org
    > > [mailto:mondrian-bounces (AT) pentaho (DOT) org] On Behalf Of Patrick Leckey
    > > Sent: Friday, July 15, 2011 12:10 PM
    > > To: Mondrian developer mailing list
    > > Subject: [Mondrian] DynamicDatasourcesXmlaServlet
    > >
    > > Hi,
    > >
    > > We're working with the latest 3.2-SNAPSHOT in a testing
    > > environment and noticed that the
    > > DynamicDatasourcesXmlaServlet no longer works, while the one
    > > in 3.2.1.13885 did.
    > >
    > > Delving into the source, a lot has changed in this area.
    > > Background scheduling the updates so it doesn't use up time
    > > on each request - tres cool. Hugely useful for us.
    > >
    > > However, I noticed in both DynamicContentFinder and
    > > FileRepository, where the scheduled executions are setup,
    > > both thread pools are being initialized with a pool size of 0
    > > - so the background threads never actually get executed, and
    > > thus the datasource never gets checked for changes.
    > >
    > > In our testing environment I set both thread pools to
    > > initialize the pool size to 1 instead, and now everything
    > > seems to work beautifully.
    > >
    > > I'm just curious if this functionality was disabled for a
    > > reason I haven't hit yet, or if this was merely an oversight?
    > >
    > > Testing environment is:
    > > - CentOS 5.6
    > > - Tomcat 5.5.23
    > > - OpenJDK 1.6_21
    > >
    > > Pat
    > > _______________________________________________
    > > Mondrian mailing list
    > > Mondrian (AT) pentaho (DOT) org
    > > http://lists.pentaho.org/mailman/listinfo/mondrian
    > >

    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian



    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  5. #5
    Luc Boudreau Guest

    Default Re: [Mondrian] DynamicDatasourcesXmlaServlet

    Patrick,

    The 4.0.X branch underwent major refactoring and is likely to have some
    nasty hidden bugs. It also introduces a new schema grammar (but upgrades
    pre-4.0 schemas in the background). Julian might know better than me the
    state of the 4.0 branch.

    Luc



    On Mon, Jul 18, 2011 at 10:34 AM, Patrick Leckey <patl (AT) seewind (DOT) com> wrote:

    > Luc & Julian,
    >
    > Thanks, I'll update our testing environment to 3.3-SNAPSHOT. We can't use
    > 3.2.1.13885 as it has a problem with some NON EMPTY queries (IIRC,
    > MONDRIAN-942 but that's just off the top of my head) which seems to have
    > been fixed in the 3.2-SNAPSHOT. We're rolling out 1.0 in early August, and
    > that was a show-stopper for us, so we're playing with all the dev builds to
    > see which is the best to go to production with.
    >
    > So far 4.0.0.13695 seems to be the lead horse, and the same change fixes
    > the DynamicDatasourcesXmlaServlet in that build too.
    >
    > Other than the fact that's not an officially stable release, and assuming
    > we're willing to take our chances, any reason we shouldn't use that build
    > over the current 3.3 builds?
    >
    > Thanks,
    > Pat
    >
    > On 2011-07-16, at 10:26 AM, Luc Boudreau wrote:
    >
    >
    > Patrick,
    >
    > Thanks for reporting this. I have fixed the issue and it will be resolved
    > as of change 14462. It will be included in our next release, Mondrian 3.3.0.
    >
    > As a side note, the 3.2-SNAPSHOT builds are from a dead branch that we do
    > not maintain nor test anymore. There might be some weird stuff in there. I
    > suggest switching to either 3.3-SNAPSHOT or stick to 3.2.1.13885 to prevent
    > any problems.
    >
    > Cheers!
    >
    > Luc
    >
    > On Fri, Jul 15, 2011 at 7:15 PM, Julian Hyde <jhyde (AT) pentaho (DOT) com> wrote:
    >
    >> An oversight. (We're human too!)
    >>
    >> Please contribute your fix. And if you contribute a test case, we can keep
    >> it working in the future...
    >>
    >> Julian
    >>
    >> > -----Original Message-----
    >> > From: mondrian-bounces (AT) pentaho (DOT) org
    >> > [mailto:mondrian-bounces (AT) pentaho (DOT) org] On Behalf Of Patrick Leckey
    >> > Sent: Friday, July 15, 2011 12:10 PM
    >> > To: Mondrian developer mailing list
    >> > Subject: [Mondrian] DynamicDatasourcesXmlaServlet
    >> >
    >> > Hi,
    >> >
    >> > We're working with the latest 3.2-SNAPSHOT in a testing
    >> > environment and noticed that the
    >> > DynamicDatasourcesXmlaServlet no longer works, while the one
    >> > in 3.2.1.13885 did.
    >> >
    >> > Delving into the source, a lot has changed in this area.
    >> > Background scheduling the updates so it doesn't use up time
    >> > on each request - tres cool. Hugely useful for us.
    >> >
    >> > However, I noticed in both DynamicContentFinder and
    >> > FileRepository, where the scheduled executions are setup,
    >> > both thread pools are being initialized with a pool size of 0
    >> > - so the background threads never actually get executed, and
    >> > thus the datasource never gets checked for changes.
    >> >
    >> > In our testing environment I set both thread pools to
    >> > initialize the pool size to 1 instead, and now everything
    >> > seems to work beautifully.
    >> >
    >> > I'm just curious if this functionality was disabled for a
    >> > reason I haven't hit yet, or if this was merely an oversight?
    >> >
    >> > Testing environment is:
    >> > - CentOS 5.6
    >> > - Tomcat 5.5.23
    >> > - OpenJDK 1.6_21
    >> >
    >> > Pat
    >> > _______________________________________________
    >> > Mondrian mailing list
    >> > Mondrian (AT) pentaho (DOT) org
    >> > http://lists.pentaho.org/mailman/listinfo/mondrian
    >> >

    >>
    >> _______________________________________________
    >> Mondrian mailing list
    >> Mondrian (AT) pentaho (DOT) org
    >> http://lists.pentaho.org/mailman/listinfo/mondrian
    >>

    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >
    >
    >
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >
    >


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

  6. #6
    Julian Hyde Guest

    Default Re: [Mondrian] DynamicDatasourcesXmlaServlet

    The 4.0.x branch (actually called //open/mondrian-release/lagunitas in
    perforce) builds but that is about it. At least 50% of the tests fail, and
    it does not have backwards compatibility with mondrian-3.2 schemas.

    In short, it is pre-alpha, and you shouldn't touch it unless you are a
    hardcore committer.


    _____

    From: mondrian-bounces (AT) pentaho (DOT) org [mailto:mondrian-bounces (AT) pentaho (DOT) org] On
    Behalf Of Luc Boudreau
    Sent: Monday, July 18, 2011 7:43 AM
    To: Mondrian developer mailing list
    Subject: Re: [Mondrian] DynamicDatasourcesXmlaServlet


    Patrick,

    The 4.0.X branch underwent major refactoring and is likely to have some
    nasty hidden bugs. It also introduces a new schema grammar (but upgrades
    pre-4.0 schemas in the background). Julian might know better than me the
    state of the 4.0 branch.

    Luc




    On Mon, Jul 18, 2011 at 10:34 AM, Patrick Leckey <patl (AT) seewind (DOT) com> wrote:


    Luc & Julian,

    Thanks, I'll update our testing environment to 3.3-SNAPSHOT. We can't use
    3.2.1.13885 as it has a problem with some NON EMPTY queries (IIRC,
    MONDRIAN-942 but that's just off the top of my head) which seems to have
    been fixed in the 3.2-SNAPSHOT. We're rolling out 1.0 in early August, and
    that was a show-stopper for us, so we're playing with all the dev builds to
    see which is the best to go to production with.

    So far 4.0.0.13695 seems to be the lead horse, and the same change fixes the
    DynamicDatasourcesXmlaServlet in that build too.

    Other than the fact that's not an officially stable release, and assuming
    we're willing to take our chances, any reason we shouldn't use that build
    over the current 3.3 builds?

    Thanks,
    Pat

    On 2011-07-16, at 10:26 AM, Luc Boudreau wrote:



    Patrick,

    Thanks for reporting this. I have fixed the issue and it will be resolved as
    of change 14462. It will be included in our next release, Mondrian 3.3.0.

    As a side note, the 3.2-SNAPSHOT builds are from a dead branch that we do
    not maintain nor test anymore. There might be some weird stuff in there. I
    suggest switching to either 3.3-SNAPSHOT or stick to 3.2.1.13885 to prevent
    any problems.

    Cheers!

    Luc


    On Fri, Jul 15, 2011 at 7:15 PM, Julian Hyde <jhyde (AT) pentaho (DOT) com> wrote:


    An oversight. (We're human too!)

    Please contribute your fix. And if you contribute a test case, we can keep
    it working in the future...

    Julian

    > -----Original Message-----
    > From: mondrian-bounces (AT) pentaho (DOT) org
    > [mailto:mondrian-bounces (AT) pentaho (DOT) org] On Behalf Of Patrick Leckey
    > Sent: Friday, July 15, 2011 12:10 PM
    > To: Mondrian developer mailing list
    > Subject: [Mondrian] DynamicDatasourcesXmlaServlet


    >
    > Hi,
    >
    > We're working with the latest 3.2-SNAPSHOT in a testing
    > environment and noticed that the
    > DynamicDatasourcesXmlaServlet no longer works, while the one
    > in 3.2.1.13885 did.
    >
    > Delving into the source, a lot has changed in this area.
    > Background scheduling the updates so it doesn't use up time
    > on each request - tres cool. Hugely useful for us.
    >
    > However, I noticed in both DynamicContentFinder and
    > FileRepository, where the scheduled executions are setup,
    > both thread pools are being initialized with a pool size of 0
    > - so the background threads never actually get executed, and
    > thus the datasource never gets checked for changes.
    >
    > In our testing environment I set both thread pools to
    > initialize the pool size to 1 instead, and now everything
    > seems to work beautifully.
    >
    > I'm just curious if this functionality was disabled for a
    > reason I haven't hit yet, or if this was merely an oversight?
    >
    > Testing environment is:
    > - CentOS 5.6
    > - Tomcat 5.5.23
    > - OpenJDK 1.6_21
    >
    > Pat
    > _______________________________________________
    > Mondrian mailing list
    > Mondrian (AT) pentaho (DOT) org
    > http://lists.pentaho.org/mailman/listinfo/mondrian
    >


    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian



    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian




    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian





    _______________________________________________
    Mondrian mailing list
    Mondrian (AT) pentaho (DOT) org
    http://lists.pentaho.org/mailman/listinfo/mondrian

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.