JReactive-8583 does not connect to my server

[JonathanUriel]

JReactive-8583

Hi, I have a problem with my client, this does not go beyond step 16, I think that my problem is in my server, since the client connects to the server, but the server does not respond.

LOG
[INFO ] [26/07/2017 11:59:02,589] ClientJReactive8583#initCliente,54: paso01
[INFO ] [26/07/2017 11:59:02,670] ClientJReactive8583#initCliente,61: paso02
[INFO ] [26/07/2017 11:59:02,681] ClientJReactive8583#initCliente,64: paso03
[INFO ] [26/07/2017 11:59:02,683] ClientJReactive8583#initCliente,71: paso04
[INFO ] [26/07/2017 11:59:02,683] ClientJReactive8583#initCliente,73: paso05
[INFO ] [26/07/2017 11:59:02,685] ClientJReactive8583#initCliente,125: paso13
[INFO ] [26/07/2017 11:59:02,687] ClientJReactive8583#initCliente,127: paso14
76 [main] INFO Iso8583Client - Initializing
[INFO ] [26/07/2017 11:59:03,009] ClientJReactive8583#initCliente,129: paso15
[INFO ] [26/07/2017 11:59:03,009] ClientJReactive8583#initCliente,131: paso16
400 [main] INFO Iso8583Client - Connecting to /127.0.0.1:8082
400 [main] INFO Iso8583Client - Iso8583Client antes de connect , getSocketAddress=/127.0.0.1:8082
739 [nioEventLoopGroup-2-1] INFO Iso8583Client - Client is connected to /127.0.0.1:8082

I share the client and server source code to see if you can check my code and help me, to know what is my problem.

https://drive.google.com/open?id=0B8VKPXMT57DTdFZZX0RjVVVRaW8

Also inside each of these I leave a bash .bat to run the jars, only modify the routes inside the bash so that these run.

First execute the .bat that found in testServerJPOS and execute in cmd C:\Project_path\bat_run_server_jpos.bat to start the server.

After, to execute client, open the project in a IDE and run the client that found in the route src->mx.isban.iso8583.server.main->ClientJReactive8583.java

[mrtechit]

Even i am facing this issue that the client does not send the message, however it is connected to the server.

The issue happens when client.connect("ip",port) is called and i believe a deadlock is created when it tries to
return connect(new InetSocketAddress(host, port));

This could be a bug in netty.

However, what i dont understand is that the IdleEventHandler works fine, and a n/w mgmt msg is sent based on the timeout and received at the listener.