Jay Paff
Active Member
Hi all,
We are running WebSphere 5.0.2.3 on IntelNT going against a iSeries 550 EnterpriseOne server running Xe SP23_F1. I know that SP23 had a bug where debug was turned on by default and can't be turned off and this is fixed in a later One-off. My question; Is anyone seeing the following error message in their JAS log and what does it mean?
2005-07-22 15:22:25.466 [ Worker Thread - OWVirtual_Thread_Group7 Assigned To com.jdedwards.runtime.virtual.OWVirtual@26cecb23] JDBC : JdeJdeBLOB->StoreBLOBOverflow
java.sql.SQLException: [SQL0803] Duplicate key value specified.
Even though Oracle says we should be able to run hundreds of folks on our configuration, our Web performance is horrid and is getting worse as more people use it. Currently, we maybe peak at 30 connections total and response is in the 10s of seconds and sometimes over a minute. I have done all the standard tuning things, like moving the ODBCs to a separate share pool, implementing HTTP compression, jacking up the heap size and turning off class GC and still performance is suckie. Has anyone found any magic bullets that make a world of diffence for Web performance? To contrast this, Citrix response is great (sub-second generally) so I believe the issues lie with the Web configuration specifics like the JAS.INI file. Any thoughts or suggestions are much appreciated.
We are running WebSphere 5.0.2.3 on IntelNT going against a iSeries 550 EnterpriseOne server running Xe SP23_F1. I know that SP23 had a bug where debug was turned on by default and can't be turned off and this is fixed in a later One-off. My question; Is anyone seeing the following error message in their JAS log and what does it mean?
2005-07-22 15:22:25.466 [ Worker Thread - OWVirtual_Thread_Group7 Assigned To com.jdedwards.runtime.virtual.OWVirtual@26cecb23] JDBC : JdeJdeBLOB->StoreBLOBOverflow
java.sql.SQLException: [SQL0803] Duplicate key value specified.
Even though Oracle says we should be able to run hundreds of folks on our configuration, our Web performance is horrid and is getting worse as more people use it. Currently, we maybe peak at 30 connections total and response is in the 10s of seconds and sometimes over a minute. I have done all the standard tuning things, like moving the ODBCs to a separate share pool, implementing HTTP compression, jacking up the heap size and turning off class GC and still performance is suckie. Has anyone found any magic bullets that make a world of diffence for Web performance? To contrast this, Citrix response is great (sub-second generally) so I believe the issues lie with the Web configuration specifics like the JAS.INI file. Any thoughts or suggestions are much appreciated.