From: | Paul Thomas <paul(at)tmsl(dot)demon(dot)co(dot)uk> |
---|---|
To: | "pgsql-jdbc (at) postgresql (dot) org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Multi-threaded servlet environment |
Date: | 2003-12-30 10:34:04 |
Message-ID: | 20031230103404.A24288@bacon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 30/12/2003 06:59 Marcus Andree S. Magalhaes wrote:
>
> We were about to lose a support agreement with BAE/Weblogic people
> simply because we were creating threads on our own. No reasons
> were given to us, but they (BES) simply don't *recommend* the
> arbitrary creation of threads.
>
> I suspect it's this way because people can easily create lots of
> leaks, excessive CPU usage or something like that and then blame
> the application server for its ridiculous performance.
EJB containers need to have full control of object lifecycles so creating
your own threads may cause problems. OTOH, web-only containers don't have
such rigid requirements so creating your own threads is fine in Tomcat (I
do this quite a bit without a problem).
HTH
--
Paul Thomas
+------------------------------+---------------------------------------------+
| Thomas Micro Systems Limited | Software Solutions for the Smaller
Business |
| Computer Consultants |
http://www.thomas-micro-systems-ltd.co.uk |
+------------------------------+---------------------------------------------+
From | Date | Subject | |
---|---|---|---|
Next Message | Nic Ferrier | 2003-12-30 14:06:16 | Re: Multi-threaded servlet environment |
Previous Message | Kris Jurka | 2003-12-30 10:01:18 | ResultSetMetaData enhancements |