Slow performance of OC4J application.

We have an application where the server runs on a system with the following configuration:

SunOS redwood 5.8 Generic_108528-14 sun4u sparc SUNW,Ultra-EnterpriseSystem = SunOS
Node = redwood
Release = 5.8
KernelID = Generic_108528-14
Machine = sun4u
OEM# = 0
Origin# = 1
NumCPU = 12

The version of Java on that system is:
java version "1.3.1_03"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03)
Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode)

We have the OC4J (version 9.0.2.0.0) and Oracle database installed on this system.

The Java client application runs on Windows 2000.

We are facing the problem that the application runs very slowly. There are instances when the UI greys out for sometime and after a few minutes comes out with the result. Our application runs several queries to the database and this is usually done by calling appropriate interfaces in EJB components (Stateless Session beans) deployed on the server.
Any idea why the performance is very slow and how this can be improved?

Thanks.
chowdryAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

vzilkaCommented:
Can you pin point the performance problem location?
Try the following - if you have a profiling tool (style JProbe) then use it on the server.
Otherwise - try using DMS - http://machine_name:8888/dmsoc4j/Spy
It will give you the time it takes for each EJB to run.
If the problem is on the server, then try to see if it is a database related issue (and then you can tune the database) or an OC4J issue. Try putting debug statements before your DB calls, and see how long they take. DMS in OC4J 9.0.2 was not powerful enough to monitor DB operations.

Once you pin point the problem location, we can see what has to be done.
Usually tuning the app server gives only about 5-15% performance boost. The problem might be in the application code, or the database configuration, or the client code. These are the most likely candidates.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vzilkaCommented:
chowdry, was the issue solved?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java App Servers

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.