tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr." <>
Subject Re: Help in diagnosing server unresponsiveness
Date Fri, 01 Feb 2013 17:41:22 GMT
On Fri, Feb 1, 2013 at 12:09 PM, Edson Richter <> wrote:
> Em 01/02/2013 15:03, Edson Richter escreveu:
> When I say (we see..) I want to mean: I see lots of junior programmers doing
> the same mistake over and over... I don't know if this is your case, but I
> feel that worth to mention here.

wow, this is all good to know! Thanks! I definitely consider myself
junior 'java' developer even though i've been developing software
since 1995. I'm loving java/jsf and tomee/tomcat right now.

my app is running fine, but i'm always striving for perfection and
performance, and that is why I made my way from mojarra to myfaces,
glassfish to tomee/tomcat, and jsf-managed-beans to cdi-managed-beans,
and just early this morning from APR to NIO connector.

>> b) Lots of people forget to correctly close external resources (files, tcp
>> connections, jdbc resources). Check your source code using FindBugs. It is
>> not perfect, but will give you lots of warnings if you run on risk of not
>> correctly closing resources. Remember, for jdbc resources, you should close
>> all result sets first, then all statements, then all connections (not all
>> database drivers will release resultset resources on statement close!).

backtracking... is this a chance/time to use jdbc interceptors? i've
seen some chatter about jdbc interceptors, but have not really dug
into it quite yet.

>> c) Also, we see incorrect thread programming...

this sounds good for clusters, right? i'm hoping to use clustering for
the app that i've developed.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message