a way to limit the max number of EIS connections

[101]

i've set up my ra with the help i got from this forum, thanks!

works fine, but i don't know how to handle this scenario:

i have an EIS where the number of connections is limited by licences. so i created my ra to pool connections and my clients are connecting/disconnectiong like crazy... :)

but what happens if jboss asks my ra to create more EIS connections then what is possible? should i throw an exception?

also i can't produce the situation because jboss 3.2.1 does not create more then 4 EIS connections, even if i start 8 clients calling getconnection. after starting more then 3 clients, the number of EIS connections stops at 4 (i use two different credentials, that's why 3 client already create 4 EIS connections).

i have seen a AvailableConnectionCount attribute with value 4 on my name=netvisor/BDL-SessionFactory,service=ManagedConnectionPool on my jmx console. what is this? how can i change it?

is there a way at all to give a max number of EIS connections to jboss, and to tell it to block connection requests until there's a free connection? (in case the max EIS connections are exceeded...)

thanks in advance,

- 101

[101]

oops, i guess it's getMaxConnections() in connection metadata interface...

[101]

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?

[adrian.brock]

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
the classloading.

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

Regards,
Adrian