Message-Id: <10535.110025@fatcity.com> From: Jay Weinshenker Date: Wed, 21 Jun 2000 12:00:17 -0500 Subject: Re: oem web version slow There is a bug with OAS 3.0.2 where JAR files after 2/29/2000 are downloaded each time... could that be your issue? Here's more info... Date: Thu, 25 May 2000 11:42:23 Subject: jinitiator caching problem To: "OAUGnet-DBA" From: "Whitaker, Adrian N" List-Unsubscribe: List-Subscribe: List-Owner: X-URL: Reply-To: oaugnet-dba@lists.ksinet.com Sender: bounce-oaugnet-dba-508222@lists.ksinet.com This may interest you if you have slow R11 startup times - I wasted hours trying to resolve it with the oracle response centre. We are running 11.0.3 on solaris 2.6. The web server is on the same physical box as the database. Our pc clients are running IE4 on win95 and we are using jinitiator 1.1.7.18. We noticed that the jar files were being re-downloaded from the unix server to the client every time we re-started IE4 - even if they were already in the pc cache. This led to slow R11 startup times. We were told to upgrade jinitiator from 1.1.5.21 to 1.1.7.18 to fix this. We did this a while ago and it did fix the problem. However - a couple of months ago the problem appeared to come back. The problem seemed to come back when we upgraded from D2K patchset4 to patchset9 on the unix server - but this was a red herring. As part of our D2K upgrade we were completely replacing our rdbms codeset and then we ran adadmin to re-copy the jar files from $APPL_TOP to $JAVA top (which we have under our v8.0 rdbms codeset). So - the jar files were in effect having their date/times updated. There is a bug in WAS 3.0.2 (for solaris at least) where any jar file dated after 29-FEB-2000 is re-downloaded. So any activity which leads to the jar files under $JAVA_TOP getting updated can expose the bug. A workaround is to touch the jar files with a date of 28-FEB-2000 (or before) - but there is also a WAS patch which replaces oraweb and seems to work (bug number 1265536). J At 12:54 PM 6/21/00 -0400, you wrote: >We finally got it to work. Turns out needed J-initiator 1.1.7.27, we had >1.1.7.18. > >However, it is super slow. It downloads the JAR files each time go into >the application. Anyone have a way to speed it up. > >Jeffrey Beckstrom >Database Administrator >Greater Cleveland Regional Transit Authority >1240 W. 6th Street >Cleveland, Ohio 44113 >(216) 781-4204 > > >-------- >If you're bored, then visit the list's website: http://www.lazydba.com >(updated daily) >to unsubscribe, send a blank email to oracledba-unsubscribe@quickdoc.co.uk >to subscribe send a blank email to oracledba-subscribe@quickdoc.co.uk