A vital piece of information that often goes overlooked is the load created by standard and custom methods run on the Java Method Server. In some applications (such as D2), the JMS is used extensively for application functionality and this can have performance implications to your end users.
You can capture this information by enabling the JMS access log, which is not enabled by default.
Open the JMS DctmServer_MethodServer/configuration/standalone.xml, and find the string “urn:jboss:domain:web:1.1”, and add the <access-log> element as shown below:
<subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false"> <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/> <virtual-server name="default-host" enable-welcome-root="true"> <alias name="localhost"/> <alias name="example.com"/>
<access-log pattern=”%a %t %H %p %U %s %S %T” rotate=”true”> <directory path=”.”/> </access-log>
</virtual-server> </subsystem>
This will create an “access_log.yyyy_mm_dd” in the same directory where you can find the other Jboss logs: boot.log and server.log.
The last value on the log line coming from “%T” denotes how long it took to execute the method.