Skip to Content
avatar image
Former Member

Portal not writing to Default Trace

SCN,

After adding a comment to an active default trace file, Portal stopped writing to it (added the comment to identify when a testing window began).

This system has one java AS with a single active node.  The trace files were configured to only log errors, but was increased to log level debug after realizing the traces weren't growing (ie no new entries despite executing tasks I know throw errors to the trace).  Still nothing...  Lastly, viewing the trace is consistent with entries in the NWA log viewer, so it's doubtful that the errors are being written elsewhere.

Any ideas?  I appreciate your help.

Thanks,

Sawyer

PS: Portal NW7.3ehp1 with SP12

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Sep 10, 2014 at 07:27 PM

    not able to follow u.....

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 10, 2014 at 01:16 PM

    Hi Jun, Not sure if I provided too much troubleshooting detail... Anyway, I added a comment to the active default trace file on the Portal AS (RHEL, NW 731).  After which, the default trace was not updated despite me knowingly generating errors.

    Ultimately, a system bounce resolved the issue...and after reproducing the error, it was written to the default trace.

    Add comment
    10|10000 characters needed characters exceeded