In the Talend Runtime container, the default configuration
file is in
Note this file is normally not used or edited directly; it gives workqueue default values that each CXF-using bundle can choose to employ when it creates its work queues.
To configure a workqueue, there is a specific corresponding file:
org.apache.cxf.workqueues-n.cfg, where typically "n" is the same as
the workqueue name; for example,
org.apache.cxf.workqueues-http-conduit.cfg would configure the
http-conduit workqueue. At the moment, this functionality is for pre-defined work
queues; it is not possible to use it for user-defined workqueues.
Here is the list of pre-defined workqueue names:
|default||this means using the default values.|
|http-conduit||On the client side when using the asynchronous methods, the HTTP conduit must wait for and process the response on a background thread. This can control the queue that is used specifically for that purpose, to limit or expand the number of outstanding asynchronous requests.|
|jms-continuation||This is used by the JMS transport to handle continuations.|
|local-transport||The local transport being based on PipedInput/OutputStreams requires the use of separate threads; this workqueue can be used to configure the queue used exclusively for the local-transport.|
|ws-addressing||For decoupled cases, the ws-addressing layer may need to process the request on a background thread. This can control the workqueue it uses.|
You can also update these variables (for example
using the standard Karaf configuration commands.