Re: [Axis2] NIO impl in Axis2 (Re: Axis2/Java: Share HTTP connection between multiple client stubs ?)

[Deepal Jayasinghe]

+1 for moving NIO code to Axis2.

Btw at the moment we have a number of transports and all of them are in
the core. And we know that Axis2 is totally independent of the
transports so what if we move all the transports into a new module ?

Thanks
Deepal


> Asankha,
>
> Can we please move this transport to Axis2 in time for 1.3?
>
> thanks,
> dims
>
> On 6/2/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
>>
>>  Hi Raimund
>>
>>  The default http/s client transport of Axis2 is based on the commons
>> HttpClient. Please see the following links for some direct solutions for
>> your issue.
>>  http://wso2.org/library/87
>>  http://wso2.org/library/230
>>
>>  You may also find more articles through a search on the OxygenTank
>> library.
>>
>>
>> I know that Asankha has been working on a non-blocking HTTP client
>> for Axis2
>> that re-uses connections. As I understand it this code is only in the
>> Synapse release so far ( http://ws.apache.org/synapse). But I know
>> there is
>> a plan to get it into the core of Axis2. It is just an Axis2
>> transport so
>> the code will work under Axis2.
>>
>>  Asankha - am I right?
>>
>>  Yes, the transport we developed for Synapse is tuned for a high
>> throughput
>> environment where you would actually gain from a non-blocking client
>> implementation. Thus, if you just want to send a message and read its
>> response, this transport is not right for you; as it will create an IO
>> Reactor, a thread pool to handle the requests, and prepare to send
>> multiple
>> messages out reusing connections where applicable. We have plans to move
>> this transport into Axis2, but the client side should be used with
>> care for
>> the above reasons.
>>
>>  asankha
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-- 
Thanks,
Deepal

"The highest tower is built one brick at a time"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] NIO impl in Axis2 (Re: Axis2/Java: Share HTTP connection between multiple client stubs ?)

[Davanum Srinivas]

Asankha,

Can we please move this transport to Axis2 in time for 1.3?

thanks,
dims

On 6/2/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote:


 Hi Raimund

 The default http/s client transport of Axis2 is based on the commons
HttpClient. Please see the following links for some direct solutions for
your issue.
 http://wso2.org/library/87
 http://wso2.org/library/230

 You may also find more articles through a search on the OxygenTank library.


I know that Asankha has been working on a non-blocking HTTP client for Axis2
that re-uses connections. As I understand it this code is only in the
Synapse release so far ( http://ws.apache.org/synapse). But I know there is
a plan to get it into the core of Axis2. It is just an Axis2 transport so
the code will work under Axis2.

 Asankha - am I right?

 Yes, the transport we developed for Synapse is tuned for a high throughput
environment where you would actually gain from a non-blocking client
implementation. Thus, if you just want to send a message and read its
response, this transport is not right for you; as it will create an IO
Reactor, a thread pool to handle the requests, and prepare to send multiple
messages out reusing connections where applicable. We have plans to move
this transport into Axis2, but the client side should be used with care for
the above reasons.

 asankha
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2/Java: Share HTTP connection between multiple client stubs ?

[Asankha C. Perera]

Hi Raimund

The default http/s client transport of Axis2 is based on the commons HttpClient.
Please see the following links for some direct solutions for your issue.
http://wso2.org/library/87
http://wso2.org/library/230

You may also find more articles through a search on the OxygenTank
library.

I know that Asankha has been working on a non-blocking
HTTP client for Axis2 that re-uses connections. As I understand it this
code is only in the Synapse release so far (
http://ws.apache.org/synapse). But I know there is a plan to get it
into the core of Axis2. It is just an Axis2 transport so the code will
work under Axis2.
  
Asankha - am I right?
  

Yes, the transport we developed for Synapse is tuned for a high
throughput environment where you would actually gain from a
non-blocking client implementation. Thus, if you just want to send a
message and read its response, this transport is not right for you; as
it will create an IO Reactor, a thread pool to handle the requests, and
prepare to send multiple messages out reusing connections where
applicable. We have plans to move this transport into Axis2, but the
client side should be used with care for the above reasons.

asankha



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2/Java: Share HTTP connection between multiple client stubs ?

[Davanum Srinivas]

Raimund,

Please see this:
http://wso2.org/library/87

thx,
dims

On 6/1/07, Traichel, Raimund <[EMAIL PROTECTED]> wrote:



Hello,

I have a question regarding the connection handing using a Axis2 / Java
Client.

Is it possible to share one HTTP connection between
multiple client stubs using Axis2 / Java Client ?

Example:
I have two services deployed (HelloWorld and HelloMoon) on my server.
From the WSDL
files "HelloWorld.wsdl" and "HelloMoon.wsdl" I have generated 2 Java
client stubs (HelloWorld_ServiceStub
and HelloMoon_ServicStub). Currently each client stub creates it's own
HTTP connection to the server.
Is it possible to establish only one connection to the server, which can
be used to send requests to
the HelloWorld AND the HelloMoon service ?
This means the two different client stubs should share the same HTTP
connection / HTTP client.
I am already using the parameter "REUSE_HTTP_CLIENT", but this has only
the effect, that the same
connection (HTTP client) is used for all requests within the same client
stub.

I am currently using Axis 2 V1.2 and Java 1.5.0_11.

Thanks,
Raimund


Raimund Traichel
Siemens Enterprise Communications GmbH & Co. KG

SEN ESY HA D QA 3
Hofmannstr. 51
81379 Munich, Germany

phone: +49 (0)89 722 31686
email : mailto:[EMAIL PROTECTED]

Communication for the open minded
www.siemens.de/open
www.siemens.com/open


Siemens Enterprise Communications GmbH & Co. KG

Managing Directors: Reinhard Benditte, Gerhard Otterbach,
Thomas Zimmermann



Registered offices: Munich

Commercial registry: Munich, HRA 88546
WEEE-Reg.-No. DE 27980375

General Partner:

Siemens Enterprise Communications Management GmbH

Registered offices: Munich

Commercial registry: Munich, HRB 163415




--
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Axis2/Java: Share HTTP connection between multiple client stubs ?

[Paul Fremantle]

Raimund

I know that Asankha has been working on a non-blocking HTTP client for Axis2
that re-uses connections. As I understand it this code is only in the
Synapse release so far (http://ws.apache.org/synapse). But I know there is a
plan to get it into the core of Axis2. It is just an Axis2 transport so the
code will work under Axis2.

Asankha - am I right?

Paul

On 6/1/07, Traichel, Raimund <[EMAIL PROTECTED]> wrote:


 Hello,

I have a question regarding the connection handing using a Axis2 / Java
Client.

Is it possible to share one HTTP connection between
multiple client stubs using Axis2 / Java Client ?

Example:
I have two services deployed (HelloWorld and HelloMoon) on my server.
From the WSDL
files "HelloWorld.wsdl" and "HelloMoon.wsdl" I have generated 2 Java
client stubs (HelloWorld_ServiceStub
and HelloMoon_ServicStub). Currently each client stub creates it's own
HTTP connection to the server.
Is it possible to establish only one connection to the server, which can
be used to send requests to
the HelloWorld AND the HelloMoon service ?
This means the two different client stubs should share the same HTTP
connection / HTTP client.
I am already using the parameter "REUSE_HTTP_CLIENT", but this has only
the effect, that the same
connection (HTTP client) is used for all requests within the same client
stub.

I am currently using Axis 2 V1.2 and Java 1.5.0_11.

Thanks,
Raimund


*Raimund Traichel*
*Siemens Enterprise Communications GmbH & Co. KG*

SEN ESY HA D QA 3
Hofmannstr. 51
81379 Munich, Germany

phone: +49 (0)89 722 31686
email : mailto:[EMAIL PROTECTED] <[EMAIL PROTECTED]>

*Communication for the open minded*
www.siemens.de/open
www.siemens.com/open

Siemens Enterprise Communications GmbH & Co. KG

Managing Directors: Reinhard Benditte, Gerhard Otterbach,
Thomas Zimmermann



Registered offices: Munich

Commercial registry: Munich, HRA 88546
WEEE-Reg.-No. DE 27980375

General Partner:

Siemens Enterprise Communications Management GmbH

Registered offices: Munich

Commercial registry: Munich, HRB 163415






--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

"Oxygenating the Web Service Platform", www.wso2.com

Axis2/Java: Share HTTP connection between multiple client stubs ?

[Traichel, Raimund]

Hello, 

I have a question regarding the connection handing using a Axis2 / Java
Client.

Is it possible to share one HTTP connection between
multiple client stubs using Axis2 / Java Client ?

Example:
I have two services deployed (HelloWorld and HelloMoon) on my server.
>From the WSDL
files "HelloWorld.wsdl" and "HelloMoon.wsdl" I have generated 2 Java
client stubs (HelloWorld_ServiceStub
and HelloMoon_ServicStub). Currently each client stub creates it's own
HTTP connection to the server.
Is it possible to establish only one connection to the server, which can
be used to send requests to
the HelloWorld AND the HelloMoon service ?
This means the two different client stubs should share the same HTTP
connection / HTTP client.
I am already using the parameter "REUSE_HTTP_CLIENT", but this has only
the effect, that the same
connection (HTTP client) is used for all requests within the same client
stub.

I am currently using Axis 2 V1.2 and Java 1.5.0_11.

Thanks,
Raimund

 

Raimund Traichel 
Siemens Enterprise Communications GmbH & Co. KG 

SEN ESY HA D QA 3 
Hofmannstr. 51
81379 Munich, Germany

phone: +49 (0)89 722 31686 
email : mailto:[EMAIL PROTECTED]
 

Communication for the open minded 
www.siemens.de/open   
www.siemens.com/open   

Siemens Enterprise Communications GmbH & Co. KG

Managing Directors: Reinhard Benditte, Gerhard Otterbach,
Thomas Zimmermann



Registered offices: Munich

Commercial registry: Munich, HRA 88546
WEEE-Reg.-No. DE 27980375 

General Partner: 

Siemens Enterprise Communications Management GmbH

Registered offices: Munich

Commercial registry: Munich, HRB 163415