Re: Multiple users accessing a servlet

[Srinivasan S (Systems Engineering Group)]

It is possible to make a database pooling with the MS-SQL server 6.5

        ********

On Sat, 31 Jul 1999, K. Venkata ramana wrote:

> >
>
> Hi Nitin,
>
> Connection pooling (using connections from a pool) is not supported by MS-Access.
> Please browse the following sites :
> http://support.microsoft.com/support/kb/articles/q169/4/70.asp
> http://support.microsoft.com/support/kb/articles/q166/0/83.asp
> This is what Microsoft says on connection pooling with regard to MS-Access :
> You cannot enable connection pooling with the Microsoft Access driver. The Microsoft
> Access driver internally uses Jet, which supports the apartment threaded model. In
> other words, Jet requires the connect/disconnect procedure to be handled by the same
> thread. For connection pooling to work, the connect/disconnect procedure needs to be
> handled by different threads. This applies to all the Microsoft Desktop drivers that
> use Jet.
> This is the story for ODBC driver manager ver3.0 or later.
> I do not know the details for JDBC and as such since it seems to depend on the
> database engine rather than the connection methodology i really doubt if we can use
> connection pooling to connect to MS-Access even with JDBC.
>
> Let me know the sites or links to any articles that have used connnection pooling
> with MS-Access and JDBC.
>
> Thanks,
>
> ramana
>
>
>
> > Nitin Kulkarni wrote:
> >
> > > Hello All,
> > >
> > > I need some help regarding multiuser programming using Servlet. We have
> > > developed an application which runs as follows
> > >
> > > HTML ----> Servlet----->
> > >                                       Database(MS Access)
> > > HTML  <---Servlet<-----
> > >
> > > The problem here is that we are opening just one connection to the database in
> > > the init() of the servlet and using the same connection for any request coming
> > > from any user.
> > >
> > > This could led to problems of data corruption such as variable getting changed
> > > before the query which uses it gets executed (This would happen if two users
> > > access the servlet at the same time).
> > >
> > > The two solutions known to handle this problem are syncronising or using
> > > SingleThreadModel.  But both these methods have their drawbacks. Also these
> > > handle multithreading aspect rather than multiuser. Is there any third way to
> > > handle this kind of a multiuser aspect.
> > >
> > > Quick help will be appreciated.
> > >
> > > Thanks
> > >
> > > Nitin
> > >
> > > ___________________________________________________________________________
> > > 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
>

___________________________________________________________________________
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