简体繁体 English

Poodle和Websphere ESB / Process Server尝试调用外部TLS服务

[英]Poodle and Websphere ESB / Process Server trying to call an external TLS service

原文 2014-10-22 13:28:48 0 1 java/ ssl/ websphere

I had the following error when calling a service that requests at least TLS (no SSL3 for you Poodle!). 调用至少要求TLS的服务时出现以下错误（贵宾犬没有SSL3！）。

com.ibm.websphere.sca.ServiceUnavailableException: Could not obtain a connection to the destination or Exception was happened on the connection. com.ibm.websphere.sca.ServiceUnavailableException：无法获得与目标的连接，或者该连接发生异常。 Failed to process the request. 无法处理请求。 Unsupported record version Unknown-0.0 at com.ibm.ws.http.imprt.handler.HTTPImportService.sendHTTPRequest(HTTPImportService.java:254) at com.ibm.ws.http.imprt.handler.HTTPImportHandler.processMessage(HTTPImportHandler.java:261) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:785) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1626) at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:999) at com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionImportExport(UOWNativeWASStrategyImpl.java:455) at com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage(JoinUOWNativeHandler.java:168) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:785) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1626) at com.ibm.ws com.ibm.ws.http.imprt.handler.HTTPImportHandler.processMessage（HTTPImportHandler.java：com.ibm.ws.http.imprt.handler.HTTPImportService.sendHTTPRequest（HTTPImportService.java:254）上不受支持的记录版本为Unknown-0.0 261）com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage（MessageDispatcherImpl.java：com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI（MessageDispatcherImpl.java:785） 1626），位于com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionImportExport（UOWNativeWASStrategyImpl.java:455）的com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process（ManagedMessageImpl.java:999）在com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI（MessageDispatcherImpl.java:785）处在com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI（MessageInpatcherImpl.java:785）在com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage com.ibm.ws上的.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage（MessageDispatcherImpl.java:1626） .sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:990) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.SCAInvocationAction.invokeSync(SCAInvocationAction.java:554) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeByStyle(RetryControl.java:379) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeWithRetry(RetryControl.java:253) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.ServiceInvocation.complete(ServiceInvocation.java:127) at com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActionFactoryImpl.create(FlowActionFactoryImpl.java:750) at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.invokeFlowAction(ServiceInvokeMediation.java:651) at com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.mediate(ServiceInvokeMediation.java:564) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:741) at com.ibm.ws.sibx.scax.mediation 位于com.ibm.ws.sibx.mediation.flowaction.impl.sca.SCAInvocationAction.invokeSync（SCAInvocationAction.java:554）的.sca.internal.message.impl.ManagedMessageImpl.process（ManagedMessageImpl.java:990） .ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeByStyle（RetryControl.java:379）位于com.ibm.ws.sibx.mediation.flowaction.impl.sca.RetryControl.invokeWithRetry（RetryControl.java:253） com.ibm.ws.sibx.mediation.flowaction.impl.sca.FlowActionFactoryImpl.create（FlowActionFactoryImpl.com.ibm.ws.sibx.mediation.flow.impl.sca.ServiceInvocation.complete（ServiceInvocation.java:127） com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.invokeFlowAction（ServiceInvokeMediation.java:651）处的com.ibm.ws.sibx.mediation.primitives.serviceinvoke.ServiceInvokeMediation.mediate（ServiceInvokeMediation。 java：564）位于com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation（JavaMediationPrimitive.java:741）位于com.ibm.ws.sibx.scax.mediation .engine.JavaMediationPrimitive.performInvocationWithCatch(JavaMediationPrimitive.java:577) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:397) at com.ibm.ws.sibx.scax.mediation.engine.SIBXJavaMediationPrimitive.invoke(SIBXJavaMediationPrimitive.java:108) at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:344) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:843) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:763) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocationWithCatch(JavaMediationPrimitive.java:577) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:397) at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:344) at com.ibm.ws.sibx. com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke（JavaMediationPrimitive.invoke（JavaMediationPrimitive.java:397）处的.engine.JavaMediationPrimitive.performInvocationWithCatch（JavaMediationPrimitive.java:577）位于com.ibm.ws.sibx.scax.mediation处位于com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections（MediationPrimitive.java:344）的com.ibm.ws.sibx.scax.mediation的.engine.SIBXJavaMediationPrimitive.invoke（SIBXJavaMediationPrimitive.java:108） com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation（JavaMediationPrimitive.java:763）上的.engine.JavaMediationPrimitive.fireOutputTerminals（JavaMediationPrimitive.java:843），位于com.ibm.ws.sibx.scax.mediation上com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke（JavaMediationPrimitive.invoke（JavaMediationPrimitive.java:397）处的.engine.JavaMediationPrimitive.performInvocationWithCatch（JavaMediationPrimitive.java:577）位于com.ibm.ws.sibx.scax.mediation处com.ibm.ws.sibx上的.engine.MediationPrimitive.invokeConnections（MediationPrimitive.java:344）。 scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals(JavaMediationPrimitive.java:843) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation(JavaMediationPrimitive.java:763) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocationWithCatch(JavaMediationPrimitive.java:577) at com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke(JavaMediationPrimitive.java:397) at com.ibm.ws.sibx.scax.mediation.engine.MediationPrimitive.invokeConnections(MediationPrimitive.java:344) at com.ibm.ws.sibx.scax.mediation.engine.Input.invoke(Input.java:245) com.ibm.ws.sibx上com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.performInvocation（JavaMediationPrimitive.java:763）上的scax.mediation.engine.JavaMediationPrimitive.fireOutputTerminals（JavaMediationPrimitive.java:843）。 com.ibm.ws.sibx上com.ibm.ws.sibx.scax.mediation.engine.JavaMediationPrimitive.invoke（JavaMediationPrimitive.java:397）上的scax.mediation.engine.JavaMediationPrimitive.performInvocationWithCatch（JavaMediationPrimitive.java:577）。位于com.ibm.ws.sibx.scax.mediation.engine.Input.invoke（Input.java:245）的scax.mediation.engine.MediationPrimitive.invokeConnections（MediationPrimitive.java:344）

The config was Websphere 8.0.0.7 with Websphere Process Server 8.0.1.2 and I was calling to an HTTP service using an HTTP import through https, the WAS was already using a SSL configuration with TLS (tried several options, all same error) and the ssl.client.props file is already following the IBM recommendations (tried several combinations). 配置为带有Websphere Process Server 8.0.1.2的Websphere 8.0.0.7，我正在使用通过https进行HTTP导入来调用HTTP服务，WAS已经在使用SSL配置和TLS（尝试了多个选项，所有相同的错误），并且ssl.client.props文件已经遵循IBM的建议（尝试了几种组合）。

Then we moved to FIPS with transitional support but another issue appeared 然后我们在过渡支持下移至FIPS，但出现了另一个问题

com.ibm.websphere.sca.ServiceUnavailableException: Could not obtain a connection to the destination or Exception was happened on the connection. com.ibm.websphere.sca.ServiceUnavailableException：无法获得与目标的连接，或者该连接发生异常。 Failed to process the request. 无法处理请求。 SSL protocol cannot be enabled in FIPS/SP800_131/suiteb mode at com.ibm.ws.http.imprt.handler.HTTPImportService.sendHTTPRequest(HTTPImportService.java:254) at com.ibm.ws.http.imprt.handler.HTTPImportHandler.processMessage(HTTPImportHandler.java:261) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI(MessageDispatcherImpl.java:785) at com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessage(MessageDispatcherImpl.java:1626) at com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process(ManagedMessageImpl.java:999) at com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionImportExport(UOWNativeWASStrategyImpl.java:455) at com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage(JoinUOWNativeHandler.java:168) 无法在com.ibm.ws.http.imprt.handler.HTTPImportHandler的com.ibm.ws.http.imprt.handler.HTTPImportService.sendHTTPRequest（HTTPImportService.java:254）的FIPS / SP800_131 / suiteb模式下启用SSL协议。 com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl.processMessageWithPCI（com.ibm.ws.sca.internal.message.impl.MessageDispatcherImpl的processMessage（HTTPImportHandler.java:261）。 com.ibm.ws.sca.internal.message.impl.ManagedMessageImpl.process（ManagedMessageImpl.java:999）处的processMessage（MessageDispatcherImpl.java:1626）com.ibm.ws.sca.uow.handler.UOWNativeWASStrategyImpl.transactionImportExport（ UOWNativeWASStrategyImpl.java:455），位于com.ibm.ws.sca.uow.handler.JoinUOWNativeHandler.processMessage（JoinUOWNativeHandler.java:168）

1 个解决方案

The problem was within the HTTP import internal component (was using SSL as a hardcoded configuration) so I wrote my own HTTP client in a custom Java and called it a day. 问题出在HTTP导入内部组件（使用SSL作为硬编码配置）之内，所以我用自定义Java编写了自己的HTTP客户端，并称之为一天。 No fix pack at that moment. 那时没有修订包。