oops, i guess it's getMaxConnections() in connection metadata interface...
could it be that getMaxConnections() is not called at all by jboss? i've searched the sources and i've not found a method call at all...
anyone with more insight?
Yes you should throw a ResourceException
if the number of connections is exceeded.
You may find this difficult to enforce though.
e.g. To avoid people deploying the twice you could
create a singleton, but this won't work if they
use different classloader repositories to isolate
There were some bugs in the pool's exception handling,
that caused leaks in the available connections.
These should all be fixed with jboss-3.2.2RC2