re:Exceptions while synching Oracle Lite database with multiple

When a full refresh occurs, and especially ones with that amount of records, there is alot of compression happening on the WebServer causing high weights on the CPU and your memory is probably spiking as well. Couple of things, ask a Java guy about optimal memory settings for the oc4j container. Also look at setting the following parameters in the webtogo.ora file:

MAX_CONCURRENT=CPU*2
MAX_CONNECTIONS=CPU*4 You might have to play around with those numbers too. Find out at what point your CPU's experience weights and then set that MAX_CONCURRENT to be that number. The MAX_CONNECTIONS can be used as a queue. So, if you have MAX_CONCURRENT=5 and MAX_CONNECTIONS=10, 10 people will be able to connect and only 4 will sync. The 11th person will get a Server Busy error. There is also a TIMEOUT parameter but I found it didn't work in 9i Lite.

You may have already done this, but turn logging off. That should help as well. Received on Tue Nov 15 2005 - 02:11:20 CST