Please Wait (has no any Error message)
Tue, 03/10/2009 - 19:39 — tiger
Tomcat 5.5
JDK 1.5.0-11
NextApp Echo v2.1.0.beta3
The company I work at uses Echo2 to build a large ERP system.
We wrote thousands of programs.
Now, we encounter a problem:
The fireFox browser appears "PLEASE WAIT" message sometimes, but logs has no error message. The Tomcat did not crash, but we have to wait 1 to several minutes. The frequence of "PLEASE WAIT" did make us annoy.
Because there is no error message, so it is difficult to debug.
I want to know what directions should I consider to solve the question..
THANKS in advance...
TIGER
Are you saying it recovers
Are you saying it recovers after some time, or do you have to hit reload (or restart the browser) for things to begin working again?
If it does NOT recover, check the Firefox error log. (Tools menu, Error Console).
It's best to clear the error console and close out all other browser windows, and THEN attempt to replicate the problem in your Echo application. (Clearing it first is necessary because most *other* web sites/applications will have tons of error messages being sent to the console, but Echo will only show error messages in that console if something has actually gone wrong).
If you can see the Echo app printing an error to that console when it fails, please post that message (or a screenshot of the console)
Additionally would suggest upgrading to 2.1.1. The problem is likely in 2.1.0.beta3, that release is nearly three years old.
Best
--Tod
It recover after some time.
Yes, it recover after some time.
What should I do???
THANKS!!
Definitely would suggest
Definitely would suggest updating to the latest version (2.1.1) first.
Thread Dump
If there is no error, it is most likely that the server is still processing the request. Create a few thread dumps of the server, shouldn't be that hard to debug.
Niels
If it recovers, then
If it recovers, then everything is just ok in terms of "functionality".
This can be caused by one of the following:
- Some packets lost on the TCP layer in communication, the client/server just retries (But usually faster than 1-2 minutes)
- On the server side your app is taking longer than expected
- Some sort of (perhaps DB, critical sections etc.) locking preventing progress of the thread.
Things to look at:
- Has you app server JVM enough memory, or is it just busy with garbage collection
- Does the app always "hang" at the same place ?
- Is the app server running out of some resources (for example number of concurrent requests, or waiting for a pooled DB connection etc.)
- Do other users of the same app continue to work, or do they also hang ?
André