Hi,
we have since few days some trouble with connection exceptions. I tried to increase the timeout values in the gatling.conf but it doesn’t matter… Already checked different backend versions of our groupware server but all backend versions have the same connection issues.
Log-Snippet:
What’s your snapshot timestamp (there’s an ongoing issue that prevents maven users to properly detect snapshot updates)?
When you tried to change the connection timeout in gatling.conf, did you properly uncomment the line (remove the leading #)?
What’s your snapshot timestamp (there’s an ongoing issue that prevents maven users to properly detect snapshot updates)?
io.gatling
gatling-core
2.0.0-SNAPSHOT
20140512200538
When you tried to change the connection timeout in gatling.conf, did you properly uncomment the line (remove the leading #)?
I’m only shooting in the dark there.
The only change I can see that could cause this is this one: https://github.com/excilys/gatling/commit/4baff8d333ddc178ab3cb57213ae7ab86ba991e3#diff-d98d97393127b53be0f245c386bed3ed
Do you think you could drop a replacement for gatling-http.jar I’d provide in your local repo ans give it a shop.
Yep just send me the jar and I’ll check this…
It makes no real difference to me 
Any other idea?
So the problem is not with this change, which is for me good news. 
First, are you sure that the problem is not on your side (application, network…)?
I double-checked that but I’m going this test this again. Will switch to a previous build of our groupware server where I know that it worked fine.
Found an another exception :
java.net.ConnectException: Connection timed out: /192.168.32.116:80
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.7.0_55]
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) ~[na:1.7.0_55]
at org.jboss.netty.channel.socket.nio.NioClientBoss.connect(NioClientBoss.java:150) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:105) [netty-3.9.1.Final.jar:na]
… 8 common frames omitted
Wrapped by: java.net.ConnectException: Connection timed out: /192.168.32.116:80 to http://192.168.32.116:80/ajax/tasks?folder=2363&order=desc&columns=1%2C20%2C200%2C202%2C220%2C203%2C300%2C309&session=ba6b240e20b9414cb49ec84ac695d27d&sort=202&action=all
at com.ning.http.client.providers.netty.NettyConnectListener.operationComplete(NettyConnectListener.java:103) ~[async-http-client-1.8.8.jar:na]
at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:418) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.DefaultChannelFuture.setFailure(DefaultChannelFuture.java:380) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioClientBoss.processSelectedKeys(NioClientBoss.java:109) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioClientBoss.process(NioClientBoss.java:79) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:318) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.channel.socket.nio.NioClientBoss.run(NioClientBoss.java:42) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.9.1.Final.jar:na]
at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.9.1.Final.jar:na]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_55]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_55]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_55]
Yeah, but you’re really at socket level here: the connection can’t really be established.
You’re way below Gatling applicative level here, not much we can do, the problem/limit seems to be in your system/network.
OK thank you anyway
Sorry I can’t help more.
Please tell us if you find anything and good luck.