Plenty of warnings in jazz.log: AuthenticationPolicy FormAuthentication
In one of our biggest repositories we are getting the same warning in jazz.log, between midnight and 1am, like the following:
2014-09-03 00:57:59,300 [ Thread-72887] WARN onal.dataservices.client.auth.AuthenticationPolicy - FormAuthentication: Can not create SSLContext with com.ibm.team.repository.transport.client.protocol protocol
We get them everyday, and around 2000-4000 each day. It seems to be related to ETL jobs, but there are no errors in the related etl logs, neither failures in the UI.
Accepted answer
Hi Gabriel
These warnings can be safely ignored. The error is due to the wrong string value is used for checking custom ssl protocol in the AuthenticationPolicy class. The string value should be System.getProperty("com.ibm.team.repository.transport.client.protocol") instead of "com.ibm.team.repository.transport.client.protocol".
Since we are already trapping, logging the exception and continue with the initialization of the remaining protocols, this error is safe to ignore.
This is a product defect logged under the Defect:114110
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/114110
You might not have permission to view the defect details as it's created internally.
Workaround:
Set this property in log4j for jazz and jts.
log4j.logger.com.ibm.rational.dataservices=OFF
setting this property will hide the warnings else these warnings can be safely ignored.
If this answers your question please mark it as accepted.
These warnings can be safely ignored. The error is due to the wrong string value is used for checking custom ssl protocol in the AuthenticationPolicy class. The string value should be System.getProperty("com.ibm.team.repository.transport.client.protocol") instead of "com.ibm.team.repository.transport.client.protocol".
Since we are already trapping, logging the exception and continue with the initialization of the remaining protocols, this error is safe to ignore.
This is a product defect logged under the Defect:114110
https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/114110
You might not have permission to view the defect details as it's created internally.
Workaround:
Set this property in log4j for jazz and jts.
log4j.logger.com.ibm.rational.dataservices=OFF
setting this property will hide the warnings else these warnings can be safely ignored.
If this answers your question please mark it as accepted.
One other answer
>>Where to you set this value? I did not find an entry in JTS or ccm advanced properties.
You need to open log4j.properties (located in your server side, typically server/conf/jts) for each JTS and CCM application and then add the suggested property, save the file. Exit. In order for the property to take effect,you don't need to restart the server. Just use following URL:
for jts:
https://<SERVER>:<PORT>/<jts_context>/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
for jazz/ccm
https://<SERVER>:<PORT>/<ccm_context>/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
SERVER : is your public URL of the JAZZ server.
PORT: port is used by your server, typically 9443 or 80
context: typically /jts (jazz team server) /ccm (Team Concert)
You need to open log4j.properties (located in your server side, typically server/conf/jts) for each JTS and CCM application and then add the suggested property, save the file. Exit. In order for the property to take effect,you don't need to restart the server. Just use following URL:
for jts:
https://<SERVER>:<PORT>/<jts_context>/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
for jazz/ccm
https://<SERVER>:<PORT>/<ccm_context>/admin?internal=true#action=com.ibm.team.repository.admin.reloadLoggingSettings
SERVER : is your public URL of the JAZZ server.
PORT: port is used by your server, typically 9443 or 80
context: typically /jts (jazz team server) /ccm (Team Concert)
Comments
Donald Nong
Sep 03 '14, 8:45 p.m.Also check the application server (Tomcat or WAS) log files and see if any related warnings/errors are there. Do the ETL jobs all finish without any problems? From the message, it seems that the JTS server cannot connect to one of the applications, which may be hosted on a different application server.