1)  Please don't double post the same thread. Thanks.
2)  Did you catch RuntimeIOException after ConnectFuture future =
connector.connect()? The reconnect in a infinite loop without Thread.sleep()
normally causes 100% CPU usage.


On 9/8/07, YoungJoon, Chun <[EMAIL PROTECTED]> wrote:
>
> Hello.
>
>
>
> I'm using mina in my server application and the server also uses
> SocketConnector to connect to client in some cases. Sometimes my server
> uses
> CPU up to 100% and I found out that
>
> when SocketConnector connects to an address which is not reachable
> (machine
> is off), it just use up all cpu resource after some time trying to connect
> (eg. 30 seconds).
>
>
>
> A simple test application that uses SocketConnector also has same problem.
> 1
> connection uses 50% cpu and
>
> 2 or more connections more cpu %.
>
>
>
> The weird thing is even though machine is off and the address is not
> reachable (no route to host with telnet), connection handler's (instance
> of
> SingleSessionIoHandler) sessionOpened() method is called, though no
> further
> progress. And setConnectTimeout() does not work and ConnectFuture is not
> getting notified as well.
>
>
>
> My debugging shows SocketIoProcessor thread seems to be the cause.
> Couldn't
> figure out the detail yet.
>
> Anyone is having the same problem with me?
>
>
>
> I'm using mina 2.0 trunk (from maven repository) and java 1.6u2, Windows
> XP
> SP2.
>
> Thanks.
>
>
>
>

Reply via email to