title: Why blocking weblogic.socket.Muxer Threads are acceptable in webogic?
body: <p>Ιs it really a blocking issue in my Application?</p>
  
  <p><code>weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:92)</code> shows blocking in thread analyzer , is it really a blocking thread I should worry about?</p>
  
  <pre><code>ExecuteThread: '3' for queue: 'weblogic.socket.Muxer'"   daemon prio=3 tid=0x0000000101f38000 nid=0x38 waiting for monitor entry [0xfffffffe40dff000]      
  java.lang.Thread.State: BLOCKED (on object monitor)      at 
  weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:92)      - 
  waiting to lock &lt;0xfffffffe70ec4898&gt; (a java.lang.String)      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)
  </code></pre>
  
  <p>EDIT: </p>
  
  <p>I got a <a href="http://web.archive.org/web/20120305055218/http://www.bea-weblogic.com/is-it-normal-to-see-blocked-weblogic-socket-muxer-threads.html" rel="nofollow">link</a> explaining answer ( Which says its not an issue) but Not sure what purpose can a blocked Thread serve ? Why it is designed in this way?
  So changing title of question as below</p>
  
  <p>Old Title- weblogic.socket.DevPollSocketMuxer.processSockets shows blocking in thread analyzer , is it really a blocking thread I should worry about?</p>
  
  <p>New Title -Why blocking weblogic.socket.Muxer Threads are acceptable ? What purpose will it serve?</p>