[
https://issues.apache.org/jira/browse/OOZIE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116078#comment-14116078
]
Robert Kanter commented on OOZIE-1705:
--------------------------------------
{quote}When you have code that logs directly, yes line number and class name
are useful. But for oozie, all logging is done using XLog and the class name
and line numbers in oozie.log always point to XLog code. (Its bad, we should
fix it){quote}
I double-checked and you're right about the line numbers; those are always
wrong. The class name is correct though and I think we should keep that.
I tried running it but didn't see a gc.log anywhere. Are you sure that the
arguments are correct?
Also, when running any of the tools (oozie-setup.sh commands, ooziedb.sh, etc)
I get this error (though the script continues running and works anyway):
{noformat}
$ ooziedb.sh create -run
/Users/rkanter/dev/oozie/conf/oozie-env.sh: line 25: $CATALINA_OPTS -Xmx1024m
-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
-Xloggc:${oozie.log.dir}/gc.log: bad substitution
setting CATALINA_OPTS="$CATALINA_OPTS -Xmx1024m -verbose:gc
-XX:+PrintGCDetails -XX:+PrintGCTimeStamps -Xloggc:${oozie.log.dir}/gc.log"
Validate DB Connection
...
{noformat}
> Enable gc logs and print thread id in logs
> ------------------------------------------
>
> Key: OOZIE-1705
> URL: https://issues.apache.org/jira/browse/OOZIE-1705
> Project: Oozie
> Issue Type: Task
> Reporter: Shwetha G S
> Assignee: Shwetha G S
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-1705-v2.patch, OOZIE-1705.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
