Gatling 1.5.6 , Increase in number of users over 400 fails with this exception

When I increase the number of users above 400 and 150 repititions, then approximately half the calls fail (~3149) with the following stack trace, any ideas? We’re using Gatling 1.5.6.

Thanks
-Narayan-

17:20:26.790 [DEBUG] c.n.h.c.p.n.NettyAsyncHttpProvider - Channel Closed: [id: 0x1d8c8bd2, /10.190.191.15:56970 :laughing: callbackstress.api.dev.digby.com/173.203.62.100:443] with attachment com.ning.http.client.providers.netty.NettyAsyncHttpProvider$DiscardEvent@671b1201

17:20:26.790 [DEBUG] o.j.n.h.s.SslHandler - Failed to clean up SSLEngine.

javax.net.ssl.SSLException: Inbound closed before receiving peer’s close_notify: possible truncation attack?

at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) ~[na:1.6]

at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1447) ~[na:1.6]

at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1415) ~[na:1.6]

at com.sun.net.ssl.internal.ssl.SSLEngineImpl.closeInbound(SSLEngineImpl.java:1354) ~[na:1.6]

at org.jboss.netty.handler.ssl.SslHandler.closeEngine(SslHandler.java:657) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.handler.ssl.SslHandler.channelDisconnected(SslHandler.java:649) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.Channels.fireChannelDisconnected(Channels.java:396) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.AbstractNioWorker.close(AbstractNioWorker.java:360) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:93) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:108) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89) ~[netty-3.9.2.Final.jar:na]

at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) ~[netty-3.9.2.Final.jar:na]

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [na:1.6.0_65]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [na:1.6.0_65]

at java.lang.Thread.run(Thread.java:695) [na:1.6.0_65]

It probably means that your server’s SSL engine is bogus.

Hi Stephane,

Thanks! This is our DEV environment. Could you please elaborate, how do we fix this? Any pointers?

-Narayan-

Hi Stephane,

So, if we fix it using instructions provided here: http://tomcat.apache.org/tomcat-6.0-doc/ssl-howto.html
I am assuming this exception would go away? Point is … why does it work for the other 50%? I can understand if it fails for all the calls?! A bit confused!

Thanks
-Narayan-

Well, I’m willing to help people with Gatling issues, but I don’t do consulting for free…
The problem could be in several places, from old JDK or old Tomcat bug to network failures.

Thanks!

Hello Narayan,

I’ve got similar issue today - Did you get around this issue? If yes can you please explain.

Thanks
Jhansi