You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@ignite.apache.org by Ankit Singhai <an...@gmail.com> on 2017/04/21 11:44:30 UTC

With same load Ignite is not able to respond after enabling SSL

Hi All,
We have 3 servers and 10 clients in topology, wherein all use-cases are on
Ignite Cache. Load is round 40K cache operations / min i.e. Create, Read,
Update and Delete but after enabling SSL we are getting below exceptions
(which was working earlier with out SSL).


[07:25:15] (err) Failed to execute compound future reducer:
GridNearGetFuture [tx=null, ver=GridCacheVersion [topVer=104236831,
time=1492773516157, order=1492771941620, nodeOrder=23],
innerFuts=[[node=292ba740-8376-4ecc-a836-31e222be7c9e, loc=false,
done=true]], super=GridCompoundIdentityFuture [super=GridCompoundFuture
[rdc=Map reducer: {}, initFlag=0, lsnrCalls=0, done=false, cancelled=false,
err=null, futs=[true]]]]class org.apache.ignite.IgniteCheckedException:
Failed to send message (node may have left the grid or TCP connection cannot
be established due to firewall issues) [node=TcpDiscoveryNode
[id=292ba740-8376-4ecc-a836-31e222be7c9e, addrs=[10.179.29.136],
sockAddrs=[in1s5xraai002.ivycomptech.co.in/10.179.29.136:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1492771286410,
loc=false, ver=1.8.0#20161205-sha1:9ca40dbe, isClient=false],
topic=TOPIC_CACHE, msg=GridNearGetRequest
[futId=a382d109b51-0e611836-1099-4aef-8fc5-4db1230b4a99,
miniId=b382d109b51-0e611836-1099-4aef-8fc5-4db1230b4a99,
ver=GridCacheVersion [topVer=104236831, time=1492773516157,
order=1492771941620, nodeOrder=23], keyMap=null, reload=false,
readThrough=true, skipVals=false, topVer=AffinityTopologyVersion [topVer=25,
minorTopVer=4], subjId=ccc10d0d-3e3f-41e0-8d24-0ab2272cc8f9, taskNameHash=0,
accessTtl=86400000], policy=2]
        at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1153)
        at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1217)
        at
org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:910)
        at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.map(GridNearGetFuture.java:384)
        at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.init(GridNearGetFuture.java:162)
        at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.loadAsync(GridNearCacheAdapter.java:272)
        at
org.apache.ignite.internal.processors.cache.distributed.near.GridNearAtomicCache.getAllAsync(GridNearAtomicCache.java:417)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.getAsync(GridCacheAdapter.java:1737)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4800)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4783)
        at
org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1395)
        at
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.get(IgniteCacheProxy.java:1118)
        at
com.pg.partner.loginservice.cache.PartnerTokenCacheManager.getPartnerToken(PartnerTokenCacheManager.java:62)
        at
com.pg.partner.loginservice.impl.PartnerLoginServiceImpl.generatePartnerToken(PartnerLoginServiceImpl.java:185)
        at sun.reflect.GeneratedMethodAccessor67.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at
com.partygaming.serviceregistry.SRRemoteInvocation.invoke(SRRemoteInvocation.java:189)
        at
com.partygaming.serviceregistry.resolver.AbstractServiceResolver.executeOnService(AbstractServiceResolver.java:1259)
        at
com.partygaming.serviceregistry.exportimport.RemoteServiceRegistryImpl.execute(RemoteServiceRegistryImpl.java:17)
        at sun.reflect.GeneratedMethodAccessor66.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
        at sun.rmi.transport.Transport$1.run(Transport.java:177)
        at sun.rmi.transport.Transport$1.run(Transport.java:174)
        at java.security.AccessController.doPrivileged(Native Method)
        at sun.rmi.transport.Transport.serviceCall(Transport.java:173)
        at
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:556)
        at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:811)
        at
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:670)
        at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:744)
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to send
message to remote node: TcpDiscoveryNode
[id=292ba740-8376-4ecc-a836-31e222be7c9e, addrs=[10.179.29.136],
sockAddrs=[in1s5xraai002.ivycomptech.co.in/10.179.29.136:47500],
discPort=47500, order=1, intOrder=1, lastExchangeTime=1492771286410,
loc=false, ver=1.8.0#20161205-sha1:9ca40dbe, isClient=false]
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2017)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:1955)
        at
org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1148)
        ... 33 more
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to connect
to node (is node still alive?). Make sure that each ComputeTask and cache
Transaction has a timeout set in order to prevent parties from waiting
forever in case of network issues
[nodeId=292ba740-8376-4ecc-a836-31e222be7c9e,
addrs=[in1s5xraai002.ivycomptech.co.in/10.179.29.136:9090]]
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2521)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2161)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2055)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.access$4600(TcpCommunicationSpi.java:239)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.processDisconnect(TcpCommunicationSpi.java:3236)
        at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$CommunicationWorker.body(TcpCommunicationSpi.java:3116)
        at
org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
        Suppressed: class org.apache.ignite.IgniteCheckedException: Failed
to connect to address: in1s5xraai002.ivycomptech.co.in/10.179.29.136:9090
                at
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2526)
                ... 6 more
        Caused by: java.lang.NullPointerException
                at
org.apache.ignite.internal.util.nio.GridNioRecoveryDescriptor.ackReceived(GridNioRecoveryDescriptor.java:195)
                at
org.apache.ignite.internal.util.nio.GridNioRecoveryDescriptor.onHandshake(GridNioRecoveryDescriptor.java:278)

Any help on what might be causing this?



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/With-same-load-Ignite-is-not-able-to-respond-after-enabling-SSL-tp12146.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: With same load Ignite is not able to respond after enabling SSL

Posted by Anton Vinogradov <av...@apache.org>.

Hi,

I see that code from stack trace you provided was refactored at 1.9,
possible this will fix your issue.

On Fri, Apr 21, 2017 at 3:00 PM, Ankit Singhai <an...@gmail.com> wrote:

> igniteClient.gz
> <http://apache-ignite-users.70518.x6.nabble.com/file/
> n12149/igniteClient.gz>
> server1.gz
> <http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server1.gz>
> server2.gz
> <http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server2.gz>
> server3.gz
> <http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server3.gz>
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/With-same-load-Ignite-is-not-able-to-
> respond-after-enabling-SSL-tp12146p12149.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: With same load Ignite is not able to respond after enabling SSL

Posted by Ankit Singhai <an...@gmail.com>.

igniteClient.gz
<http://apache-ignite-users.70518.x6.nabble.com/file/n12149/igniteClient.gz>  
server1.gz
<http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server1.gz>  
server2.gz
<http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server2.gz>  
server3.gz
<http://apache-ignite-users.70518.x6.nabble.com/file/n12149/server3.gz>  



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/With-same-load-Ignite-is-not-able-to-respond-after-enabling-SSL-tp12146p12149.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.