Re: Object pooling

I have some heavyweight objects that i would like to try pooling.

To be specific, they're JAX-WS (actually JBossWS) Service (and/or port)
objects. My observations so far are that they take hundreds of
milliseconds to make (if you count instantiation of the service,
instantiation of the port, and extra time taken the first time a method
on the port is called, it seems to be 200-800 ms, depending), and that
the spec doesn't guarantee that they're threadsafe (and as it happens, i
believe that in the JBossWS implementation, neither the service nor the
port is threadsafe).

That may not be that much time in the grand scheme of things, but some
guys in the sort of ops-infrastructure-architecture part of the project
are making worried noises about performance of the web service
interfaces, and i'd like to be able to reassure them.

I know the modern warnings about pooling, but this seems like a case
where it could be justified. Does that sound right?

So, what's the state of the art in object pooling? My default starting
point is Commons pooling:

http://commons.apache.org/pool/

But i note that it doesn't do generics. I would really like something
that does generics. I could wrap a generic wrapper round it fairly
easily, but i'd rather not have to. So, are there any other pooling
implementations around which use generics, or are otherwise preferable?