Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Tool doesn't seem to be working. #2

Open
pveentjer opened this issue Nov 9, 2018 · 0 comments
Open

Tool doesn't seem to be working. #2

pveentjer opened this issue Nov 9, 2018 · 0 comments

Comments

@pveentjer
Copy link

pveentjer commented Nov 9, 2018

Hi Nitsan,

I'm trying your tool in EC2 and can't seem to get it working.

on server:
java -jar lib/java-ping.jar -client -select 10.0.0.228 5701 1
java -jar lib/java-ping.jar -server -block 10.0.0.228 5701

On the client I can see:

[simulator@ip-10-0-0-73 ~]$ java -jar lib/java-ping.jar -client -select 10.0.0.228 5701 1
Pinging 10.0.0.228:5701 messages of size 1
Min,50%,90%,99%,99.9%,99.99%,Max

But nothing happens.

I can see they are connecting. If I insert a wrong address on the client I get an error. And if I terminate while the client is 'freezing' the client throws an exception.

There are no firewall issues. I can run simulator (java based benchmark/soak test environment) on the environment without problems. I explicitly set the ports since I know these are open.

When I place both client and server in -block mode and kill the server when the client is connecting, the client starts to output

[simulator@ip-10-0-0-73 ~]$ java -jar lib/java-ping.jar -client -block 10.0.0.228 5701 1
Pinging 10.0.0.228:5701 messages of size 1
Min,50%,90%,99%,99.9%,99.99%,Max
@290,307,316,86119,101210,160963,2529405
@294,307,313,321,377,11215,17564
@295,308,313,321,331,6231,44325
@300,312,320,326,336,5563,17103
@300,312,318,326,345,11156,17879
@301,312,316,325,333,5475,68306
@299,312,316,325,333,5595,19332
@300,312,318,326,335,11244,17198
@300,312,316,325,335,11106,41112
@301,312,320,326,335,6109,18175
@300,312,316,325,332,5342,17111
@300,312,316,325,333,11126,37548
@300,312,316,325,338,10952,17520
@300,312,320,326,336,11216,22149
@300,312,317,325,333,5568,18147
@301,312,317,326,350,11310,18878
@300,312,319,326,338,11415,20731
@299,312,316,325,332,5349,17109
@301,312,316,325,334,11103,18128
@300,312,318,326,342,10962,36726
@300,312,317,325,334,11197,20350
@300,312,317,325,335,11214,17853
@300,312,316,325,333,5393,34899
@300,312,316,325,332,11129,17714
@300,312,317,325,334,5502,17103
@299,312,317,325,337,11076,17935
@300,312,316,325,333,5355,17132
@301,312,318,326,337,11113,18525
@300,312,316,325,334,5524,33918
@300,312,317,325,336,11163,21493

Even though the java server has been killed with a 'killall -9 java'. So there is nothing running but the client is still reporting latencies

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant