PosixSocketMuxer: unexpected exception in poll: (22) Invalid argument

Question

I'm running JDeveloper 12.x using WLS 12.1.1.0.0. The server starts fine, but when I launch the WLS console, the web browser appears (deploying WLS console...) then goes blank. The WLS console has repeated this exception:
<Oct 10, 2011 6:03:32 PM MDT> <Error> <Socket> <BEA-000421> <Uncaught Throwable in processSockets
java.io.IOException: unexpected exception in poll: (22) Invalid argument.
java.io.IOException: unexpected exception in poll: (22) Invalid argument
     at weblogic.socket.PosixSocketMuxer.poll(Native Method)
     at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:106)
     at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
     at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
     Truncated. see log file for complete stacktrace
I'm running Mac OS 10.6.7 in 64-bit mode.
There is no additional stack trace information in the server or the default domain log.
Is there any way around this? Can I edit something in config.xml or startWebLogic.sh as a workaround?

Answer 1

Some notes concerning running WebLogic on Max OS are presented, maybe they help - http://blogs.oracle.com/wahmed/entry/installing_weblogics_10_3_1
Looking at the error "java.io.IOException: unexpected exception in poll: (22) Invalid argument at weblogic.socket.PosixSocketMuxer.poll(Native Method)"
which is related to the socket muxer. By default, a native socket muxer is used - could be this is not working on MAC.
What you can try to do is enable the Java based muxer, by editing the config.xml, for example,
<server>
    <name>AdminServer</name>
    <reverse-dns-allowed>false</reverse-dns-allowed>
    <native-io-enabled>false</native-io-enabled>
    <thread-pool-percent-socket-readers>33</thread-pool-percent-socket-readers>
    <ssl>
      <login-timeout-millis>25000</login-timeout-millis>
    </ssl>
    <max-open-sock-count>-1</max-open-sock-count>
    <stuck-thread-max-time>600</stuck-thread-max-time>
    <stuck-thread-timer-interval>60</stuck-thread-timer-interval>
    <gathered-writes-enabled>false</gathered-writes-enabled>
    <scattered-reads-enabled>false</scattered-reads-enabled>
    <listen-address></listen-address>
    <accept-backlog>300</accept-backlog>
    <login-timeout-millis>5000</login-timeout-millis>
    <low-memory-time-interval>3600</low-memory-time-interval>
    <low-memory-sample-size>10</low-memory-sample-size>
    <low-memory-granularity-level>5</low-memory-granularity-level>
    <low-memory-gc-threshold>5</low-memory-gc-threshold>
</server>The native-io-enabled element controls is the native muxer is enabled or not.
The thread-pool-percent-socket-readers element tells how may threads from the execute queue
are used by the muxer; the default is 33%.