RMI TCP Accept Loop throws java.net.SocketException: Invalid argument in Native method

[Earle Nietzel]

I can reproduce regularly with using ActiveMQ 5.4.0 (also tried 5.6.0)
on Mac only.

When using multicast discovery the app won't start without
-XX:+UseVMInterruptibleIO.

If I remove the multicast discovery and opt for tcp or nio then don't
need to use -XX:+UseVMInterruptibleIO.

but in either case I am seeing these RMI warnings.

I will come up with a easy way to reproduce it and post.

Earle

On Thu, Aug 30, 2012 at 12:23 AM, Earle Nietzel <earle.nietzel at gmail.com> wrote:
> Hi Greg,
>
> Thanks for the info, though, I am wired on this mac and have the wifi
> turned off.
>
> Earle
>
> On Wed, Aug 29, 2012 at 10:28 PM, Gregg Wonderly <greggwon at gmail.com> wrote:
>> Also, if the socket is being asynchronously closed, it might be related to
>> the "Lion WiFi Constantly Dropping" problem that some people are reporting
>> as still not fixed.
>>
>> View the full discussion for Wifi Constantly Dropping in Lion
>>
>> Gregg Wonderly
>>
>> On Aug 29, 2012, at 9:25 PM, Gregg Wonderly <greggwon at gmail.com> wrote:
>>
>> In many cases, doesn't this come from using a valid (not -1) fd/socket
>> number, but which has been closed?  Is the connection being closed
>> asynchronously from some other code or the remote end?
>>
>> Gregg Wonderly
>>
>> On Aug 29, 2012, at 6:45 PM, Earle Nietzel <earle.nietzel at gmail.com> wrote:
>>
>> Seeing the following Warning multiple times every few seconds.
>>
>> Aug 29, 2012 7:09:26 PM sun.rmi.transport.tcp.TCPTransport$AcceptLoop
>> executeAcceptLoop
>> WARNING: RMI TCP Accept-1099: accept loop for
>> ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=1099] throws
>> java.net.SocketException: Invalid argument
>> at java.net.PlainSocketImpl.socketAccept(Native Method)
>> at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:398)
>> at java.net.ServerSocket.implAccept(ServerSocket.java:522)
>> at java.net.ServerSocket.accept(ServerSocket.java:490)
>> at
>> sun.rmi.transport.tcp.TCPTransport$AcceptLoop.executeAcceptLoop(TCPTransport.java:387)
>> at sun.rmi.transport.tcp.TCPTransport$AcceptLoop.run(TCPTransport.java:359)
>> at java.lang.Thread.run(Thread.java:722)
>>
>>
>> OSX 10.8.1
>>
>> java version "1.7.0_06"
>> Java(TM) SE Runtime Environment (build 1.7.0_06-b24)
>> Java HotSpot(TM) 64-Bit Server VM (build 23.2-b09, mixed mode)
>>
>> The closest thread I found seems to be this one:
>> http://mail.openjdk.java.net/pipermail/bsd-port-dev/2008-December/000229.html
>>
>> No issues when using JAVA 6 JDK's.
>>
>> These warnings appear constantly when working with ActiveMQ 5.4.0, 5.6.0.
>>
>> Forgive for me if this post seems irrelevant to this list :)
>>
>> Earle
>>
>>
>>