Geek asks and answers

How to enable JVM logs in logs and tracing in the Websphere console

Whenever I go to the TroubleShooting-> Logs and Trace-> Server tab, I get a general properties section that only has a link for the Log Change Details option. I changed the trace inside to reflect my applications. But beyond this option, I cannot see the log files inside WAS. We have WAS on Z / OS and I can view mainframe logs. Is there a file or script that needs to be run to enable JVM logs?

+3
source share
1 answer

  • On AIX, Linux, and Windows, when I go to TroubleShooting → Logs and Trace → Server, I get a few links in the general properties section, one of which is the “Diagnostic trace”, through which I can enable / disable tracking and configuration, where Log files are located, their sizes, tipping parameters, etc.

    The fact that you do not see this link indicates that it is something specific to z / OS, or that you do not have privileges to perform operations at runtime. You can check whether you are logging in with a user who is a member of the Administrators group (you can check the user in Users and Groups - Administrative User Roles).

  • , , "" " ". , , . Runtime, .

  • wsadmin, http://pic.dhe.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftxml_profiletrace.html

    • ( )

      ts = AdminControl.queryNames('type=TraceService,node=mynode,process=server1,*')
AdminControl.setAttribute(ts, 'traceSpecification', 'com.ibm.=all=enabled')


    • ts = AdminControl.queryNames('type=TraceService,node=mynode,process=server1,*')
AdminControl.setAttribute(ts, 'traceSpecification', 'com.ibm.*=all=disabled')
0

More articles:


All Articles