I've got a very strange situation in my developement weblogic environment recently. Without any wilful config change server suddenly started to hang for seven seconds on each request. This hang happens before the request is dispatched to my web application. By using a profiler and stoping the server with debuger randomly during that period I found out that absolute majority of it's time it spends at this point:
and typical data at ZipFile.getEntry(String) line: 149 suggest that it walks through all jar files at C:\develop_ib\weblogic-ib\domains\domain_cs\servers\AdminServer\tmp\_WL_user\mci\naecdr\war\WEB-INF\lib\ and tries to find every class which is loaded.
Does anyone have any clue why is this happening and how to get rid of it?
Is your Weblogic current setup in development mode? Typically in that mode resources are re-loadable which triggers Weblogic to scan your deployment folder for changes. This then lead to heavy JAR file scan and IO; ultimately degrading the overall performance since each Thread / Request are spending time performing this task.