Return-Path: 
 <users-return-28142-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id CBC8B9CAD
	for <apmail-camel-users-archive@www.apache.org>;
 Tue,  3 Apr 2012 21:09:53 +0000 (UTC)
Received: (qmail 47317 invoked by uid 500); 3 Apr 2012 21:09:53 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 47285 invoked by uid 500); 3 Apr 2012 21:09:53 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 47277 invoked by uid 99); 3 Apr 2012 21:09:53 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 21:09:53 +0000
X-ASF-Spam-Status: No, hits=0.7 required=5.0
	tests=NORMAL_HTTP_TO_IP,SPF_NEUTRAL,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Received: from [64.85.173.253] (HELO server.dankulp.com) (64.85.173.253)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Apr 2012 21:09:48 +0000
Received: by server.dankulp.com (Postfix, from userid 5000)
	id 98E35182B34; Tue,  3 Apr 2012 17:09:27 -0400 (EDT)
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.dankulp.com
X-Spam-Level: 
X-Msg-File: /tmp/mailfilter-users@camel.apache.org.xBqLHcmLm3
Received: from dilbert.dankulp.com
 (75-145-250-221-Connecticut.hfc.comcastbusiness.net [75.145.250.221])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by server.dankulp.com (Postfix) with ESMTPSA id 49A8C180328;
	Tue,  3 Apr 2012 17:09:26 -0400 (EDT)
From: Daniel Kulp <dkulp@apache.org>
To: users@camel.apache.org
Cc: Omar Atia <omar.atia@its.ws>
Subject: Re: Jetty server...Performance testing ...
Date: Tue, 03 Apr 2012 17:09:20 -0400
Message-ID: <3817832.N9kd4RuP91@dilbert.dankulp.com>
User-Agent: KMail/4.8.0 (Linux/3.2.2; KDE/4.8.1; x86_64; ; )
In-Reply-To: <0CBB2FB9E35D9C4998B56A2F1BA57B5F15471BD5@EG-MBX1.corp.its.ws>
References: <0CBB2FB9E35D9C4998B56A2F1BA57B5F15471B17@EG-MBX1.corp.its.ws>
 <CAGgTx3jBy0o9RMdwt1UwPSEO1VNG2PK-VEy7f_KLHnXH_dSK5g@mail.gmail.com>
 <0CBB2FB9E35D9C4998B56A2F1BA57B5F15471BD5@EG-MBX1.corp.its.ws>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-Virus-Checked: Checked by ClamAV on apache.org
X-Old-Spam-Status: No, score=-102.9 required=3.0 tests=ALL_TRUSTED,BAYES_00,
	SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.2


In this case, you CAN configure the CXF Jetty instance we use based on =
the=20
config stuff documented at:

http://cxf.apache.org/docs/jetty-configuration.html


(assuming Spring)

However, I'm not sure you need to.   With the more recent versions of J=
etty,=20
the "default" is a maximum of 256 threads in the pool.    A couple of t=
hose=20
are used for their selectors, but you still end up with potentially a l=
ot of=20
threads available.

Dan



On Tuesday, April 03, 2012 04:11:05 PM Omar Atia wrote:
> Is this what you want ?
>=20
> <cxf:cxfEndpoint
> =09    address=3D"http://0.0.0.0:7782/services/JBoss4CBS"
> =09=09id=3D"JBossCBSWS"
> serviceClass=3D"com.huawei.oss.business.intf.webservice.cbs.Boss4CBSI=
nterfa
> ceEndpoint" wsdlURL=3D"JBoss4CBS/Boss4CBSInterfaceService.wsdl">
> =09 =09 <cxf:inInterceptors>
> =09    <ref bean=3D"logginginInterceptor"/>
> =09</cxf:inInterceptors >
>=20
> <cxf:outInterceptors>
> =09    <ref bean=3D"loggingOutInterceptor"/>
> =09</cxf:outInterceptors>
> =09<cxf:properties>
>        <entry key=3D"dataFormat" value=3D"POJO"/>
>        <entry key=3D"setDefaultBus" value=3D"false"/>
>         <entry key=3D"schema-validation-enabled" value=3D"false" />
>      </cxf:properties>
>=20
> </cxf:cxfEndpoint>
>=20
> -----Original Message-----
> From: Raul Kripalani [mailto:raul@fusesource.com]
> Sent: Tuesday, April 03, 2012 7:02 PM
> To: users@camel.apache.org
> Subject: Re: Jetty server...Performance testing ...
>=20
> Hi Omar,
>=20
> I believe the performance you get will depend on the CXF transport yo=
u are
> using. Can you post your CXF JBossCBSWS bean definition?
>=20
> Are you using a Jetty runtime to expose your HTTP endpoints? If so, y=
ou
> may be able to tune your threading parameters according to this page:=

> http://cxf.apache.org/docs/jetty-configuration.html. Jetty behaves
> asynchronously thanks to the Continuations API.
>=20
> Additionally, you can consider splitting your route into segments wit=
h
> different concurrency levels by using SEDA endpoints with the
> concurrentConsumers option.
>=20
> Regards,
>=20
> *Ra=FAl Kripalani*
> *Principal Consultant | FuseSource Corp.
> raul@fusesource.com | fusesource.com <http://www.fusesource.com/>
> skype: raul.fuse | twitter: @raulvk <http://twitter.com/raulvk>,
> @fusenews<http://twitter.com/fusenews> *
>=20
> On 3 April 2012 16:34, Omar Atia <omar.atia@its.ws> wrote:
> > Sorry I will deploy CXF WS on ServiceMix using Apache camel :
> >=20
> > Like this route :
> >=20
> > <route>
> >=20
> >                <from uri=3D"cxf:bean:JBossCBSWS"/>
> >                <to uri=3D"log:testingJboss"/>
> >               =20
> >                <transform>
> >                <method bean=3D"WSresp"/>
> >                </transform>
> >               =20
> >               =20
> >                </route>
> >=20
> > Bean has to JDBC connect to DB and execute a DB package .
> >=20
> > Thanks,
> > Omar Atia
> >=20
> >=20
> >=20
> > From: Omar Atia
> > Sent: Tuesday, April 03, 2012 6:20 PM
> > To: 'users@camel.apache.org'
> > Subject: Jetty server...Performance testing ...
> >=20
> > Dears,
> >=20
> > I have Jetty server with WS deployed on ServiceMix , that WS connec=
t
> > using JDBC to DB and call DB package , well Can we have performance=

> > for 15 request to be processed per second I know it depends on DB
> > response .
> >=20
> > How we can increase no of threads for Jetty server? Can we have suc=
h
> > number of request per second? I believe performance testing should
> > Judge.
> >=20
> > Well appreciate your feedback,
> >=20
> > Thanks,
> > Omar Atia
--=20
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com