JBoss

Beside of two management consoles, available, if enabled during the installation process, at http://<host_name>:<port_number>/admin-console and http://<host_name>:<port_number>/web-console, JBoss offers also a JMX Console that can be enabled together with the management consoles. The JMX Console lists all registered services (MBeans) that are active in the application server and accessible either through the JMX Console itself or programmatically from Java code.

JBoss web console can be used to monitor memory usage, amount of calls to a specific method, method call durations, CPU usage, database connection pool statistics, etc.

Contents

• What can be done with JBoss consoles
• Server log files
• IFS Applications logging
• More information

Examples of things to do with the consoles:

• Display the JNDI-tree
• Manage Connection Pools
• Generate a thread dump
  Navigate to jboss.system:type=ServerInfo mbean, scroll down to the bottom where it says "listThreadDump" and invoke. 
• Display the memory pool usage
  Navigate to jboss.system:type=ServerInfo in order to check memory usage, available memory and other JVM-related information.
• Shut down JBoss
  Navigate to the jboss.system:type=Server mbean, click on the jboss.system:type=Server, scroll down to Shutdown and click invoke.
• IFS Log Management ( LoggingManager MBean)
  Navigate to the ifs.fnd.log:service=LoggingManager mbean, click on the ifs.fnd.log:service=LoggingManager. Set the appropriate values for different categories of logs and apply. Valid Log levels are DEBUG, INFO, TRACE, WARNING and ERROR.

Server log files

JBoss Web logging

Every access to the application server goes through the web server.
JBoss Web logs all client requests to access.log in IFS_HOME\jboss-eap-5.1\jboss-as\server\<instance>\log

169.254.19.167 - alain [30/Apr/2012:10:25:14 +0200] POST /fndext/clientgateway/ManageMyUserProfile/LoadMyUserProfile HTTP/1.1 200 18342 4020

In the example above a client with IP 169.254.19.167 successfully (the HTTP response code is 200) invoked the LoadMyUserProfile method in the ManageMyUserProfile activity. The HTTP response code is very important. A successful call will always result in the 200 - OK code. Anything else indicates some kind of error.

You might see codes such as:

503 - Service Unavailable (Application Server is probably down)
401 - Unauthorized (Typically indicates a user authentication problem)
500 - Internal server error (Some serious server problem prevented it from fulfilling the request)

JBoss logging

JBoss server logging outputs a mix of internal JBoss logs and log entries produced by the deployed applications in IFS_HOME\jboss-eap-5.1\jboss-as\server\<instance>\logs\server.log. By default, a very restrictive log level is used (you will not see much in this file). You can enable more extensive logging by checking "Enable extended logging" in the IFS Installer, but you have to do an instance reconfiguration to do this. The log files described below should be used before you start changing JBoss logging.

IFS Applications logging

You can change values for log levels and add or remove class specifications for class debugging, as described in Manage Server Logging, using JBoss JMX Console. Values can be changed in runtime (no need to restart the application server to apply changes)

• Navigate to the page http://<host_name>:<port_number>/jmx-console of the current application server.
• Find JMX MBean with name LoggingManager and click on the name.
  
• In the JMX MBean View page you can change log levels for categories; press Apply Changes after making any changes.
  
• At the bottom of the same page you can add or remove class logger definitions by entering parameter text, as documented here, and pressing button Invoke

Further reading

More information and tips can be found on the following pages:

• Redhat JBoss