| From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
|---|---|
| To: | Vitalii Tymchyshyn <tivv00(at)gmail(dot)com> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: JDBC gripe list |
| Date: | 2011-03-29 10:11:51 |
| Message-ID: | 4D91B067.9040008@postnewspapers.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On 29/03/2011 4:36 PM, Vitalii Tymchyshyn wrote:
> Please note that you will get into problems with classloaders and
> different containers. E.g. running a thread from classloader will
> prevent this classloader to be GCd. Tomcat handles this (with a lot of
> warnings), but it is not recommended practice. See
> http://www.theserverside.com/discussions/thread.tss?thread_id=44353 or
> http://stackoverflow.com/questions/533783/why-spawning-threads-in-j2ee-container-is-discouraged
Good point. When running under a container, it'd be best to get a thread
pool from the container via JNDI or using resource injection. that
should be fairly easily handled using a connection param.
--
Craig Ringer
Tech-related writing at http://soapyfrogs.blogspot.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitalii Tymchyshyn | 2011-03-29 10:33:21 | Re: JDBC gripe list |
| Previous Message | Vitalii Tymchyshyn | 2011-03-29 08:36:18 | Re: JDBC gripe list |