When analyzing Thread Dumps

Thread States

BLOCKED            Thread state for a thread blocked waiting for a monitor lock.

NEW            Thread state for a thread which has not yet started.

RUNNABLE            Thread state for a runnable thread.

TERMINATED            Thread state for a terminated thread.

TIMED_WAITING            Thread state for a waiting thread with a specified waiting time.

WAITING            Thread state for a waiting thread.

Thread LC
http://bip.weizmann.ac.il/course/prog2/tutorial/essential/threads/lifecycle.html

Tool to analyse thread dumps: TDA

Some good guidelines:
http://nirmalfdo.blogspot.com/2013/05/how-to-find-culprit-when-cpu-starts-to.html

http_access logs

http_access logs files are prefixed with “http_access_”. These files include access information for the server. We can get the access information for webapps also from this. These logs rotates on daily basis.

In Carbon 4.0.* based products, you can disable http access logs by removing the following entry from catalina-server.xml which is located in $CARBON_HOME/repository/conf/tomcat.

<valve classname="org.apache.catalina.valves.AccessLogValve" directory="${carbon.home}/repository/logs" prefix="http_access_" suffix=".log" pattern="combined"/>

For the products which uses nhttp transport (Ex. WSO2 ESB) you also have to define the below entry in log4j.properties file.

log4j.logger.org.apache.synapse.transport.nhttp.Access=WARN

log4j.properties file is located in $CARBON_HOME/repository/conf/

Pointing the correct jars to your classpath

Add relevant $CARBON_HOME/repository/lib jars to your classpath after running "ant" command in $CARBON_HOME/bin