[
https://issues.jboss.org/browse/JBWS-3497?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3497:
---------------------------------------
OK, with this fix you can provide a jboss-webservices.xml descriptor as follows in your
deployment and have the default CXF work queue configured accordingly:
{code:xml}
<?xml version="1.1" encoding="UTF-8"?>
<webservices
xmlns="http://www.jboss.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1.2"
xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee">
<property>
<name>cxf.queue.default.maxQueueSize</name>
<value>500</value>
</property>
<property>
<name>cxf.queue.default.highWaterMark</name>
<value>300</value>
</property>
...
</webservices>
{code}
Documentation on the configurable options coming soon.
This of course removes the need of using the jbossws-cxf.xml spring based approach.
Add ability to configure the queue depth on the asynchronous
(@Oneway) work queue.
----------------------------------------------------------------------------------
Key: JBWS-3497
URL:
https://issues.jboss.org/browse/JBWS-3497
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Affects Versions: jbossws-cxf-4.0.2
Environment: Linux 64 bit.
Reporter: Jeremy Whiting
Assignee: Alessio Soldano
Priority: Critical
Fix For: jbossws-cxf-4.1
I need to increase the queue depth on a thread pool. The underlying CXF implementation
is throwing a WARNING indicating the queue is full and the callee thread will have to
execute the work. When this occurs performance is degraded.
I would like to see the thread pool configuration exposed to allow the setting of
executor queue depth
worker thread count
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira