Open a command prompt and change directory to /WebSphere/AppServer/bin.

Type wsadmin (will take a minute to connect – if authentication is enabled, it will prompt).

Enter set jvm [$AdminControl completeObjectName,process=server1,*].

Replace server1 with the actual server you want to take a thread dump from (has to be local to this machine).

Enter $AdminControl invoke $jvm dumpThreads.

The thread dump is created in the profile folder for the server you created a dump for. There should be a “javacore.someText.txt” file created. If it’s a cluster, you’ll have to repeat the above steps for each server.

Websphere 7

Using JConsole. Connect the JConsole present in IBM JDK and trigger threaddump using that. You would have to follow the steps mentioned here for it to get to work.

Capturing SQL Logs

The SQL queries by UM can be logged using the default logging system for that system. Following two categories should be used:

com.adobe.idp.storeprovider.jdbc – Logs all the queries fired with the value populated.

storeprovider.stacktrace – This would also log the stacktrace of the thread which fired the query.

The logging level should be set to TRACE or the lowest for the queries to be logged. For the POF layer use the category com.adobe.pof.adapter for seeing the queries getting fired.