IMS94 commented on pull request #107:
URL: https://github.com/apache/oodt/pull/107#issuecomment-769559187
@yasithmilinda You can simply build the OODT distribution and, run `oodt
start`. Check if all the services (filemgr, resmgr and workflow manager) comes
up without an issue (you can use the status page to see if services are
running). Then, if all are running, you can check if the log files are created
under `${component_directory}/logs` folder (ex: `filemgr/logs`).
My only concern is, when running, say `file manager`, that shell script
passes in the `logging.properties` file which is for JUL. When we were using
JUL within the applications, this works fine. Now, when we have changed the
logging within applications to slf4j (log4j2), we are not providing a
`log4j2.xml` in that shell script (correct me if I'm wrong). This may cause the
logs to not be printed properly in the log files. However, I remember I did
some log4j2 migration sometime back, in which I added the log4j2.xml files and
used the `log4j2 jul adapter` to print JUL logs in log4j2 log outputs. It will
be great if you can double check. If `log4j2.xml` is there, then your changes
will work without any issue.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
