[jira] [Commented] (DIRSTUDIO-1287) Error connecting to LDAPS server
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401851#comment-17401851 ] Robin commented on DIRSTUDIO-1287: -- Let me know if there’s any other debugging I can do to determine if that’s the case, happy to play around with this. > Error connecting to LDAPS server > > > Key: DIRSTUDIO-1287 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1287 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M17 >Reporter: Robin >Priority: Major > > In trying to connect to an LDAP server via TLS I have run into what I believe > to be a bug. > The LDAP server is the built-in one on a Synology NAS with a valid > certificate installed. > I am able to successfully bind to it using LDAPS on port 636 using > javax.naming: > {code:java} > Hashtable env = new Hashtable(); > env.put(Context.INITIAL_CONTEXT_FACTORY, > "com.sun.jndi.ldap.LdapCtxFactory"); > env.put(Context.PROVIDER_URL, ldapUrl); > env.put(Context.SECURITY_AUTHENTICATION, authentication); > env.put(Context.SECURITY_PRINCIPAL, bindDN); > env.put(Context.SECURITY_CREDENTIALS, password); > return new InitialLdapContext (env, null); > {code} > However, when trying to connect using Apache Directory Studio I keep getting > an error: > The authentication failed ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue > has been emptied, no response was found. > I started Directory Studio with -Djavax.net.debug=all to see what happens and > this is what I found: > * There's a bunch of logging which eventually ends with this line: > {code:java} > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:20.548 > BST|SSLSessionImpl.java:242|Session initialized: > Session(1629363140485|TLS_AES_128_GCM_SHA256){code} > * It then idles for a while after which this happens: > {code:java} > javax.net.ssl|ALL|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineImpl.java:752|Closing outbound of SSLEngine > javax.net.ssl|WARNING|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:168|outbound has closed, ignore outbound > application data > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:505|WRITE: TLS13 alert, length = 2 > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLCipher.java:2036|Plaintext before ENCRYPTION ( > : 01 00 15 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0010: 00 00 00 ... > ) > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:523|Raw write ( > : 17 03 03 00 23 00 65 A2 9A C7 DD 2C 23 8D 18 75 #.e,#..u > 0010: 98 7F 17 DD 3B 01 61 36 C8 83 9A E1 0D 41 B0 00 ;.a6.A.. > 0020: 07 8D 20 48 EB 1E 31 7B.. H..1. > ) > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:50.513 > BST|SSLEngineImpl.java:724|Closing inbound of SSLEngine > javax.net.ssl|ERROR|34|NioProcessor-5|2021-08-19 09:52:50.514 > BST|TransportContext.java:341|Fatal (INTERNAL_ERROR): closing inbound before > receiving peer's close_notify ( > "throwable" : { > javax.net.ssl.SSLException: closing inbound before receiving peer's > close_notify > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133) > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283) > at > java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733) > at org.apache.mina.filter.ssl.SslHandler.destroy(SslHandler.java:209) > at > org.apache.mina.filter.ssl.SslFilter.sessionClosed(SslFilter.java:485) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.access$900(DefaultIoFilterChain.java:49) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.sessionClosed(DefaultIoFilterChain.java:1092) > at > org.apache.mina.core.filterchain.IoFilterAdapter.sessionClosed(IoFilterAdapter.java:98) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.fireSessionClosed(DefaultIoFilterChain.java:599) > at > org
[jira] [Commented] (DIRSTUDIO-1287) Error connecting to LDAPS server
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401846#comment-17401846 ] Stefan Seelmann commented on DIRSTUDIO-1287: In M17 we integrated LDAP API 2.1.0 which enables TLS 1.3 (https://issues.apache.org/jira/browse/DIRAPI-375) which seems it was a mistake as https://issues.apache.org/jira/browse/DIRMINA-1132 seems to be an issue after all. In your debug log I see {{TLS13 alert}} so I assume it's related. > Error connecting to LDAPS server > > > Key: DIRSTUDIO-1287 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1287 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M17 >Reporter: Robin >Priority: Major > > In trying to connect to an LDAP server via TLS I have run into what I believe > to be a bug. > The LDAP server is the built-in one on a Synology NAS with a valid > certificate installed. > I am able to successfully bind to it using LDAPS on port 636 using > javax.naming: > {code:java} > Hashtable env = new Hashtable(); > env.put(Context.INITIAL_CONTEXT_FACTORY, > "com.sun.jndi.ldap.LdapCtxFactory"); > env.put(Context.PROVIDER_URL, ldapUrl); > env.put(Context.SECURITY_AUTHENTICATION, authentication); > env.put(Context.SECURITY_PRINCIPAL, bindDN); > env.put(Context.SECURITY_CREDENTIALS, password); > return new InitialLdapContext (env, null); > {code} > However, when trying to connect using Apache Directory Studio I keep getting > an error: > The authentication failed ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue > has been emptied, no response was found. > I started Directory Studio with -Djavax.net.debug=all to see what happens and > this is what I found: > * There's a bunch of logging which eventually ends with this line: > {code:java} > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:20.548 > BST|SSLSessionImpl.java:242|Session initialized: > Session(1629363140485|TLS_AES_128_GCM_SHA256){code} > * It then idles for a while after which this happens: > {code:java} > javax.net.ssl|ALL|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineImpl.java:752|Closing outbound of SSLEngine > javax.net.ssl|WARNING|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:168|outbound has closed, ignore outbound > application data > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:505|WRITE: TLS13 alert, length = 2 > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLCipher.java:2036|Plaintext before ENCRYPTION ( > : 01 00 15 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0010: 00 00 00 ... > ) > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:523|Raw write ( > : 17 03 03 00 23 00 65 A2 9A C7 DD 2C 23 8D 18 75 #.e,#..u > 0010: 98 7F 17 DD 3B 01 61 36 C8 83 9A E1 0D 41 B0 00 ;.a6.A.. > 0020: 07 8D 20 48 EB 1E 31 7B.. H..1. > ) > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:50.513 > BST|SSLEngineImpl.java:724|Closing inbound of SSLEngine > javax.net.ssl|ERROR|34|NioProcessor-5|2021-08-19 09:52:50.514 > BST|TransportContext.java:341|Fatal (INTERNAL_ERROR): closing inbound before > receiving peer's close_notify ( > "throwable" : { > javax.net.ssl.SSLException: closing inbound before receiving peer's > close_notify > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133) > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283) > at > java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733) > at org.apache.mina.filter.ssl.SslHandler.destroy(SslHandler.java:209) > at > org.apache.mina.filter.ssl.SslFilter.sessionClosed(SslFilter.java:485) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.access$900(DefaultIoFilterChain.java:49) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.sessionClosed(DefaultIoFilterChain.java:1092) > at > org.apache.mina.core.filterchain.IoFilterAdapter.sessionClosed(IoFilterAdapter.java:98) > at > org.apache.mina.core.filterchain.DefaultIoFi
[jira] [Updated] (DIRSTUDIO-1286) Windows installer: the software version is missing
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1286: --- Fix Version/s: 2.0.0-M18 > Windows installer: the software version is missing > -- > > Key: DIRSTUDIO-1286 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286 > Project: Directory Studio > Issue Type: Improvement > Components: studio-installer >Affects Versions: 2.0.0-M17 > Environment: Windows 10 >Reporter: Elvis Bortoletto >Priority: Minor > Fix For: 2.0.0-M18 > > Attachments: image-2021-08-17-18-31-32-731.png, > image-2021-08-17-18-32-47-581.png > > > Once installed the Directory Studio, the version is not reported in "Control > Panel | Programs and Features". > !image-2021-08-17-18-32-47-581.png! > As a side effect, "winget upgrade" gets confused, reporting the Directory > Studio in the list of the packages with an available upgrade. > !image-2021-08-17-18-31-32-731.png! > Maybe reporting the software version would enhance the user experience and > would fix the winget behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1286) Windows installer: the software version is missing
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1286. Resolution: Fixed > Windows installer: the software version is missing > -- > > Key: DIRSTUDIO-1286 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286 > Project: Directory Studio > Issue Type: Improvement > Components: studio-installer >Affects Versions: 2.0.0-M17 > Environment: Windows 10 >Reporter: Elvis Bortoletto >Priority: Minor > Fix For: 2.0.0-M18 > > Attachments: image-2021-08-17-18-31-32-731.png, > image-2021-08-17-18-32-47-581.png > > > Once installed the Directory Studio, the version is not reported in "Control > Panel | Programs and Features". > !image-2021-08-17-18-32-47-581.png! > As a side effect, "winget upgrade" gets confused, reporting the Directory > Studio in the list of the packages with an available upgrade. > !image-2021-08-17-18-31-32-731.png! > Maybe reporting the software version would enhance the user experience and > would fix the winget behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSTUDIO-1286) Windows installer: the software version is missing
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401839#comment-17401839 ] Stefan Seelmann commented on DIRSTUDIO-1286: Great, thank for reporting and the patch :) > Windows installer: the software version is missing > -- > > Key: DIRSTUDIO-1286 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286 > Project: Directory Studio > Issue Type: Improvement > Components: studio-installer >Affects Versions: 2.0.0-M17 > Environment: Windows 10 >Reporter: Elvis Bortoletto >Priority: Minor > Fix For: 2.0.0-M18 > > Attachments: image-2021-08-17-18-31-32-731.png, > image-2021-08-17-18-32-47-581.png > > > Once installed the Directory Studio, the version is not reported in "Control > Panel | Programs and Features". > !image-2021-08-17-18-32-47-581.png! > As a side effect, "winget upgrade" gets confused, reporting the Directory > Studio in the list of the packages with an available upgrade. > !image-2021-08-17-18-31-32-731.png! > Maybe reporting the software version would enhance the user experience and > would fix the winget behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Commented] (DIRSTUDIO-1287) Error connecting to LDAPS server
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401585#comment-17401585 ] Robin commented on DIRSTUDIO-1287: -- I tried this on M16 and it works consistently. Random tests on M17: * Single-click the connection in the Connections view and then expand the DIT object in the LDAP Browser view: Does not work - QUEUE_EMPTIED * Double-click the connection in the Connections view and wait for it to connect: Does not work - QUEUE_EMPTIED * Double-click the connection in the Connections view and then expand the DIT and Root DSE objects in the LDAP browser view whilst the Progress view shows it is trying to connect: Appears to work every time Strange one, but at least it looks like there's a workaround that allows this to work on M17. > Error connecting to LDAPS server > > > Key: DIRSTUDIO-1287 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1287 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M17 >Reporter: Robin >Priority: Major > > In trying to connect to an LDAP server via TLS I have run into what I believe > to be a bug. > The LDAP server is the built-in one on a Synology NAS with a valid > certificate installed. > I am able to successfully bind to it using LDAPS on port 636 using > javax.naming: > {code:java} > Hashtable env = new Hashtable(); > env.put(Context.INITIAL_CONTEXT_FACTORY, > "com.sun.jndi.ldap.LdapCtxFactory"); > env.put(Context.PROVIDER_URL, ldapUrl); > env.put(Context.SECURITY_AUTHENTICATION, authentication); > env.put(Context.SECURITY_PRINCIPAL, bindDN); > env.put(Context.SECURITY_CREDENTIALS, password); > return new InitialLdapContext (env, null); > {code} > However, when trying to connect using Apache Directory Studio I keep getting > an error: > The authentication failed ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue > has been emptied, no response was found. > I started Directory Studio with -Djavax.net.debug=all to see what happens and > this is what I found: > * There's a bunch of logging which eventually ends with this line: > {code:java} > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:20.548 > BST|SSLSessionImpl.java:242|Session initialized: > Session(1629363140485|TLS_AES_128_GCM_SHA256){code} > * It then idles for a while after which this happens: > {code:java} > javax.net.ssl|ALL|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineImpl.java:752|Closing outbound of SSLEngine > javax.net.ssl|WARNING|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:168|outbound has closed, ignore outbound > application data > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:505|WRITE: TLS13 alert, length = 2 > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLCipher.java:2036|Plaintext before ENCRYPTION ( > : 01 00 15 00 00 00 00 00 00 00 00 00 00 00 00 00 > 0010: 00 00 00 ... > ) > javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 > BST|SSLEngineOutputRecord.java:523|Raw write ( > : 17 03 03 00 23 00 65 A2 9A C7 DD 2C 23 8D 18 75 #.e,#..u > 0010: 98 7F 17 DD 3B 01 61 36 C8 83 9A E1 0D 41 B0 00 ;.a6.A.. > 0020: 07 8D 20 48 EB 1E 31 7B.. H..1. > ) > javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:50.513 > BST|SSLEngineImpl.java:724|Closing inbound of SSLEngine > javax.net.ssl|ERROR|34|NioProcessor-5|2021-08-19 09:52:50.514 > BST|TransportContext.java:341|Fatal (INTERNAL_ERROR): closing inbound before > receiving peer's close_notify ( > "throwable" : { > javax.net.ssl.SSLException: closing inbound before receiving peer's > close_notify > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133) > at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292) > at > java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283) > at > java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733) > at org.apache.mina.filter.ssl.SslHandler.destroy(SslHandler.java:209) > at > org.apache.mina.filter.ssl.SslFilter.sessionClosed(SslFilter.java:485) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) > at > org.apache.mina.core.filterchain.DefaultIoFilterChain.access$900(
[jira] [Commented] (DIRSTUDIO-1286) Windows installer: the software version is missing
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401581#comment-17401581 ] Elvis Bortoletto commented on DIRSTUDIO-1286: - I've just tried it out, and it worked! Thank you very much! > Windows installer: the software version is missing > -- > > Key: DIRSTUDIO-1286 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1286 > Project: Directory Studio > Issue Type: Improvement > Components: studio-installer >Affects Versions: 2.0.0-M17 > Environment: Windows 10 >Reporter: Elvis Bortoletto >Priority: Minor > Attachments: image-2021-08-17-18-31-32-731.png, > image-2021-08-17-18-32-47-581.png > > > Once installed the Directory Studio, the version is not reported in "Control > Panel | Programs and Features". > !image-2021-08-17-18-32-47-581.png! > As a side effect, "winget upgrade" gets confused, reporting the Directory > Studio in the list of the packages with an available upgrade. > !image-2021-08-17-18-31-32-731.png! > Maybe reporting the software version would enhance the user experience and > would fix the winget behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Created] (DIRSTUDIO-1287) Error connecting to LDAPS server
Robin created DIRSTUDIO-1287: Summary: Error connecting to LDAPS server Key: DIRSTUDIO-1287 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1287 Project: Directory Studio Issue Type: Bug Affects Versions: 2.0.0-M17 Reporter: Robin In trying to connect to an LDAP server via TLS I have run into what I believe to be a bug. The LDAP server is the built-in one on a Synology NAS with a valid certificate installed. I am able to successfully bind to it using LDAPS on port 636 using javax.naming: {code:java} Hashtable env = new Hashtable(); env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory"); env.put(Context.PROVIDER_URL, ldapUrl); env.put(Context.SECURITY_AUTHENTICATION, authentication); env.put(Context.SECURITY_PRINCIPAL, bindDN); env.put(Context.SECURITY_CREDENTIALS, password); return new InitialLdapContext (env, null); {code} However, when trying to connect using Apache Directory Studio I keep getting an error: The authentication failed ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue has been emptied, no response was found. I started Directory Studio with -Djavax.net.debug=all to see what happens and this is what I found: * There's a bunch of logging which eventually ends with this line: {code:java} javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:20.548 BST|SSLSessionImpl.java:242|Session initialized: Session(1629363140485|TLS_AES_128_GCM_SHA256){code} * It then idles for a while after which this happens: {code:java} javax.net.ssl|ALL|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 BST|SSLEngineImpl.java:752|Closing outbound of SSLEngine javax.net.ssl|WARNING|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 BST|SSLEngineOutputRecord.java:168|outbound has closed, ignore outbound application data javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 BST|SSLEngineOutputRecord.java:505|WRITE: TLS13 alert, length = 2 javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 BST|SSLCipher.java:2036|Plaintext before ENCRYPTION ( : 01 00 15 00 00 00 00 00 00 00 00 00 00 00 00 00 0010: 00 00 00 ... ) javax.net.ssl|DEBUG|32|Worker-4: Open Connection|2021-08-19 09:52:50.512 BST|SSLEngineOutputRecord.java:523|Raw write ( : 17 03 03 00 23 00 65 A2 9A C7 DD 2C 23 8D 18 75 #.e,#..u 0010: 98 7F 17 DD 3B 01 61 36 C8 83 9A E1 0D 41 B0 00 ;.a6.A.. 0020: 07 8D 20 48 EB 1E 31 7B.. H..1. ) javax.net.ssl|ALL|34|NioProcessor-5|2021-08-19 09:52:50.513 BST|SSLEngineImpl.java:724|Closing inbound of SSLEngine javax.net.ssl|ERROR|34|NioProcessor-5|2021-08-19 09:52:50.514 BST|TransportContext.java:341|Fatal (INTERNAL_ERROR): closing inbound before receiving peer's close_notify ( "throwable" : { javax.net.ssl.SSLException: closing inbound before receiving peer's close_notify at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133) at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:336) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:292) at java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:283) at java.base/sun.security.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:733) at org.apache.mina.filter.ssl.SslHandler.destroy(SslHandler.java:209) at org.apache.mina.filter.ssl.SslFilter.sessionClosed(SslFilter.java:485) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) at org.apache.mina.core.filterchain.DefaultIoFilterChain.access$900(DefaultIoFilterChain.java:49) at org.apache.mina.core.filterchain.DefaultIoFilterChain$EntryImpl$1.sessionClosed(DefaultIoFilterChain.java:1092) at org.apache.mina.core.filterchain.IoFilterAdapter.sessionClosed(IoFilterAdapter.java:98) at org.apache.mina.core.filterchain.DefaultIoFilterChain.callNextSessionClosed(DefaultIoFilterChain.java:606) at org.apache.mina.core.filterchain.DefaultIoFilterChain.fireSessionClosed(DefaultIoFilterChain.java:599) at org.apache.mina.core.service.IoServiceListenerSupport.fireSessionDestroyed(IoServiceListenerSupport.java:251) at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.removeNow(AbstractPollingIoProcessor.java:1142) at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.removeSessions(AbstractPollingIoProcessor.java:864) at org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run(AbstractPollingIoProcessor.java: