on 08-01-2006 4:12 PM
We have Web As 640 Java Sp09 and we are developing custom applicatons.
We noticed that as more and more users start to use the applications, more frequently the "Http 500 dispatching error" occurs.
Often after the error the application come up by itself, other times we have to restart the whole J2EE.
There is a lot of hardware resources. The CPu and the RAM are not exausted, neverthless the errors Http 500 error is always more frequent.
Any idea ?
Any experience is very appreciated.
regards
hi,
Your Web server encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
check this
http://www.checkupdown.com/status/E500.html
Regards,
Ganesh N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thankx .
Please , I'm an Abap guy.
What do you mean with MX parameters ? Are they the memory parameters?
The Settings for the GC where are in the Visual Administrator ?
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mauro,
Check the MX parameters configured on the J2EE (for Garbage collector) and also make sure you have enough threads configured on your server and dispatcher nodes
as directed : http://help.sap.com/saphelp_erp2005/helpdata/en/5a/e30aac42484b4db29685101d251add/frameset.htm)
Hope this helps,
Regards,
MIke
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.