This is an automated email from the ASF dual-hosted git repository.

rlevas pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/ambari.git


The following commit(s) were added to refs/heads/trunk by this push:
     new 6482518  add com.sun.jndi.ldap.connect.pool.* settings to 
AMBARI_JVM_ARGS
6482518 is described below

commit 6482518c1a204f1d6f06b760a29a546bca40447e
Author: David F. Quiroga <[email protected]>
AuthorDate: Mon May 28 22:02:16 2018 -0700

    add com.sun.jndi.ldap.connect.pool.* settings to AMBARI_JVM_ARGS
---
 ambari-server/conf/unix/ambari-env.sh | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ambari-server/conf/unix/ambari-env.sh 
b/ambari-server/conf/unix/ambari-env.sh
index 7ee2dc5..6371abb 100644
--- a/ambari-server/conf/unix/ambari-env.sh
+++ b/ambari-server/conf/unix/ambari-env.sh
@@ -15,7 +15,7 @@
 
 
 AMBARI_PASSHPHRASE="DEV"
-export AMBARI_JVM_ARGS="$AMBARI_JVM_ARGS -Xms512m -Xmx2048m 
-XX:MaxPermSize=128m 
-Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf
 -Djava.security.krb5.conf=/etc/krb5.conf 
-Djavax.security.auth.useSubjectCredsOnly=false"
+export AMBARI_JVM_ARGS="$AMBARI_JVM_ARGS -Xms512m -Xmx2048m 
-XX:MaxPermSize=128m 
-Djava.security.auth.login.config=$ROOT/etc/ambari-server/conf/krb5JAASLogin.conf
 -Djava.security.krb5.conf=/etc/krb5.conf 
-Djavax.security.auth.useSubjectCredsOnly=false 
-Dcom.sun.jndi.ldap.connect.pool.protocol=\"plain ssl\" 
-Dcom.sun.jndi.ldap.connect.pool.maxsize=20 
-Dcom.sun.jndi.ldap.connect.pool.timeout=300000"
 export PATH=$PATH:$ROOT/var/lib/ambari-server
 export PYTHONPATH=$ROOT/usr/lib/ambari-server/lib:$PYTHONPATH
 
@@ -23,4 +23,4 @@ export PYTHONPATH=$ROOT/usr/lib/ambari-server/lib:$PYTHONPATH
 # export PYTHON=/usr/bin/python2
 
 # to add additional directory or jar to server classpath use SERVER_CLASSPATH 
variable
-# export SERVER_CLASSPATH=/etc/hadoop/conf/secure
\ No newline at end of file
+# export SERVER_CLASSPATH=/etc/hadoop/conf/secure

-- 
To stop receiving notification emails like this one, please contact
[email protected].

Reply via email to