After Java upgrade, Automic proxy server 1.0.1 fails to start

Document ID : KB000084469
Last Modified Date : 14/04/2018
Show Technical Document Details
Issue:
Error Message :
Proxy Server 1.0.1: U2100015 java.lang.Exception: Error detected in ServiceConnection: Asynchronous failure: bad record MAC
Proxy Client 1.0.1: U2100015 java.lang.Exception: Error detected in ServiceConnection: Asynchronous failure: Inbound closed before receiving peer's close_notify: possible truncation attack?

After upgrading the java version from 1.7 to 1.8 the  Proxy Server 1.0.1 won't start anymore.

Error message in the Proxy Server is the following:
20180120/083607.097 - U2100015 
java.lang.Exception: Error detected in ServiceConnection: Asynchronous failure: bad record MAC
    at com.uc4.proxy.shared.ServiceConnectionProtocol.socketException(ServiceConnectionProtocol.java:431)
    at com.uc4.proxy.nbio.PacketChannel.handleRead(PacketChannel.java:171)
    at com.uc4.proxy.nbio.SSLChannel.fireReadEvent(SSLChannel.java:405)
    at com.uc4.proxy.nbio.SSLChannelManager.fireEvents(SSLChannelManager.java:32)
    at com.uc4.proxy.nbio.SelectorThread.run(SelectorThread.java:287)
    at com.uc4.proxy.nbio.SelectorThread.access$000(SelectorThread.java:40)
    at com.uc4.proxy.nbio.SelectorThread$1.run(SelectorThread.java:88)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Asynchronous failure: bad record MAC
    at com.uc4.proxy.nbio.SSLChannel.checkChannelStillValid(SSLChannel.java:166)
    at com.uc4.proxy.nbio.SSLChannel.read(SSLChannel.java:172)
    at com.uc4.proxy.nbio.PacketChannel.handleRead(PacketChannel.java:151)
    ... 6 more
Caused by: javax.net.ssl.SSLException: bad record MAC
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.readRecord(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.readNetRecord(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.unwrap(Unknown Source)
    at javax.net.ssl.SSLEngine.unwrap(Unknown Source)
    at com.uc4.proxy.nbio.SSLChannel.readAndDecrypt(SSLChannel.java:237)
    at com.uc4.proxy.nbio.SSLChannel.handleRead(SSLChannel.java:626)
    at com.uc4.proxy.nbio.SelectorThread.run(SelectorThread.java:322)
    ... 3 more

Error message in the Proxy Client is the following:
20180120/105429.509 - U2100015 
java.lang.Exception: Error detected in ServiceConnection: Asynchronous failure: Inbound closed before receiving peer's close_notify: possible truncation attack?
    at com.uc4.proxy.shared.ServiceConnectionProtocol.socketException(ServiceConnectionProtocol.java:435)
    at com.uc4.proxy.nbio.PacketChannel.handleRead(PacketChannel.java:171)
    at com.uc4.proxy.nbio.SSLChannel.fireReadEvent(SSLChannel.java:405)
    at com.uc4.proxy.nbio.SSLChannelManager.fireEvents(SSLChannelManager.java:32)
    at com.uc4.proxy.nbio.SelectorThread.run(SelectorThread.java:287)
    at com.uc4.proxy.nbio.SelectorThread.access$000(SelectorThread.java:40)
    at com.uc4.proxy.nbio.SelectorThread$1.run(SelectorThread.java:88)
    at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Asynchronous failure: Inbound closed before receiving peer's close_notify: possible truncation attack?
    at com.uc4.proxy.nbio.SSLChannel.checkChannelStillValid(SSLChannel.java:166)
    at com.uc4.proxy.nbio.SSLChannel.read(SSLChannel.java:172)
    at com.uc4.proxy.nbio.PacketChannel.handleRead(PacketChannel.java:151)
    ... 6 more
Caused by: javax.net.ssl.SSLException: Inbound closed before receiving peer's close_notify: possible truncation attack?
    at sun.security.ssl.Alerts.getSSLException(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.fatal(Unknown Source)
    at sun.security.ssl.SSLEngineImpl.closeInbound(Unknown Source)
    at com.uc4.proxy.nbio.SSLChannel.readAndDecrypt(SSLChannel.java:220)
    at com.uc4.proxy.nbio.SSLChannel.handleRead(SSLChannel.java:626)
    at com.uc4.proxy.nbio.SelectorThread.run(SelectorThread.java:322)
    ... 3 more

 
Environment:
OS Version: N/A
Cause:
Cause type:
Configuration
Root Cause: For Proxy version 1.0.1 only java 1.7 is supported:
Resolution:
According to our Compatibility Matrix only Java 1.7 is supported for Proxy 1.0.1.

https://downloads.automic.com/tools/compatibility_matrix?compatibility-mode=component&offering_version_id=components&lifecycle_entity_id=1409731986357&version_id=1409731987584

To get the Proxy Server up and running again rollback the java version to 1.7.


Fix Status: No Fix

Fix Version(s):
N/A
Additional Information:
Workaround :
N/A