Yes, you can turn on debug logging in the CQ Connector gateway process, the Jazz server, or both.

Creata a file named "log4j.properties" in the /jazz/connectors/gateway directory with this content:

log4j.rootLogger=WARN, stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %-50.50c - %m%n
log4j.logger.com.ibm.rational.interop=DEBUG
log4j.logger.com.ibm.rational.interop.detail=OFF

To turn on logging in the CQ Connector gateway, edit the server.startup.bat script to add "-Dlog4j.configuration=log4j.properties" to the CATALINA_OPTS environment variable, then stop and restart the gateway. To turn on even more verbose logging, change the value of the "detail" property from OFF to DEBUG.

The Jazz server already has a default log4j.properties file (as of M4), so to enable connector debug logging, just add these two lines to the file and restart the server:

log4j.logger.com.ibm.team.interop=DEBUG
log4j.logger.com.ibm.team.interop.service.outgoingSyncJob=OFF

To enable more verbose logging, change the value of the "outgoingSyncJob" property from OFF to DEBUG.

You can also open the Synchronization Rules view, right-click on your project area, and choose Show All Unsynchronized to see a list of any items where synchronization was attempted but not completed for some reason. Double-clicking on an item opens a more detailed display for that item.

Hope this helps,
John

Hi all,
is there a way to debug the ClearQuest connector outside of Eclipse?
Should we enable the verbose at the level of the ClearQuest's Connector proxy logger (log4j) ?
We'd like to understand what is happening during the Defect synchronization process in order to debug Work items that did not synchronise correctly.
Thank you for your time!