Hitachi Vantara Pentaho Community Forums
Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 29

Thread: jboss notes w/ 1.6 RC1

  1. #11


    If using hibernateManaged=true, need to add the following lines to the PENTAHO_SOLUTIONS/system/hibernate/hibernate-jboss-managed.xml file. Recommend adding to default solutions:

    <!-- property name="hibernate.cache.provider_class">org.hibernate.cache.EhCacheProvider</property -->
    <property name="hibernate.cache.use_second_level_cache">false</property>
    <property name="hibernate.cache.use_query_cache">false</property>

  2. #12


    To re-iterate the problems I run into on Jboss 4.0.5 -

    1) The default Jboss server libs use commons-httpclient 2.X

    2) By enabling the classloaders (java2ParentDelegation=false) in both jboss-app.xml and jboss-web.xml, work around the commons-httpclient problem, but introduces new problems.

    --linkage, supposedly fixed by removing Tidy.jar from classpath.

    As of build 813, it looks like the HibernateUtil/template problem related to dom4j seems to have magically gone away. However, I do not understand the impact of removing Tidy.jar from classpath (nor why it causes linkage problems).

    This is still based on FileSolutionRepo, so not sure if DBSolutionRepo will have different results.

    edit: This is with the jfreeReport and Mondrian system listeners disabled as still having problems with them.
    Last edited by dhartford; 09-05-2007 at 11:54 AM.

  3. #13


    Some of my problems have been related to dirty classpaths - I've just been updating from SVN for quite some time, and old libs were still in-place and being added to application.xml.

    See Thomas's response from the JfreeSystemListener thread:

    Quote Originally Posted by Taqua View Post
    The application.xml file is auto-generated from within ant. So ultimately it comes from the third-party/lib directory (which (I assume) get copied to the deployment directory, which then get used to generate that file).

    At least the version from the SVN repository is clean and does not contain the jfreereport-jars anymore. If you work with a SVN version, then such obsolete files are usually caused by manual changes done to a previous version. If you only use release versions, then it is up to you to make sure that there are no old files. (And for a project like pentaho, with its numerous dependencies, this can be a tough job.)
    Will update with more information once I have re-built and re-tested.

  4. #14


    Got everything working fine with file-based repository. Just had to set the hibernate cache on hibernateManaged=true to either false, or specify cache mechanism.

    Also, enabled classloader to work around the jboss having different commons-httpclient version.

    --good for filebased, but not db-based repo.

    However, with DB-based repo enabled running into the UItemplate/HibernateUtil/dom4j problems. Also, needed to set hibernate.autocommit=false to work around some type of problem with the hibernateManaged=true when using DB-based repo.

    EDIT: spoke prematurly - went to show someone the filebased repo version of 1.6, and low and behold, HibernateUtil problems. No changes other than swapping the repo in /system/pentaho.xml and restarting.
    Last edited by dhartford; 09-06-2007 at 03:15 PM.

  5. #15
    Join Date
    Oct 2006


    Can you try enabling classloader logging as described here?

  6. #16


    UCL log is 3mb zipped, 2.5mb rar (even with maximum compression) - is there a portion of it you wish to look at?

    Starting from the beginning, httpclient with jboss is still a problem on RC2.820.
    Attached Files Attached Files

  7. #17
    Join Date
    Oct 2006


    Have the DeploymentExceptions been fixed? For example:

    org.jboss.deployment.DeploymentException: url file:/lib/kettle-2.5.1a.jar could not be opened, does it exist?
    Also, have you updated dom4j.jar in pentaho.war at all?

  8. #18


    I pulled everything out of SVN as-is, from scratch. Above is the first error I came across (httpclients version conflicts as described earlier in the thread), and rather than trying to fix it myself and describe other problems, going one at a time until it gets fixed and then move to the next problem. Httpclients isn't fixed.

    Has anyone been able to deploy Pentaho 1.6 on Jboss 4.0.5.GA without any problems, or is it just me? And, to make it very clear: JBoss 4.0.5.GA, not 4.2.1

    If you can prove me wrong that it deploys on 4.0.5.GA fine, great!!

    Build 838 tested as well, same httpclient issue

    edit, error log:
    java.lang.NoSuchMethodError: org.apache.commons.httpclient.HttpConnectionManager.getParams()Lorg/apache/commons/httpclient/params/HttpConnectionManagerParams;

    problem identified as Jboss uses an older version of commons-httpclient within the /server/<default>/lib. The EAR contains the newer version, but is not propertly class-loaded. Potential solution in using jboss-app.xml class-loading feature as detailed previously in this thread.
    Last edited by dhartford; 09-26-2007 at 08:58 AM.

  9. #19


    This will be the 19th post in the thread.

    I have attempted to give as much information in as detailed as feasible regarding the usecase of testing 1.6 RC on the Jboss 4.0.5 platform.

    Please, Pentaho, try it yourself. Seeing it in action will speak many more volumes than thread-post after thread-post.

    EAR deployment on a standard, unmodified, non-portal, jboss 4.0.5.GA platform.

    [[edit: FYI, if you fix httpclients with something like jboss-app.xml, the dom4j problem -seems- to have been fixed with file-based repo]]
    Last edited by dhartford; 09-26-2007 at 09:38 AM.

  10. #20
    Join Date
    Jul 2007


    Damn, I just got this error myself! But I could swear I got this working before. I'll make a few tests and get back here
    Pedro Alves
    Meet us on ##pentaho, a FreeNode irc channel

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.