Greg Parker wrote:
> Sorry, I didn't intend to sound like such a dork.
:-) Happens to us all at some point.
> Here is what I was getting at....
> In a previous note you suggested two approaches:
>
> - have a separate connection pool for each user
> Depending on the number of users you have, it might be sufficient to
> set up the pools in jboss.jcml, or you might want to do it programmatically
> using JMX at runtime.
>
> We will potentially have 150 to 200 users to start with. Would this be an
> acceptable approach? And if so, how do I configure jboss.jcml to handle this.
Probably not. You could have some way of generating your jboss.jcml from
a list of users, but that seems kind of horrible. I think you probably
want to stay away from this.
You should be able to create pools at runtime using JMX. You could write
an MBean that reads in a list of users and passwords and creates a
connection pool for each.
> - don't use connection pools, i.e. create a new JDBC connection every time
>
> Doesn't this defeat some of the purpose behind using EJB's and jboss?
Yes, you probably want to stay away from this as well.
Probably (I use that word a lot) the best solution is one of:
- fix the Minerva JDBC connection pools to take into account the
username/password when giving out connections (see the conversation
with Guy about this)
- use the JCA-based JDBC connection pools. This is inconvenient because
you need to manually deploy the resource adapter at the moment (you
could write an MBean to do this for you at startup.)
Toby.
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
