Tomcat fails to write in exceptions.log even after using Pro

Can you set 777 permissions to the log file and try.

If it still doesn’t solve the problem, provide read and execute access to the directory in which the file contain:

Example: chmod o+x /home/user

> Please advice the current permission to the log is 644.

For whom? and who starts the tomcat. Unless it's the owner of the file, 644 is not enough, -rw- is needed.

if it's the owner of the file who starts the tomcat, then what java is running the tomcat? 32/64-bit ? and what is the version of Progress/OE + bitness.

> We have set the Progress workdir in startup.sh

-->  WRKDIR: /test/apps/dlcwrk

--> -rw-r--r-- 1 abc xyz 4840 Jun 30 11:24 /test/apps/tomcat/temp/exceptions.log

Are you sure you set the WRKDIR in the Tomcat startup? Those 2 folders are different.

> Progress:OpenEdge Release 10.2B04

32 or 64-bit ?

Guess/thing to try: put "-d64" into JAVA_OPTS into Tomcat's setenv.sh to see if it resolves the issue.

$WRKDIR = /test/apps/dlcwrk/ does not set the variable

WRKDIR = /test/apps/dlcwrk/ does

or rather

WRKDIR = /test/apps/dlcwrk ; export WRKDIR

just to be safe.

>>

Also there is no such "-d64" into JAVA_OPTS in setenv.sh.

Do you want us to add it explicitly ?

<<

First please fix setting the WRKDIR, and retest.

you can put echo $WRKDIR in the startup.sh to see if it's set properly

Once the variable is properly set and it still does not solve the problem, then please yes, add the "-d64" into JAVA_OPTS.

WRKDIR=/test/apps/dlcwrk ; export WRKDIR

to be absolutely precise, without the spaces

Hi Libor,

I put that by mistake,its already like you said so no issue there.

DLC=/${QADENV}/apps/dlc; export DLC

PATH=$DLC:$DLC/bin:$PATH; export PATH

WRKDIR=/${ENV}/apps/dlcwrk/; export WRKDIR

Regarding JAVA_OPTS

Currently I have:

JAVA_HOME=`ls -td /usr/java/jdk* 2>/dev/null | head -1`;export JAVA_HOME

CATALINA_PID=`dirname $0`/../temp/tomcat_pid;export CATALINA_PID

CATALINA_OPTS="-Djava.net.preferIPv4Stack=true -Xss128k -XX:MaxPermSize=256m -XX:+UseParallelGC -Djava.awt.headless=true -server -Xms1024m -Xmx1024m -Dfile.encoding=utf-8";export CATALINA_OPTS

OK. You said you have this in test environment as well? Maybe I can connect there remotely to test and see, instead of playing "ping pong" with updates. That possible ?

Well I can reproduce this now.

Hi Libor,

Currently, After discussion with R&D,we are going to do some customisation as from Progress,after raising a case regarding this issue and failure of the Progress KBase AIA fails to start with Tomcat JSE, its confirmed from their is bug and has been reported by many users.

***********************

Only my question is why tomcat user is failing to write in the exceptions.log?

Also we have two instances of same Tomcat.

*********************

Hi Libor,

I was just want to confirm that if a space before export will do any harm?

# Local procedures

env() {

       # Returns the test environment the script is ran in

       echo $(cd $(dirname ${0}) ; echo $(pwd) | awk -F "/" '{ print $2 }')

}

ENV=$(env);

# Then set and export your local variables:

DLC=/${ENV}/apps/dlc; export DLC

PATH=$DLC:$DLC/bin:$PATH; export PATH

WRKDIR=/${ENV}/apps/dlcwrk/; export WRKDIR

> its confirmed from their is bug ...

I am aware. I logged it myself :)

>  was just want to confirm that if a space before export will do any harm?

No, it won't.

Hi Libor,

The issue has been resolved for the time being.