web services - JAX-WS Client Pool in a Java EE App Server -


I have an application running in a Java EE app server and it must call the web service of a partner company.

Using wsimport.exe from my JDK (1.6) I have generated client clients. I instruct the service to call the web service and receive the port.

I saw that the first call of the web service is slow and I believe it is because it is WSDL. The subsequent calls are fast.

I can keep WSDL locally, and apparently will accelerate the first call.

To customize my app, I was thinking that I pooled customers in this app, I have some throttling in the app - I think I have a pool of 5 clients, so I I'm using memory for up to 5 customers. If a sudden increase in my server increased, I do not have to worry that unlimited number of customers will be out of memory error. I believe, based on past experience, web service customers have used too much memory ...

  • Will you bother with the pool?
  • How will you get the web service slow on the first call?
  • What is the best way to create that pool, so that I have to do minimal programming (i mean a library / API / whatever, so that I can change the wheel again and some hairy bugs Do not have to code).

    Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -