Hi Maxim,
OK, that’s alright. Thanks for your comment.
I agree the log message should be improved. But also, if it‘s actually not
intended that sock.shutdownInput() is skipped, then the function should
probably also split into two try blocks.
Thanks!
On 16.02.22 at 12:13, Maxim Muzafarov wr
Hello,
According to the given exception stack trace, you may ignore this
warning message. It's sad to say and it's true that the log messages
should be improved, hopefully it will happen in the next release.
On Mon, 14 Feb 2022 at 18:34, Thomas Kramer wrote:
>
> Has anyone solved this or identif
Has anyone solved this or identified its severity?
Thanks,
Thomas.
On 01.02.22 11:03, Thomas Kramer wrote:
Hi,
I am switching from 2.8.1 to 2.12.0 and encounter an issue when
closing thin JDBC connection. This is my test case:
/ public static void main(String[] args) throws Exception//
/
run(IgniteSpiThread.java:58)
[ignite-core-2.11.1.jar:2.11.1]
```
From: Thomas Kramer
Sent: Tuesday, February 1, 2022 3:04 AM
To: user@ignite.apache.org
Subject: Warning Exception closing JdbcConnection
CAUTION: This email originated from outside of the organization. Do not click
links or o
Hi,
I am switching from 2.8.1 to 2.12.0 and encounter an issue when closing
thin JDBC connection. This is my test case:
/ public static void main(String[] args) throws Exception//
// {//
// try (Ignite ignite = Ignition.start())//
// {//
// System.out.println("Co
