Socket client error, broken pipe about mod-redis HOT 7 CLOSED

Can you detail a bit more, does this mean that you had a open connection for weeks and today you got this exception? Or you started now your application and start seeing this exception?

from mod-redis.

The former.
I have never seen this error before. The http server has been running
weeks, then the redis module threw the exception. Is it to do with the
temporary network outage, or something else? Could you tell me some
typical scenario, please? Thank you. -Uppsax

On 30 May 2014 14:10, Paulo Lopes [email protected] wrote:

Can you detail a bit more, does this mean that you had a open connection
for weeks and today you got this exception? Or you started now your
application and start seeing this exception?

—
Reply to this email directly or view it on GitHub
#20 (comment).

from mod-redis.

Yes the only case I can expect a broken pipe is with a network outage, I can try to see how complex is to mark the connection as broken and try to recover the link on this exception. I cannot make any guarantees on retries

from mod-redis.

As an experiment, I make redis module to access localhost redis, and then
killed the redis process. What I got looks different from the one before:

[vert.x-eventloop-thread-0] 2014-05-30T15:03:50.715+01:00 INFO
[io.vertxmod-redis1.1.4-SNAPSHOT-io.vertx.redis.RedisMod-1078596280]
Socket closed

[vert.x-eventloop-thread-0] 2014-05-30T15:03:52.921+01:00 INFO
[io.vertxmod-redis1.1.4-SNAPSHOT-io.vertx.redis.RedisMod-1078596280] Got
request when disconnected. Trying to connect.

[vert.x-eventloop-thread-0] 2014-05-30T15:03:52.924+01:00 SEVERE
[io.vertxmod-redis1.1.4-SNAPSHOT-io.vertx.redis.RedisMod-1078596280] Net
client error

java.net.ConnectException: Connection refused: localhost/127.0.0.1:6379

    at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)

    at

sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:692)

    at

io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:191)

    at

io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:228)

    at

io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:497)

    at

io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:447)

    at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:341)

    at

io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:101)

    at java.lang.Thread.run(Thread.java:722)

[vert.x-eventloop-thread-0] 2014-05-30T15:03:52.935+01:00 SEVERE
[io.vertxmod-redis1.1.4-SNAPSHOT-io.vertx.redis.RedisMod-1078596280]
Unable to connect

The former was java.io.IOException: Broken pipe, and this time was
java.net.ConnectException.

If I can be notified the outage by redis module, that would be great.
Thank you.

-Uppsax

On 30 May 2014 14:21, Paulo Lopes [email protected] wrote:

Yes the only case I can expect a broken pipe is with a network outage, I
can try to see how complex is to mark the connection as broken and try to
recover the link on this exception. I cannot make any guarantees on retries

—
Reply to this email directly or view it on GitHub
#20 (comment).

from mod-redis.

those are 2 different errors, broken pipe means that you were connected and then something happen and the connection between the module and redis server broken.

The later means that you do not have redis running at all locally, which could mean that before what caused the connection to break was that the server got removed or shutdown from your system...

from mod-redis.

So if I see broken pipe, it is not about the connection with the local
redis, because there will be no network outage with localhost... am I right?

If I so, the broken pipe I saw was definitely about the network outage with
outside its VM?

Thank you.
-Uppsax

On 30 May 2014 15:23, Paulo Lopes [email protected] wrote:

those are 2 different errors, broken pipe means that you were connected
and then something happen and the connection between the module and redis
server broken.

The later means that you do not have redis running at all locally, which
could mean that before what caused the connection to break was that the
server got removed or shutdown from your system...

—
Reply to this email directly or view it on GitHub
#20 (comment).

from mod-redis.

relates to #23

from mod-redis.