2 Replies Latest reply: Jul 2, 2008 9:30 AM by 666705 RSS

    SocketException BEA-101083 Weblogic 9.2

    666705
      Hi,

      we are facing a problem in our production environment, we get pratically every minutes the following exception :

      <30 juin 2008 10 h 27 CEST> <Error> <HTTP> <BEA-101083> <Connection failure.
      java.net.SocketException: Error in poll for fd=287, revents=32
           at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:133)
           at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
           at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
           at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
           at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
      >

      What can be the cause of this ? Our users are telling us that the application goes very slow and this is the only abnormal log that we found.

      Thank you,
      Quentin Anciaux

      <quentin.anciaux@touring.be>
        • 1. Re: SocketException BEA-101083 Weblogic 9.2
          666705
          This might point to some network issues in your environment.

          How often do you see this message and what is the volume of incoming requests?

          Regards,
          /Raj
          • 2. Re: SocketException BEA-101083 Weblogic 9.2
            666705
            Hi, the problem happens pratically once or two per minute while the application is in use... when the application is not used, no error happens.

            So it happens very often... I thought it could be a problem with a proxy/firewall in the middle, but according to the guys in charge of this, nothing has changed on his side.

            I've read things about a possible bug in the nativeIO implementation, would it be safe to deactivate nativeIO to see if this bug arise with pure java socket ?

            Also this problem only occurs in our production environment, we have 4 others environment used for testing/training/integration and this error does not occur there.

            Thanks for any help,
            Quentin Anciaux