Mitch
Member
I wonder if other E1 8.10 shops with similar configs are having performance, and stability issues specifically in Websphere 5.0.2.3.
By mid-week, JAS server becomes unstable - you know this just by looking at the Summary info and numbers under SAW. This is happening even after extensive performance adjustments, and on top of the known unicode conversion overhead.
Something is strange about memory and cache mgt in JAS server. ie. When no users logged on in weekends, the JAS server could take up 750MB out of 786 MB heap size, and it may or may not recover after refresh.
For instance, while the Fat client runs an app in seconds, the same application may take 10 to 15 min to run on the web, and other times the web is as fast as the FAT client. It's also intermitten. The same business views are called by both clients.
App side: Applied related SARs, reindexed tables.
System side: E1 8.93 R1, all w2k3 servers, JDBC V2.2 of MS. Serialize Web objects using IBM JDK 1.3.1 w patch.
We're down to JDBC interface right now based-on some lines in jas, and rt debug, ie. "removing old transactions" lines in jasdebug match with timing on the select statement in RTdebug. It's hard to understand this. Eventhough it's generally slow in web, if it were just a JDBC driver issue, shouldn't be happening to other apps as well - since we're having this performance issue in the worst form in just one application: the voucher receipt match.
Regards,
Mitch.
By mid-week, JAS server becomes unstable - you know this just by looking at the Summary info and numbers under SAW. This is happening even after extensive performance adjustments, and on top of the known unicode conversion overhead.
Something is strange about memory and cache mgt in JAS server. ie. When no users logged on in weekends, the JAS server could take up 750MB out of 786 MB heap size, and it may or may not recover after refresh.
For instance, while the Fat client runs an app in seconds, the same application may take 10 to 15 min to run on the web, and other times the web is as fast as the FAT client. It's also intermitten. The same business views are called by both clients.
App side: Applied related SARs, reindexed tables.
System side: E1 8.93 R1, all w2k3 servers, JDBC V2.2 of MS. Serialize Web objects using IBM JDK 1.3.1 w patch.
We're down to JDBC interface right now based-on some lines in jas, and rt debug, ie. "removing old transactions" lines in jasdebug match with timing on the select statement in RTdebug. It's hard to understand this. Eventhough it's generally slow in web, if it were just a JDBC driver issue, shouldn't be happening to other apps as well - since we're having this performance issue in the worst form in just one application: the voucher receipt match.
Regards,
Mitch.