This content has been marked as final. Show 3 replies
Searched in My Oracle Support and found the below details:
This issue has been fixed in the future release from the unpublished Bug 12426752
Workaround is to set logger to SEVERE level. You can do this by running following command from the WLST commandline:
Now I am able to filter the stack trace from entering into the log file.