Java.net.socketexception: connection reset
Our application runs on weblogic servers,
Intermittently we are getting below errors , after restarting weblogic managed server it is working fine We are using bc jars jdk18on-1.78.1jar
Please suggest
com.xx.migration.util.logger.MigrationUtilityLogger] [WS-Worker-1] [31] [ERROR] class com.xx.m igration.model.webServiceImpl.ConsumeMicroServiceTask: Boom, we failed: : java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at org.bouncycastle.tls.RecordStream$Record.fillTo(Unknown Source) at org.bouncycastle.tls.RecordStream$Record.readHeader(Unknown Source) at org.bouncycastle.tls.RecordStream.readRecord(Unknown Source) at org.bouncycastle.tls.TlsProtocol.safeReadRecord(Unknown Source) at org.bouncycastle.tls.TlsProtocol.blockForHandshake(Unknown Source) at org.bouncycastle.tls.TlsClientProtocol.connect(Unknown Source) at org.bouncycastle.jsse.provider.ProvSSLSocketWrap.startHandshake(Unknown Source) at org.bouncycastle.jsse.provider.ProvSSLSocketWrap.startHandshake(Unknown Source) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:395) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:354) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:134) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) at com.xx.migration.model.webServiceImpl.ConsumeMicroServiceTask.getResponse(ConsumeMicroServiceTask.java:409) at com.xx.migration.model.webServiceImpl.ConsumeMicroServiceTask.getAddress(ConsumeMicroServiceTask.java:224) at com.xx.migration.model.webServiceImpl.ConsumeMicroServiceTask.execute(ConsumeMicroServiceTask.java:184) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.xx.migration.util.common.executor.WSTask.execute(WSTask.java:28) at com.xx.migration.util.common.executor.WSExecutor$WorkerThread.run(WSExecutor.java:141)
Adding more loggers that I found in managed server logs.
<12-Mar-2025 02:00:01,888 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.DisabledAlgorithmConstraints> <BEA-000000> <Ignoring unsupported entry in 'jdk.tls.disabledAlgorithms': include jdk.disabled.namedCurves> <12-Mar-2025 02:00:01,889 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.DisabledAlgorithmConstraints> <BEA-000000> <Ignoring unsupported entry in 'jdk.certpath.disabledAlgorithms': SHA1 jdkCA & usage TLSServer> <12-Mar-2025 02:00:01,889 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.DisabledAlgorithmConstraints> <BEA-000000> <Ignoring unsupported entry in 'jdk.certpath.disabledAlgorithms': include jdk.disabled.namedCurves> <12-Mar-2025 02:00:01,890 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.DisabledAlgorithmConstraints> <BEA-000000> <Ignoring unsupported entry in 'jdk.certpath.disabledAlgorithms': SHA1 usage SignedJAR & denyAfter 2019-01-01> <12-Mar-2025 07:01:14,456 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.ProvTlsClient> <BEA-000000> <[!dt dt.trace_id=,dt.span_id=,dt.trace_sampled=true] [client #177 @5bc932a4] raised fatal(2) internal_error(80) alert: Failed to read record java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at org.bouncycastle.tls.RecordStream$Record.fillTo(Unknown Source) at org.bouncycastle.tls.RecordStream$Record.readHeader(Unknown Source) at org.bouncycastle.tls.RecordStream.readRecord(Unknown Source) Truncated.
<12-Mar-2025 07:01:14,524 o'clock GMT> <Warning> <org.bouncycastle.jsse.provider.ProvTlsClient> <BEA-000000> <[!dt dt.trace_id=,dt.span_id=,dt.trace_sampled=true] [client #178 @1b7e7cf6] raised fatal(2) internal_error(80) alert: Failed to read record java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at org.bouncycastle.tls.RecordStream$Record.fillTo(Unknown Source) at org.bouncycastle.tls.RecordStream$Record.readHeader(Unknown Source)
Mar 12, 2025 7:01:14 AM org.bouncycastle.jsse.provider.PropertyUtils getBooleanSecurityProperty INFO: Found boolean security property [keystore.type.compat]: true Mar 12, 2025 7:01:14 AM org.bouncycastle.jsse.provider.ProvTlsClient notifyHandshakeBeginning INFO: [!dt dt.trace_id=,dt.span_id=,dt.trace_sampled=true] [client #177 @5bc932a4] opening connection to Mar 12, 2025 7:01:14 AM org.bouncycastle.jsse.provider.ProvTlsClient notifyAlertRaised WARNING: [!dt dt.trace_id=,dt.span_id=,dt.trace_sampled=true] [client #177 @5bc932a4] raised fatal(2) internal_error(80) alert: Failed to read record java.net.SocketException: Connection reset
Could you please suggest
Could you suggest this intermittent connection reset error