[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{noformat}
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
{noformat}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{noformat}
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
{noformat}
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{code:java}
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
{code}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{noformat}
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
{noformat}
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{code:java}
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
{code}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{{
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
}}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{code:java}
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
{code}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{noformat}
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
{noformat}
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{code:java}
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
{code}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{{"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)}}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{{
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
}}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
{{"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)}}
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
{{
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745 }}
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9482) ejb remote client hangs on undertow default worker pool exhaustion
by Igor Vagulin (JIRA)
[ https://issues.jboss.org/browse/WFLY-9482?page=com.atlassian.jira.plugin.... ]
Igor Vagulin updated WFLY-9482:
-------------------------------
Steps to Reproduce:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests. No thread to make following
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
was:
>Steps to reproduce
- get 2 jboss instances: destination and client
- setup ejb-remoting according to article "https://docs.jboss.org/author/display/WFLY10/EJB+invocations+from+a+remot..."
- install to destination .ear with remotely accessible slsb, doing Thread.sleep(1000)
- install to client .war with servlet calling method
- make lot (>300) of concurrent get request to servlet using some bench tool (e.g. https://github.com/wg/wrk)
>Actual results
Servlet hang, all threads waiting for responses like this:
"default task-40" #331 prio=5 os_prio=0 tid=0x00007f2d7c256800 nid=0x1bf6 in Object.wait() [0x00007f2ca2db2000]
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 <0x00000000d6253958> (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)
> Expected result:
No hang
> Additional info
AFAICU ejb-client need spare thread in default xnio worker to process responses. all threads occupied by processing of servlet requests
EJBClientInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 313
EJBReceiverInvocationContext.resultReady(EJBReceiverInvocationContext$ResultProducer) line: 73
ChannelAssociation.resultReady(short, EJBReceiverInvocationContext$ResultProducer) line: 241
MethodInvocationResponseHandler.processMessage(InputStream) line: 82
ChannelAssociation.processResponse(InputStream) line: 395
ChannelAssociation$ResponseReceiver.handleMessage(Channel, MessageInputStream) line: 507
RemoteConnectionChannel$5.run() line: 456
EndpointImpl$TrackingExecutor$1.run() line: 731
XnioWorker$TaskPool(ThreadPoolExecutor).runWorker(ThreadPoolExecutor$Worker) line: 1142
ThreadPoolExecutor$Worker.run() line: 617
Thread.run() line: 745
> ejb remote client hangs on undertow default worker pool exhaustion
> ------------------------------------------------------------------
>
> Key: WFLY-9482
> URL: https://issues.jboss.org/browse/WFLY-9482
> Project: WildFly
> Issue Type: Bug
> Components: Remoting
> Affects Versions: 10.1.0.Final
> Reporter: Igor Vagulin
> Assignee: David Lloyd
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9456) High non heap memory consumption
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFLY-9456?page=com.atlassian.jira.plugin.... ]
David Lloyd resolved WFLY-9456.
-------------------------------
Resolution: Rejected
The issue was fixed by updating the JDK.
> High non heap memory consumption
> --------------------------------
>
> Key: WFLY-9456
> URL: https://issues.jboss.org/browse/WFLY-9456
> Project: WildFly
> Issue Type: Bug
> Components: Class Loading
> Affects Versions: 11.0.0.CR1, 11.0.0.Final
> Environment: CentOS 7 on Google compute engine VM
> openjdk version "1.8.0_144"
> OpenJDK Runtime Environment (build 1.8.0_144-b01)
> OpenJDK 64-Bit Server VM (build 25.144-b01, mixed mode)
> Reporter: Klaus Erber
> Assignee: David Lloyd
> Attachments: wf10-nmt.txt, wf11-nmt.txt
>
>
> After a clean install of WF11CR1 without any configuration changes and startup with standalone.sh we see a high memory usage on the system side (about 800 MB).
> Wenn we do the same with WF10Final we see a memory usage of about 210 MB.
> Her are the output auf ps aux:
> wf11
> ke4 1652 14.0 22.1 2863404 *801620* pts/3 Sl+ 14:01 0:07 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
> wf10
> ke4 1836 42.1 5.7 2687744 *209204* pts/2 Sl+ 14:02 0:06 java -D[Standalone] -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
> The result is, that we can only start 3 instances of wildfly 11 on a 3.75 GB VM. The 4th instance crashes the system. In our real scenario (Wildfly instances in docker containers hosting the REST interface for our application) we see about 1 GB memory consumption per backend node.
> The heap and other memory pools not seems to be the reason for this behaviour - see the attached native memory tracking results.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFCORE-3381) CLI, looping over commands/operations
by Kabir Khan (JIRA)
Kabir Khan created WFCORE-3381:
----------------------------------
Summary: CLI, looping over commands/operations
Key: WFCORE-3381
URL: https://issues.jboss.org/browse/WFCORE-3381
Project: WildFly Core
Issue Type: Enhancement
Components: CLI
Reporter: Jean-Francois Denise
Assignee: Jean-Francois Denise
A support similar to Java iteration could be exposed by CLI. By leveraging the variable and the control flow CLI features, a command can be exposed to iterate collections and execute CLI commands/operations for each item present in the collection.
Something like:
for varName in :read-children-names(type=deployment)
echo Manifest file in $varName
attachment display --operation=/deployment=$varName:read-content(path=META-INF/MANIFEST.MF)
done
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months