You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by cververs <cv...@thoughtworks.com> on 2009/03/28 16:24:06 UTC
CXF JMS WebSphere 6.1 - client loses connection
Hi,
We're using CXF 2.1.2 in WebSphere 6.1 to access services over Tibco EMS.
We'd like to instantiate clients (using the generated code from WSDLs). The
client creation takes a few seconds (because of parsing the WSDLs), so we'd
like to keep them around for the various user sessions to invoke rather than
recreate them for every invocation.
If we configure the WSDLs to connect directly to TIBCO, this works
beautifully. Once we switch to the WS JMS connection factory, the problems
start. WS cuts off the connection because it has these connection pools. So
we HAVE to recreate the clients at every invocation, slowing down the user
experience.
Any advice on how to tackle this, e.g. settings on the WS connection pools,
CXF settings or implementing the cleints diferently so they do not have to
read the entire WSDLs?
Thanks!
--
View this message in context: http://www.nabble.com/CXF-JMS-WebSphere-6.1---client-loses-connection-tp22757975p22757975.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: CXF JMS WebSphere 6.1 - client loses connection
Posted by Daniel Kulp <dk...@apache.org>.
The 2.1.5 snapshots (and the 2.2 release version) has a new JMS transport
based on Spring JMS. One of the things this DOES have is a reconnect on
failure setting for the JMS transport. Thus, if the connection goes down,
the client will automatically try to reconnect to the broker. Might be
worth looking into upgrading.
Dan
On Sat March 28 2009 11:24:06 am cververs wrote:
> Hi,
>
> We're using CXF 2.1.2 in WebSphere 6.1 to access services over Tibco EMS.
> We'd like to instantiate clients (using the generated code from WSDLs). The
> client creation takes a few seconds (because of parsing the WSDLs), so we'd
> like to keep them around for the various user sessions to invoke rather
> than recreate them for every invocation.
>
> If we configure the WSDLs to connect directly to TIBCO, this works
> beautifully. Once we switch to the WS JMS connection factory, the problems
> start. WS cuts off the connection because it has these connection pools. So
> we HAVE to recreate the clients at every invocation, slowing down the user
> experience.
>
> Any advice on how to tackle this, e.g. settings on the WS connection pools,
> CXF settings or implementing the cleints diferently so they do not have to
> read the entire WSDLs?
>
> Thanks!
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog