(DP) Support Tip: How to Debug AppServer
In order to determine the root cause of many issues like schedules issues, authentication issues, etc. Debugs of the Application Server are required. These logs are written to
You can follow these instructions:
- omnisv stop
- Clear all the directory conent of /var/opt/omni/log/AppServer / C:\ProgramData\OmniBack\log\AppServer
- omnisv -start -debug 1-500 logs.txt AppServer
- Once you the issue has been duplicated disabled debugging by running omnisv stop / omnisv start
Re: (DP) Support Tip: How to Debug AppServer
UPDATE: I've just checked the change in A.10.03 you mentioned and I really like it. This is pretty handy and makes AppServer debugging easy compared with the previous approach. The information below apply for A.10.02 and earlier.
As far as I know running omnisv in debug mode will not enable AppServer debugs. JBoss/Wildfly will not respond to the debug parameter so a manual modifcation of the standalone.xml is required to get more of less log information from AppServer.
So you can add this section one or multiple times and replace category=“X".
<logger category=“X" use-parent-handlers="false">
<handlers> <handler name="DP_LOGGER"/> </handlers> </logger>
Examples for category=“X" values:
Please use the Like button below, if you find this post useful.