RE: CXF 3.1.x missing taskExecutor and unmanaged threads

[Andrei Shakirin <as...@talend.com>]

Hi Bjorn,

It is possible now to configure external executor for JMS transport in Bus using "org.apache.cxf.extensions.jms.destination.executor" and/or "org.apache.cxf.extensions.jms.conduit.executor" properties.  Please try CXF 3.2.0-SNAPSHOT.

https://issues.apache.org/jira/browse/CXF-6702
https://github.com/apache/cxf/commit/0336a2399b1980e04372c651368f8718f75a4f14 

Regards,
Andrei.

> -----Original Message-----
> From: Tyla, BHP (Björn) [mailto:bjorn.tyla@apg.nl]
> Sent: Mittwoch, 25. November 2015 15:48
> To: users@cxf.apache.org
> Cc: Christian Schneider
> Subject: RE: CXF 3.1.x missing taskExecutor and unmanaged threads
> 
> Hi Andrei,
> 
> An option to specify a custom taskExecutor would be very much appreciated
> since this issue also blocks the upgrade of the spring framework.
> 
> Regards
> Bjorn
> 
> -----Original Message-----
> From: Andrei Shakirin [mailto:ashakirin@talend.com]
> Sent: dinsdag 24 november 2015 21:36
> To: users@cxf.apache.org
> Cc: Christian Schneider
> Subject: RE: CXF 3.1.x missing taskExecutor and unmanaged threads
> 
> Hi,
> 
> The JMS Transport was refactored from Spring to pure java in CXF 3.0.0.
> You can configure the number of concurrent JMS consumers now using
> concurrentConsumers option in JMS URI:
> jms:queue:ExampleQueueName?concurrentConsumers=15
> 
> AFAIK PollingMessageListenerContainer creates the fixed thread pool based of
> concurrentConsumers setting. Currently it is not possible to set own
> taskExecutor there.
> 
> Christian, do you think we can extend PollingMessageListenerContainer to use
> custom executor?
> 
> Regards,
> Andrei.
> 
> > -----Original Message-----
> > From: Tyla, BHP (Björn) [mailto:bjorn.tyla@apg.nl]
> > Sent: Dienstag, 24. November 2015 12:00
> > To: users@cxf.apache.org
> > Subject: CXF 3.1.x missing taskExecutor and unmanaged threads
> >
> > Hi,
> >
> > I'm trying to upgrade from CXF 2.7.x to 3.1.x. for my spring
> > application running on WebSphere 8.5 that uses SOAP over JMS for long
> > running operations. On 2.7.x I'm using the spring/websphere
> > taskExecutor to correctly integrate with WebSphere to avoid creating
> > unmanaged threads. I also use the thread pool to limit/throttle the number of
> concurrent request.
> >
> > It seems that it is no longer possible to configure a taskExecutor
> > that should be used by CXF/spring. This is an issue within a JEE
> > container since unmanged threads are not allowed and cannot access the JEE
> context.
> >
> > Please advise on how to correctly use CXF 3.1.x with spring in an JEE
> > (WebSphere) environment.
> >
> > Regards,
> > Bjorn
> >
> > De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend
> > bestemd voor de geadresseerde. Wanneer u dit bericht per abuis
> > ontvangt, verzoeken wij u contact op te nemen met de afzender per
> > kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht
> > te vernietigen en de inhoud ervan aan niemand openbaar te maken.
> > Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan
> > wel ontijdige overbrenging van de inhoud van een verzonden
> > e-mailbericht, noch voor daarbij overgebrachte virussen.
> >
> > APG Groep N.V. is gevestigd te Heerlen en is ingeschreven in het
> > handelsregister van de Kamer van Koophandel Limburg onder nummer
> > 14099617
> >
> >
> > The information contained in this e-mail is confidential and may be
> privileged.
> > It may be read, copied and used only by the intended recipient.
> > If you have received it in error, please contact the sender
> > immediately by return e-mail; please delete in this case the e-mail
> > and do not disclose its contents to any person. We don't accept
> > liability for any errors, omissions, delays of receipt or viruses in
> > the contents of this message which arise as a result of e-mail transmission.
> >
> > APG Groep N.V. is registered in the trade register of the Chamber of
> > Commerce Limburg, The Netherlands, registration number: 14099617
> 
> De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor
> de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u
> contact op te nemen met de afzender per kerende e-mail. Verder verzoeken
> wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan
> niemand openbaar te maken.
> Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel
> ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch
> voor daarbij overgebrachte virussen.
> 
> APG Groep N.V. is gevestigd te Heerlen en is ingeschreven in het
> handelsregister van de Kamer van Koophandel Limburg onder nummer
> 14099617
> 
> 
> The information contained in this e-mail is confidential and may be privileged.
> It may be read, copied and used only by the intended recipient.
> If you have received it in error, please contact the sender immediately by
> return e-mail; please delete in this case the e-mail and do not disclose its
> contents to any person. We don't accept liability for any errors, omissions,
> delays of receipt or viruses in the contents of this message which arise as a
> result of e-mail transmission.
> 
> APG Groep N.V. is registered in the trade register of the Chamber
> of Commerce Limburg, The Netherlands, registration number: 14099617