Hello,
Looking further into this issue, I found out that the server has 2
network cards with teaming - load balancing - turned on.
Could this lead be the cause ? Is this a windows, java or windows issue ?
- Ron
rzo wrote:
Hello,
I am currently using mina on many different servers.
On one specific server (windows) I keep getting the following
exception on NioSocketAcceptor.bind():
INFO|6348/0|09-08-23 21:38:16|java.net.SocketException: Socket
operation on nonsocket: socket
INFO|6348/0|09-08-23 21:38:16| at sun.nio.ch.Net.socket0(Native Method)
INFO|6348/0|09-08-23 21:38:16| at
sun.nio.ch.Net.serverSocket(Net.java:98)
INFO|6348/0|09-08-23 21:38:16| at
sun.nio.ch.ServerSocketChannelImpl.<init>(ServerSocketChannelImpl.java:73)
INFO|6348/0|09-08-23 21:38:16| at
sun.nio.ch.SelectorProviderImpl.openServerSocketChannel(SelectorProviderImpl.java:33)
INFO|6348/0|09-08-23 21:38:16| at
java.nio.channels.ServerSocketChannel.open(ServerSocketChannel.java:75)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:233)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.transport.socket.nio.NioSocketAcceptor.open(NioSocketAcceptor.java:49)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.core.polling.AbstractPollingIoAcceptor.registerHandles(AbstractPollingIoAcceptor.java:513)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.core.polling.AbstractPollingIoAcceptor.access$200(AbstractPollingIoAcceptor.java:67)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.core.polling.AbstractPollingIoAcceptor$Acceptor.run(AbstractPollingIoAcceptor.java:400)
INFO|6348/0|09-08-23 21:38:16| at
org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:65)
INFO|6348/0|09-08-23 21:38:16| at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
INFO|6348/0|09-08-23 21:38:16| at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
INFO|6348/0|09-08-23 21:38:16| at java.lang.Thread.run(Thread.java:619)
given that I am calling bind in a loop, this exception may repeat
itself for a few minutes and then the bind succeeds.
on occasion it may take hours for the bind to succeed.
I searched the internet for this exception but did not find a reason.
Any help or hint to solve this issue or any workaround will be highly
appreciated.
Would a switch to AprSocketAcceptor help ?
- Ron
http://yajsw.sourceforge.net
