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

[Alan Bateman]

On 30/08/2012 05:39, Earle Nietzel wrote:
> 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
>
This is interesting because UseVMInterruptibleIO was Solaris specific 
(and so is news to me that legacy interruptible I/O was implemented on 
Mac). As background, we have been trying to eliminate this for many 
years. The UseVMInterruptibleIO option was added in jdk6 to allow 
developers on Solaris to disable it and check that their applications 
still ran, then in jdk7 the default value of the option was changed to 
disabled it by default. The original plan was to completely remove it at 
some point too.

-Alan.