0 Replies Latest reply on Oct 21, 2017 10:24 AM by Igor Vagulin

    default remoting config cause hang on xnio pool exhaustion

    Igor Vagulin Newbie

      Hi All,

       

      Can someone give me advice is default remoting config is really broken or I missing something.

       

      Lets imagine following:

      - I have 2 jboss A and B

      - jboss B have application with remotely accessible slsb

      - jboss A have ui application with servlet calling slsb at B

       

      If my load occupy all threads in default undertow server xnio worker at jboss A remoting will not be able to process replies from jboss B. Replies processing require spare core thread in default worker.

       

      All my threads just hanging with stacks like this:

       

      "default task-214" #516 prio=5 os_prio=0 tid=0x00007f2d9803c000 nid=0x1d64 in Object.wait() [0x00007f2c94c0e000]

        java.lang.Thread.State: WAITING (on object monitor)

      at java.lang.Object.wait(Native Method)

      at java.lang.Object.wait(Object.java:502)

      at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:413)

      - locked <0x00000000d5810ac0> (a java.lang.Object)

      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:204)

      at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)

      at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)

      at com.sun.proxy.$Proxy253.process(Unknown Source)

       

      Currently I am creating additional worker for default undertow server. But maybe I am really missing something.