INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the : /usr/jdk/instances/jdk1.7.0/jre/lib/ġ0:45:43 AM init INFO: Command line argument: -Djava.io.tmpdir=/application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57/tempġ0:45:42 AM .AprLifecycleListener lifecycleEvent INFO: Command line argument: =/application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57 INFO: Command line argument: -Dcatalina.base=/application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57 INFO: Command line argument: =/application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57/endorsed INFO: Command line argument: =/usr/jdk/instances/jdk1.7.0/jre/lib/ INFO: Command line argument: .file=/application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57/conf/logging.properties
INFO: CATALINA_HOME: /application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57 INFO: CATALINA_BASE: /application/paragnq2a/parsit4/users/jyotir/staging/apache-tomcat-7.0.57 INFO: JAVA_HOME: /usr/jdk/instances/jdk1.7.0/jre INFO: Server version: Apache Tomcat/7.0.57 I have given below the stack trace from the tomcat startup logs:ġ0:45:42 AM .VersionLoggerListener log The OS is Sun Solaris and the JDK 1.7 installer I have used is 'jdk-7u60-ea-bin-b15-solaris-sparc-17_apr_'. If I simply change the JAVA_HOME to any of my JDK 1.6 installation, tomcat starts up smoothly as expected. sessionIdGeneratorBase.createRandom=Creation of SecureRandom instance for session ID generation using milliseconds.I am facing a strange issue where the tomcat version 7.0.57 is not starting up with JDK version 1.7. Result.getAlgorithm(), Long.valueOf(t2 - t1))) Īnd the human readable English text comes from here: Log.warn(sm.getString("sessionIdGeneratorBase.createRandom", Bug 61180 - Change log level of sessionIdGeneratorBase.createRandom to warn rather than info.The motivation for that change was this bug report here: This log line gets triggered when generation takes longer than a tenth of a second (100 miliseconds) But it's some background info, in case you're wondering where this log line comes from.
Tomcat 4821 4.7 13.9 2626888 263396 ? Ssl 22:31 0:23 /usr/lib/jvm/jre/bin/java -DJENKINS_HOME=/opt/jenkins/ -Xmx512m 4Stack=true 4Addresses=true =/etc/tomcat/fastersecurerandom.properties -classpath /usr/share/tomcat/bin/bootstrap.jar:/usr/share/tomcat/bin/tomcat-juli.jar:/usr/share/java/commons-daemon.jar -Dcatalina.base=/usr/share/tomcat =/usr/share/tomcat = -Djava.io.tmpdir=/var/cache/tomcat/temp .file=/usr/share/tomcat/conf/logging.properties = .Bootstrap start The best way to debug if they are taking affect is is to check the command running like this: $ ps aux | grep java On different versions/flavours you may find variations on where is best to set the environment variables for tomcat. Poor old confused tomcat 7 wouldn't start as per a warning in /var/log/messages
Here are some specific instructions to adjust just tomcat as per Henry's answerĬreate /etc/tomcat/fastersecurerandom.properties securerandom.source=file:/dev/urandomĮdit JAVA_OPTS inside /etc/tomcat/nf JAVA_OPTS="=/etc/tomcat/fastersecurerandom.properties"įYI I found I could not set multiple JAVA_OPTS with JAVA_OPTS="$JAVA_OPTS.
0 kommentar(er)
