keiwer villabona ruiz wrote:an application in Apache Web Server, The application is consuming these web services that are in glassfish.
my problem is that it runs very slow in production.
I was researching about the performance between Apache and Glassfish. And I got something like AJP / mod_jk.
but not if it is the solution.
It seems highly unlikely to me. Apache has been running perfectly happily on thousands (probably millions) of servers for many, many years; and I can't imagine that you're the first person to team it up with Glassfish. It might be worth checking with a Glassfish forum to see if there are any known performance issues, but it seems far more likely that the problem lies in your own code.
I can only offer a few general bits of advice when dealing with performance issues:
1. Look for specific bottlenecks.
2. Measure everything.
3. Don't make any assumptions about code that you have no control over (ie, in your case, Apache and Glassfish).
4. (Whatever you do) Don't change anything until you KNOW what the problem is.
If you need to make an alteration for testing purposes, back it out when the test is finished.
5. Don't use vague phrases like "runs very slow". How "slow" is it? How "fast" does it need to be?
One possible thing to think about, if you have end users, is to create Service Level Agreements that specify exactly how fast the system is expected to run.
"Leadership is nature's way of removing morons from the productive flow" - Dogbert
Articles by Winston can be found here
I meant at that Apache was installed and we do not configured for high performance (Apache Performance Tuning). addition that the library (nusoap) for consuming web services that we use lacked a cache setting.
already solved the problem. Thanks for your feedback.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop