On Tue, 19 Oct 1999, Peter Delahunty wrote:
> I'm not 100% sure but wouldn't you be better off using multiple
> threads and just syncronising the methods that access the DB.
>
> Using the syncronized key word.
But spell it "synchronized" :-).
Better yet, try to isolate the critical code even further down than
the method level, down to as small a block as possible, and then
synchronize that. There's been a lot of discussion of
SingleThreadModel on this list, and the consensus is that it's better
to avoid it. You can check the archives for details.
> -----Original Message-----
> From: niraj l [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 19, 1999 2:14 PM
> To: [EMAIL PROTECTED]
> Subject: Ideal value for single threadmodel pool size
>
>
> Hello ,
> I have a servlet application with heavy database transaction. My classes
> implement SingleThread Model.
> With 100 people accesssing the application simultaneously( we use a tool
> SQA Roboot to simulate it) what should be ideal value for "Single
> ThreadModel Pool Size" in Jrun (jse settings).
> Any quick help will really help me coz I am facing a production problem.
> Thanks,
> Niraj.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
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
