We make use of a DAO layer and the MS-SQL JDBC Driver. And yes, I =
checked there are no connection leaks. We are returning everything to =
I do know that the free MS-SQL JDBC Driver isn't good enough for =
production use and there are much better drivers available, but since =
this is a Proof-Of-Concept which is towards its closing stages, none of =
the 'higher-ups' are interested in purchasing a new driver.
I am just a junior programmer. :-( The best part is we are competing =
against Microsoft! (yes, the real MS) for this POC.
I am going to start on profiling the application and seeing whether I =
can come up with anything.
From: Bill Burke [mailto:bill@...]
Sent: Sunday, August 31, 2003 10:20 AM
Subject: Re: [JBoss-user] JBoss Performance Tuning Tips - a bit of an
So the application is entirely straight JDBC?
Stephen Davidson wrote:
> Elankath, Tarun (Cognizant) wrote:
>> Hi all,
>> We have a small web + ejb application for a POC (Proof of Concept)=20
>> that is competing against a corresponding .NET application. We are=20
>> using Struts, 1 Stateful Session Bean, 1 Stateless Session Bean and=20
>> only 10 JSP pages. The application connects to a separate MS-SQL=20
>> database server.
>> This application is being deployed in WebSphere, JBoss across Windows =
>> and Linux as the target servers.
>> So far, JBoss is giving the worst results on a 1000 user stress test, =
>> which I am certain is ENTIRELY due to my inexperience with this=20
>> application server, and nothing whatsover to do with jboss.
>> All performance tips on tuning jboss config parameters will be much=20
>> appreciated. I have done the following:
>> -increased ms and mx heap size
>> -increased connection pool size
>> -increase maxProcessor,minProcessor setting (for Tomcat)
>> -decreased session timeouts.
>> -made log level to ERROR in log4.xml
>> I am still now sure on how to disable class reloading totally.
>> All tips/suggestions will be deeply appreciated. If JBoss performs=20
>> good, then our client would definitely prefer .Net to Java, just for=20
>> the cost factor.
> Hi Tarun.
> At this point, I would recommend starting a profiler (I like =
> but there are others as well, pick your favorite), and seeing where =
> hangup is. Because it sounds like you do have one.
> Some of the nastiest I ever found (was not in JBoss itself, but=20
> sometimes in code running on it) had to do with synchronized methods=20
> (especially a static synchronixed in an abstract base class). A=20
> profiler would show if a method was getting stuck somewhere.
> Just a suggestion.
> Good luck,
JBoss Group LLC.
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
JBoss-user mailing list