Hello! I would suggest regular (or DEBUG) Ignite logs + SSL debug logs.
https://docs.oracle.com/javase/7/docs/technotes/guides/security/jsse/ReadDebug.html Regards, -- Ilya Kasnacheev пт, 19 окт. 2018 г. в 20:58, Loredana Radulescu Ivanoff <lradu...@tibco.com >: > Definitely - do you want debug logs, and if yes, should I enable them on > all Ignite packages, or just for certain ones? Any other diagnostic flags > that I should set? > > On Fri, Oct 19, 2018 at 7:48 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > >> Hello! >> >> Apache Ignite does not claim support JDK 11 at this moment. However, I >> was able to run SSL test (TcpDiscoverySslTrustedUntrustedTest) and it >> turned out mostly fine. >> >> More info is needed from your side, such as full instances logs. >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пт, 19 окт. 2018 г. в 0:56, Loredana Radulescu Ivanoff < >> lradu...@tibco.com>: >> >>> Hello, >>> >>> I can consistently reproduce this issue with Ignite 2.6.0, JDK 11 and >>> SSL enabled: >>> >>> >>> - the second node that I bring up joins, and then shortly after >>> freezes and prints this message every minute: >>> >>> "WARN ...[*Initialization*] >>> processors.cache.GridCachePartitionExchangeManager: Still waiting for >>> initial partition map exchange" >>> >>> >>> - once the second node joins, the first node starts experiencing >>> very frequent 100% CPU spikes; these are the messages I see: >>> >>> WARN 2018-10-18T13:50:52,728-0700 [] >>> communication.tcp.TcpCommunicationSpi: Communication SPI session write >>> timed out (consider increasing 'socketWriteTimeout' configuration property) >>> [remoteAddr=/10.100.36.82:51620, writeTimeout=15000] >>> WARN 2018-10-18T13:50:52,737-0700 [] >>> communication.tcp.TcpCommunicationSpi: Failed to shutdown SSL session >>> gracefully (will force close) [ex=javax.net.ssl.SSLException: Incorrect SSL >>> engine status after closeOutbound call [status=OK, >>> handshakeStatus=NEED_WRAP, >>> WARN 2018-10-18T13:51:01,441-0700 [] >>> dht.preloader.GridDhtPartitionsExchangeFuture: Unable to await partitions >>> release latch within timeout: ServerLatch [permits=1, >>> pendingAcks=[aeba8bb7-c9b8-4d46-be8a-df361eaa8fc5], super=CompletableLatch >>> [id=exchange, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0]]] >>> >>> Other observations: >>> >>> I can reproduce this every time I start the nodes, and it doesn't matter >>> which node comes up first. >>> >>> >>> The issue goes away if I disable SSL. >>> >>> >>> Increasing the socketWriteTimeout, networkTimeout or the >>> failureDetectionTimeout does not help. >>> >>> It seems to be happening only with JDK 11, and not with JDK 8. >>> >>> >>> Do you have any suggestions/known issues about this? >>> >>> Thank you, >>> >>> Loredana >>> >>> >>> >>> >>>
