I believe in oracle you can set profiles for users and
limit things like cpu time etc ... and number of
sessions per user ... a session can be considered as a
connection here.
You would get this error if you tried to long into
many sqlplus sessions at the same time as the user
uyou are using for the DB cache.
When we have a cache of connections such a profile
setting is silly (polite term). I cant recall the
commands to change if off hand (my oracle dba days are
far behind me I hope) and more than likely you will
not be able to alter your own profile ask your dba.
No pool of connections could work with such a limit,
try lowering the number of connections established I
bet the error goes away - I dont believe it ibatis
thats at fault.
Daryl
--- Clinton Begin <[EMAIL PROTECTED]> wrote:
> Too many concurrent connections open at any given
> time by one account,
> or possibly prepared statements (but that's usually
> a "too many
> cursors" error) .
>
> Cheers,
> Clinton
>
>
> On Fri, 11 Mar 2005 13:59:24 -0700, Nathan Maves
> <[EMAIL PROTECTED]> wrote:
> > I thought ibatis took care of all of this? :)
> >
> > Caused by: java.sql.SQLException: ORA-02391:
> exceeded simultaneous
> > SESSIONS_PER_USER limit
> >
> >
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
