Trace Levels

For SSL
com.ibm.ws.websvcs.*=all: com.ibm.ws.policyset.*=all: com.ibm.ws.wssecurity.*=all: com.ibm.ws.wsaddressing.*=all: com.ibm.ws.wstx.*=all: org.apache.axis2.*=all

For Adapter
com.ibm.j2ca* = all

For Trace JaxWS
com.ibm.ws.websvcs.trace.*=all: com.ibm.bpm.ws.jaxws.*=all
*=info:com.ibm.websphere.wssecurity.*=all:com.ibm.ws.webservices.wssecurity.*=all:com.ibm.wsspi.wssecurity.*=all:com.ibm.ws.wssecurity.*=all:com.ibm.xml.soapsec.*=all:com.ibm.ws.webservices.trace.*=all:com.ibm.ws.websvcs.trace.*=all:com.ibm.ws.webservices.multiprotocol.AgnosticService=all:

http://www-01.ibm.com/support/docview.wss?uid=swg21199176

*=info: SCA.JMS=all: com.ibm.mq.*=all: com.ibm.ejs.jms.*=all

Jms MQ

*=info:SCA.JMS=all:com.ibm.mq.*=all:com.ibm.ejs.jms.*=all

SerializerException:
 

*=info:com.ibm.wbiserver.map.*=all:SCA.*=all:ArtifactLoader=all:BOCore=all:BOFactory=all:BOXMLSerializer=all:
BOXMLDocument=all:BOTypeMetaData=all

It is recommended to set the number of historical trace files to 10 and the size of each historical trace file to 100MB, in case useful traces are overwritten. Please don't forget to disable the trace string after test.

1)  Stop the server.

2)  Remove all the existing logs trace and FFDCs so we have a more concise log output.

3)  Restart the server.

4)  Reproduce the issue and note the time the symptoms occurred.

5)  Insure the trace covers the time period noted in step four above.

6)  Zip up the profile's logs directory.

7)  Send us the zip of the logs directory noting any errors, exceptions, or symptoms.