Welcome to the Jazz Community Forum
Who is the "client" within ETL jobs which requires TLS V1.0 to run the job?
Our corporate security requested to disable TLS V.1.0 on our Webservers so I disabled this within IHS httpd.conf on the port 443.
Jazz is working well on the UI. I have not seen any issue without TLS V1.0. Also the Eclipse Client is working without problems.
But this morning I recognized that most ETL jobs failed. I looked into the ETL log files and got the error:
ERROR e.repository.internal.LicenseRemoteSnapshotService - javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.
This message I get for all ETL Jobs except the “Star”. I also see this error every hour in the log. I changed now httpd.conf, enable TLSV1.0 again and restarted the HIS service. After this I’m able to run the Collector jobs.
Question: who is the client in this case, referenced in the error message? Can we enable somewhere the support of TLSV1.1 or higher for the ETL Jobs?
Full Log:
2013-02-18 01:17:05,968 [ jts: AsynchronousTaskRunner-2] ERROR e.repository.internal.LicenseRemoteSnapshotService - javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.
java.sql.SQLException: javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.
at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.fetchMoreData(BaseRDSResultSet.java:2101)
at com.ibm.rational.drivers.jdbc.xml.BaseRDSResultSet.next(BaseRDSResultSet.java:1472)
at com.ibm.team.datawarehouse.service.XdcResultSet.next(XdcResultSet.java:176)
at com.ibm.team.datawarehouse.service.repository.internal.etlbuild.IntegralRangeCounter.execute(IntegralRangeCounter.java:75)
at com.ibm.team.datawarehouse.service.repository.internal.LicenseRemoteSnapshotService.updateSnapshot(LicenseRemoteSnapshotService.java:67)
at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService$1.run(AbstractRemoteSnapshotService.java:200)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService$5.run(RemoteDatabaseService.java:254)
at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:381)
at com.ibm.team.datawarehouse.service.internal.RemoteDatabaseService.write(RemoteDatabaseService.java:244)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy71.write(Unknown Source)
at com.ibm.team.datawarehouse.service.internal.RemoteDataWarehouseProvider.write(RemoteDataWarehouseProvider.java:29)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy532.write(Unknown Source)
at com.ibm.team.datawarehouse.service.etl.AbstractRemoteSnapshotService.updateData(AbstractRemoteSnapshotService.java:195)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy335.updateData(Unknown Source)
at com.ibm.team.datawarehouse.service.AbstractSnapshotTask.run(AbstractSnapshotTask.java:88)
at com.ibm.team.datawarehouse.service.AbstractExclusiveTask.runTask(AbstractExclusiveTask.java:38)
at com.ibm.team.repository.service.async.AbstractAutoScheduledTask.executeTask(AbstractAutoScheduledTask.java:88)
at sun.reflect.GeneratedMethodAccessor63.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
at $Proxy336.executeTask(Unknown Source)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.runTask(AsynchronousTaskRunner.java:153)
at com.ibm.team.repository.service.internal.scheduler.AsynchronousTaskRunner.run(AsynchronousTaskRunner.java:116)
at java.lang.Thread.run(Thread.java:772)
One answer
Seen in Forum Question:
https://jazz.net/forum/questions/96722/why-are-data-warehouse-jobs-failing-with-peer-not-authenticated
https://jazz.net/forum/questions/96722/why-are-data-warehouse-jobs-failing-with-peer-not-authenticated
Maybe this is the answer:
In WebSphere Security / SSL Configurations / Node Default / Quality of Protection had "SSL" for the protocol. The working JTS had "SSL_TLS" for the same setting.
Comments
Guido Schneider
Mar 15 '13, 5:40 a.m.I created defect:
https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#action=com.ibm.team.workitem.viewWorkItem&id=255958