This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes Web Services and the fly likes soap-connection pooling Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "soap-connection pooling" Watch "soap-connection pooling" New topic

soap-connection pooling

b jr

Joined: Apr 03, 2006
Posts: 1
I m new to webservices. I m accesing a webservice by manually coding the client (soap connections). How do I make sure that the connections are not created for each transaction? Is there a client side setup to make sure that the soap connections are pooled or reused?

// Create the connection

SOAPConnectionFactory scf = SOAPConnectionFactory.newInstance();

SOAPConnection conn = scf.createConnection();

Peer Reynders

Joined: Aug 19, 2005
Posts: 2932
Hi "b jr",

Welcome to the JavaRanch. There aren't many rules around here, however adherence to the JavaRanch Naming Policy is one of them. The display name b jr does not comply with that policy. Please adjust your display name. Your cooperation is appreciated.
Peer Reynders

Joined: Aug 19, 2005
Posts: 2932
Web services use HTTP as their transport. HTTP is a connectionless protocol. The web service client sends a SOAP request inside of an HTTP request and gets its SOAP response within the HTTP response. So there are no connections to pool.
Transactions between the web service client and web service can only be coordinated through additional protocols like WS-Transaction, support of which is likely limited to the commercial super-platforms (IBM Websphere, BEA Weblogic, Oracle Application Server, etc.).
I agree. Here's the link:
subject: soap-connection pooling
It's not a secret anymore!