Rachana Ananthakrishnan wrote:
You can get detailed SSL logging by setting this to ON in
$GLOBUS_LOCATION/container-log4j.properties.
# SSL Debugging
log4j.category.COM.claymoresystems.ptls.SSLDebug=OFF
In the same configuration file, enable this to see what is sent on the
response:
# Enable on-the-wire logging (outgoing messages only)
# log4j.logger.httpclient.wire=DEBUG
We have similar logging for clients in log4j.properties.
Our setup has Java WS Core deployed under Tomcat 5.5.26, which uses JDK
logging by default, so I made the following additions to the Tomcat
conf/logging.properties configuration file:
COM.claymoresystems.ptls.SSLDebug.level = FINE
httpclient.wire.level = FINE
After restarting Tomcat with this change, copious amounts of hexadecimal
data were written to the logs/catalina.out log file when processing a
web service request, but I still did't see anything resembling a stack
trace or error message in the server side logs.
At this point, I'm reasonably certain my client-side certificate (a
"Web Server" certificate from Microsoft Certificate Services) is not
properly configured for grid usage, so my next logical step is to
correct that problem. (In other words, for this problem, I think there
isn't a strong need to extract further information from the Globus logs
right now.)
Thanks,
Joel
