Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 482D611281 for ; Wed, 25 Jun 2014 18:58:26 +0000 (UTC) Received: (qmail 51862 invoked by uid 500); 25 Jun 2014 18:58:26 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 51829 invoked by uid 500); 25 Jun 2014 18:58:26 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 51595 invoked by uid 99); 25 Jun 2014 18:58:26 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2014 18:58:26 +0000 Date: Wed, 25 Jun 2014 18:58:26 +0000 (UTC) From: "Hayden Marchant (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-2944) Generated configuration files and scripts assume SUN as JVM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043919#comment-14043919 ] Hayden Marchant commented on ACCUMULO-2944: ------------------------------------------- Corey, frequently the default JAVA_HOME in the shell might not be set with the desired JVM since a number of different versions could be installed. I agree that it might be desirable to suggest the JVM installed on JAVA_HOME as a default selection if no other specific ones are selected. Should this be recorded as an enhancement in a separate JIRA? > Generated configuration files and scripts assume SUN as JVM > ----------------------------------------------------------- > > Key: ACCUMULO-2944 > URL: https://issues.apache.org/jira/browse/ACCUMULO-2944 > Project: Accumulo > Issue Type: Sub-task > Components: build > Affects Versions: 1.6.0 > Environment: IBM JVM > Reporter: Hayden Marchant > Assignee: Hayden Marchant > Fix For: 1.6.1, 1.7.0 > > Original Estimate: 72h > Remaining Estimate: 72h > > There are a few issues, detailed below: > a. The generated configuration files contain references to GC > params that are specific to Sun JVM. In accumulo-env.sh, the > ACCUMULO_TSERVER_OPTS contains -XX:NewSize and -XX:MaxNewSize , and also in ACCUMULO_GENERAL_OPTS, > -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 are used. > b. in bin/accumulo, get ClassNotFoundException due to > specification of JAXP Doc Builder: > -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl > . > The Sun implementation of Document Builder Factory does not exists > in IBM JDK, so a ClassNotFoundException is thrown on running accumulo > script > c. MiniAccumuloCluster - in the MiniAccumuloClusterImpl, > Sun-speciifc GC params are passed as params to the java process (similar > to section a. ) > Single proposal for solving all 3 issues: > Enhance bootstrap_config.sh with request to select Java vendor. > Selecting this will set correct values for GC params (they differ between > IBM and Sun), inclusion/ommision of JAXP setting. The > MiniAccumuloClusterImpl can read the same env variable that was set in > code for the GC Params, and use in the exec command. > For exampel, doing this will result in CMS settings existing for SUN JVM, but when using IBM JVM, the relevant GC parameter for IBM JVM will be used instead. In addition, the SUN JAXP implementation will be omitted on non-SUN JVM. > For now, I plan on having 4 options in new question > 1. Sun > 2. OpenJDK > 3. IBM > 4. Other -- This message was sent by Atlassian JIRA (v6.2#6252)