Hello,
I have seen several topics in the JCA forum discussing different issues, which could be
solved by the re-authentication feature. I guess in our situation this is also the case.
We are using a third party JCA resource adapter providing connections to the CORBA
services. The CORBA services have different interfaces. We have to authenticate the user
requesting a connection and using then the authentication mechanism:
| <security-domain-and-application>
|
which causes that the connections are pooled by the Subject and their types. Now regarding
the connection pool size. For example:
500 application users (different identities)
70 different connection types
20 max pool size (each sub-pool)
1 min pool size (each sub-pool)
The result of this scenario is that the pool can grow up to 500*70*20=700000 connections.
Well, at the moment our pool size do not achieve this level, but the number of application
users tend to grow.
Considering this scenario the re-authentication would allow to have just one common pool
for all connections and re-use them for every identity.
I would very appreciate if the re-authentication is considered by the pooling
implementation in JBoss. Since JCA does not restrict the number of the types/interfaces of
the connections provided by a resource adapter, I can imagine that there could be many
other resource adapters and their users, which will surely benefit from this feature.
Thanks and kind regards,
Dmitri
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4229661#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...