The bast way is to use stacks for connection pooling. popping out
connections. you can then user empty() method of stack to check for any
ideal connections in the stack pool. The waiting clients should be
maintained in a vector and should be passed a connection upon availibility.
you have to implement a connection listener interface in each servlet which
listens for availibility of connection. maybe you can show a custom page
till the connection is available

It works fine

Purav

-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of
Ramesh, Kesav
Sent: Monday, April 23, 2001 10:50 AM
To: [EMAIL PROTECTED]
Subject: Re: Help pleaseeeeeeeeee


may be you should check the max number of connections and increment size

Regards

Ramesh Kesavanarayanan

Electronic Data Systems
Steeple Reach,
25, Cathedral Road,
A SEI-CMM�  Level-3 Organization
  91-44-811 3801 to 15 ext :2186
  91-44-233 0380 (res)
 [EMAIL PROTECTED]
 [EMAIL PROTECTED]


> -----Original Message-----
> From: Jayakumar Mani [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, April 21, 2001 3:26 PM
> To:   [EMAIL PROTECTED]
> Subject:      Help pleaseeeeeeeeee
>
> Hi guys/gals,
>   I have done one ConnectionPooling class by Wrox
> publications. The problem is they are creating the
> connection objects & storing in vector...
> suppose i have two connections & stored it in one
> vector
> it is giving no problem when i access two connections.
> but after that...it is saying
>
> java.sql.SQLException: [Microsoft][ODBC SQL Server
> Driver]Connection is busy with results for another
> hstmt
>
> this is the error
> how can i solve this
> Thanks in advance
> Jayakumar
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Auctions - buy the things you want at great prices
> http://auctions.yahoo.com/
>
> __________________________________________________________________________
> _
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
> body
> of the message "signoff SERVLET-INTEREST".
>
> Archives: http://archives.java.sun.com/archives/servlet-interest.html
> Resources: http://java.sun.com/products/servlet/external-resources.html
> LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.250 / Virus Database: 123 - Release Date: 4/18/01

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.250 / Virus Database: 123 - Release Date: 4/18/01

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to