Hi Mirunalini, Are you sure that the catalina.sh that you execute is actually picking up from the one that you have downloaded? Do you have any tomcat installed from other sources, such as from the centos 7.3?
For a very long period of time, I have never seen Tomcat written as "jakarta-tomcat" in any of recent download versions (including version 7.0). It's been spun off from Apache Jakarta project long time ago. I suspect some of your configuration is actually picking up from the centos packaged version of tomcat. You can see whether there's a centos bundled tomcat installed by executing: sudo yum list | grep tomcat If it shows any tomcat, uninstall it using (I am assuming this is your development machine, not production machine): sudo yum remove <package-name> Regards, Daniel Baktiar On Tue, Dec 12, 2017 at 5:43 PM, mirunalini Chandrasekaran < miru3...@gmail.com> wrote: > Hi, > > This is how i guess tomcat starts, and also it uses the startup script with > catalina.sh file. > > ps -ef | grep tomcat > > root 1357 1 0 11:53 ? 00:00:08 > /usr/local/thirdparty/java/jdk/bin/java -classpath > :/usr/local/thirdparty/jakarta-tomcat/lib/javax.ws. > rs-api-2.0.jar:/usr/local/thirdparty/jakarta-tomca > /lib/jersey-client.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/jersey-common.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/hk2-api-2.3.0-b05.jar:/usr/local/thirdparty/ > jakarta-tomcat/lib/jersey-guava-2.10.1.jar:/usr/local/ > thirdparty/jakarta-tomcat/lib/javax-inject.jar:/usr/local/ > thirdparty/jakarta-tomcat/lib/hk2-locator-2.3.0-b05.jar:/ > usr/local/thirdparty/jakarta-tomcat/lib/hk2-utils-2.3.0- > b05.jar:/usr/local/thirdparty/jakarta-tomcat/lib/javax. > annotation-api-1.2.jar:/usr/local/thirdparty/jakarta- > tomcat/lib/catalina.jar:/usr/local/platform/jar/ > cucminventory-tcpserver.jar > com.cisco.cucminventory.server.MultiThreadedTCPServer > root 6115 5927 0 15:05 pts/0 00:00:00 grep --color=auto tomcat > root 27529 1 0 11:57 ? 00:00:00 /home/tomcat/tomcat -user > tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile > /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname > /home/tomcat/tomcat -outfile > /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 > -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/ > usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/ > thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/ > usr/lib:/usr/local/cm/lib::/usr/local/platform/lib > -Djavax.net.ssl.trustStore=/usr/local/platform/.security/ > tomcat/trust-certs/tomcat-trust.keystore > -Djavax.net.ssl.trustStorePassword= > -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/ > logs/diagnostic-info.jvm-crash.%p.tomcat.txt > -Dsun.zip.disableMemoryMapping=true > -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh > -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Dlog4j.configuration=file:/usr/local/thirdparty/jakarta- > tomcat/webapps/log4jinit/log4j.xml > -Xmx1824m -Xms256m -XX:MaxPermSize=448m > -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -cp > :/common/download:/usr/local/platform/application_locale/ > platform-api:/usr/local/platform/application_locale/cmplatform:/usr/local/ > platform/application_locale:/usr/local/cm/application_ > locale/cmservices:/usr/local/cm/application_locale/car:/ > usr/local/cm/application_locale/ccmadmin:/usr/local/cm/ > application_locale/ucmuser:/usr/local/cm/application_ > locale:/etc/opt/cisco/elm/server/resource:/usr/local/ > thirdparty/jakarta-tomcat/bin/bootstrap.jar::/usr/local/ > thirdparty/jakarta-tomcat/bin/tomcat-juli.jar > -Djava.security.policy==/usr/local/thirdparty/jakarta- > tomcat/conf/catalina.policy > -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat > -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat > -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp > org.apache.catalina.startup.Bootstrap start > tomcat 27530 27529 6 11:57 ? 00:12:50 /home/tomcat/tomcat -user > tomcat -home /usr/local/thirdparty/java/j2sdk -pidfile > /usr/local/thirdparty/jakarta-tomcat/conf/tomcat.pid -procname > /home/tomcat/tomcat -outfile > /usr/local/thirdparty/jakarta-tomcat/logs/catalina.out -errfile &1 > -Djava.library.path=/usr/local/cm/lib:/usr/local/lib:/ > usr/local/thirdparty/java/j2sdk/jre/lib/i386:/usr/local/ > thirdparty/java/j2sdk/jre/lib/i386/server:/usr/lib/pgsql:/ > usr/lib:/usr/local/cm/lib::/usr/local/platform/lib > -Djavax.net.ssl.trustStore=/usr/local/platform/.security/ > tomcat/trust-certs/tomcat-trust.keystore > -Djavax.net.ssl.trustStorePassword= > -XX:ErrorFile=/usr/local/thirdparty/jakarta-tomcat/ > logs/diagnostic-info.jvm-crash.%p.tomcat.txt > -Dsun.zip.disableMemoryMapping=true > -XX:OnOutOfMemoryError=/tomcat_diagnostics.sh > -XX:OnError=/tomcat_diagnostics.sh -Djdk.tls.ephemeralDHKeySize=2048 > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > -Dlog4j.configuration=file:/usr/local/thirdparty/jakarta- > tomcat/webapps/log4jinit/log4j.xml > -Xmx1824m -Xms256m -XX:MaxPermSize=448m > -Djava.endorsed.dirs=/usr/local/thirdparty/jakarta-tomcat/endorsed -cp > :/common/download:/usr/local/platform/application_locale/ > platform-api:/usr/local/platform/application_locale/cmplatform:/usr/local/ > platform/application_locale:/usr/local/cm/application_ > locale/cmservices:/usr/local/cm/application_locale/car:/ > usr/local/cm/application_locale/ccmadmin:/usr/local/cm/ > application_locale/ucmuser:/usr/local/cm/application_ > locale:/etc/opt/cisco/elm/server/resource:/usr/local/ > thirdparty/jakarta-tomcat/bin/bootstrap.jar::/usr/local/ > thirdparty/jakarta-tomcat/bin/tomcat-juli.jar > -Djava.security.policy==/usr/local/thirdparty/jakarta- > tomcat/conf/catalina.policy > -Dcatalina.base=/usr/local/thirdparty/jakarta-tomcat > -Dcatalina.home=/usr/local/thirdparty/jakarta-tomcat > -Djava.io.tmpdir=/usr/local/thirdparty/jakarta-tomcat/temp > org.apache.catalina.startup.Bootstrap start > > Regards, > Mirunalini > > > On Fri, Dec 8, 2017 at 12:56 PM, Konstantin Kolinko < > knst.koli...@gmail.com> > wrote: > > > 2017-12-08 9:58 GMT+03:00 mirunalini Chandrasekaran <miru3...@gmail.com > >: > > > Hi All, > > > > > > I am using Tomcat 7.0.81 on centos 7.3 and using openjdk 1.7.0.141. > > Tomcat > > > was downloaded from http://tomcat.apache.org/ > > > > > > The problem I am seeing recently is manager*.log and localhost*.log > files > > > are not created. Instead, I see the messages that were to be written > into > > > manager.log are going into Catalina.out. catalina.out and > > > localhost_access.log continue to work like before. May I know how and > > from > > > where to start debugging this? > > > I have verified logging.properties, there is no issue with it. > > > > How do you start Tomcat? > > > > Overall, Tomcat uses the standard java.uti.logging API to perform its > > logging. The java.util.logging is configured via the following two > > system properties: > > > > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > > -Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties > > > > These two properties are set by catalina.sh wrapper script when it > > launches java process for Tomcat > > If those properties are missing, the default configuration of > > java.util.logging is to log everything to a > > java.util.logging.ConsoleHandler. > > > > The stdout and stderr of the java process are redirected to > > "catalina.out" file by catalina.sh script. It is not a proper log > > file. > > > > Best regards, > > Konstantin Kolinko > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: users-h...@tomcat.apache.org > > > > >
