- This topic has 28 replies, 7 voices, and was last updated 20 years, 5 months ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version: Windows 2000 SP4
Eclipse version: 3.0.0
Eclipse build id: 200406251208
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins: Rational ClearCase
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7.200
Eclipse JDK version: j2sdk1.4.2_03
Application Server JDK version: j2sdk1.4.2_03
Are there any exceptions in the Eclipse log file? no– Message Body ——————————-
After deploying my web project using “MyEclipse -> Add and Remove Project Deployments…”, it becomes very slow to start WebLogic using MyEclipse. My system basically hangs for about 5-10 minutes with 100% CPU usage after displaying the following Console message:
<Jul 29, 2004 4:45:30 PM PDT> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server “myserver” for domain “mydomain”>
Alternatively, if I launch WebLogic outside of Eclipse the entire startup process takes less than 30 seconds.
This same behavior has been observed on all of our developers’ machines, which generally have 2.4 GHz P4 CPUs with 1GB RAM.
We have tried modifying the WebLogic JVM memory args (e.g. “-Xms512m -Xmx512m”) with no noticable performance change.It might be worth noting that the project we are deploying has two Eclipse project build path dependencies and about 27 .jar dependencies, all of which we are deploying using the “Smart deployment” option in the MyEclipse preferences. Also, these project and .jar dependencies are actually referenced from a ClearCase repository before being deployed to our local machine by MyEclipse. The project itself is on the order of several hundred .jsp files, several hundred .java files, and a couple hundred config files (.properties, .xml, etc.).
Any tips or suggestions for improving the performance would be greatly appreciated.
Are any of the resources getting deployed comming off of remote machines or is everything copied locally first then the deployer copies it from the local machine/repo into the deployment location?
All resources are being deployed directly from a remote Machine (actually a ClearCase view) into to the deployment location, with no intermediate local copy being made. The idea was to avoid the need for developers to create their own projects locally with all the proper classpath and project references. Also, working out of the same source location helps promote reserved checkouts during resource modification.
Can you open up your network properties while starting the app server and see if there is any network traffic while the app server is starting… if its not and the system is literally just sitting there for ages, then we can atleast rule out remote resource access as the problem… (I want to make sure our connector isn’ try to do something we aren’t aware of).
Hi Riyad,
I’ve tried starting the web server while watching both the task manager and network properties. In the task manager, the CPU usage spikes at or near 100% much of the time and the memory usage never reaches full capacity. In the network properties there is definitely some network traffic. However, it seems to occur much less frequently and there are long spans of time (multiple minutes) where the CPU usage is maxed out with absolutely zero network activity.
This is very strange, can you check your log file for any timeout errors or something equally as silly (located at <workspace dir>\.metadata\.log)
Also you might try disabling your network interface or otherwise shutting down your nic, so if it IS a timeout issue of sorts, then it seems that it should startup much faster since all network attempts fill fail immediately.
However the 100% CPU thing is a bit strange. Once we have this info, I can ask the devs to take a look.
Thank you for your patience in this matter, it does take some investigation work to figure it all out.
Ok, after deploying the site I tried disabling the network connection before starting up WebLogic. There must be some network dependency because immediately upon starting WebLogic, the javaw.exe task grabbed 100% of the CPU usage and basically ground my machine to a standstill. I let it go for over 20 minutes with no change.
At this point I re-enabled the network connection and the startup continued (messages began to appear in the console) and I got control of my machine back. After the following console message…
<WebLogicServer> <BEA-000327> <Starting WebLogic…
…I disabled the network connection once again. The CPU usage hovered around 100%, but did not freeze up my machine as before. A few more console messages displayed (basically DTD validation errors for one of the TLD files in my web project), then the startup seemed to stop again. My machine was not frozen, but the javaw.exe process stayed pretty constant at 100% CPU.
After about 15 minutes with no change, I re-enabled the network connection one last time and the WebLogic startup continued and finally finished within just a few seconds.
The only messages I found in the .log file were the following, written at the very beginning of the startup process:
!SESSION Aug 03, 2004 14:51:22.889 ———————————————
eclipse.buildId=I200406251208
java.version=1.4.2_03
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: –vmargs -Xms256M -Xmx256M!ENTRY org.eclipse.ui 4 4 Aug 03, 2004 14:51:22.889
!MESSAGE Unable to find Action Set: net.sourceforge.eclipseccase.ui.actionsetThis is officially weird… before we can start blaming MyEclipse I would very much appreciate it if you could:
1) Download Eclipse 3.0 SDK final
2) Download MyEclipse 3.8 Beta 2
3) Install them into some temp location like C:\Temp\Eclipse3 and C:\Temp\MyEclipse3.8
4) Load up that Eclipse that you just installed, create a new workspace.
5) navigate to your WebLogic connector settings and duplicate those settings from your other Eclipse install
6) Run WebLogic… did it work?
7) Now try and import your project, deploy it, try and rerun weblogic, did it work?Ok, I went to a fresh machine with roughly the same configuration as mine (a little less RAM) and installed the following from scratch:
– Eclipse 3.0
– MyEclipse 3.8 Beta2
– WebLogic 8.1 SP2Then I experimented with a few different ways of deploying projects and observed the WebLogic startup times listed below:
– Start WebLogic in MyEcilpse with no projects deployed:
< 1 min.– Start in MyEclipse with a simple, local web project deployed (couple of classes and JPSs):
~ 1 min.– Start in MyEclipse with a simple ClearCased web project deployed:
~ 1 min.– Start in MyEclipse with our large, imported, ClearCased web project deployed:
~ 13 min.– Start outside of MyEclipse with above project deployed:
< 2 min.– Start in MyEclipse w/ McCafee virus scanning turned off:
~ 4 min.– (Retry) Start in MyEclipse w/ virus scan back on:
~ 11 min.So, it seems that the virus scan program had some effect – I’m guessing because it is scanning any remote files being accessed by or copied to the local machine. But, I still question why there is a need for much network activity at all, since most of the files should have already been copied to the local WebLogic deployment area.
Anyway, I went back to my original machine and tried starting WebLogic with and without virus scanning turned on and got the following startup times:
– Start in MyEclipse w/ McCafee virus scanning turned off:
~ 4 min.– Start in MyEclipse w/ McCafee virus scanning turned on:
~ 7 min.– Start outside of MyEclipse w/ McCafee virus scanning turned on or off:
~ 1 min.So, this seems to confirm that turning off our virus scanning does help somewhat. However, we really can’t get away with doing that on a regular basis. Anyway, even with the virus scanning turned off, the performance is still too slow, I think.
Your details to testing and are *much* appreciated. With a situation like this its very tedious finding the culprit and quite hard with the team being remote, we appreicate all the extra time you are taking to help run this down.
As a last ditch effort, I want to figure out if the ClearCase plugin is to blame or if MyEclipse is to blame… is there a way to checkout a project locally and then disable the clearcase plugin and then try and start WebLogic? I wonder if the WebLogic connector is doing something, when combined with the CC plugin, that is causing an insessent amount of network activity that wouldn’t otherwise happen.
No problem. Thank you for your suggestions in troubleshooting this.
Sorry, but I forgot to mention that when I installed everything onto the fresh machine, I did not even install the ClearCase plug-in. I simply pointed Eclipse to the project through a local drive (e.g. J:) that had been mapped to my ClearCase view. This is exactly what I did on my other machine. The only difference is the CC plug-in, which simply allows us to check-in and check-out files from with Eclipse. Anyway, the slow behavior seems to be the same whether or not the plug-in is present.
Ok thank you for the update, I’ll have to kick this back to the devs… I’m not too sure what this might be now.
A couple of things come to mind. First, if you’re using a remote clearcase view, rather than a local copy, it will always be slower than running locally due to the network latency.
Second, in comparing your external startup times from the command line, is Eclipse running at the same time? If not, you’ve got a couple hundred meg of extra ram that you don’t have when Eclipse is up.
Third, when starting from the commandline, you’re not starting a full debug install of WebLogic. To compare more fairly, instead of selecting a ‘Debug’ startup in Eclipse, select a ‘Run’ startup. This disables debugging and will yield a fairer comparison. It might be that WebLogic is recompiling all your JSP’s when started through Eclipse, but not from the commandline, for example. Check the temporary compilation directory to see for sure.
Thanks for the good information. Please see my comments below…
First, if you’re using a remote clearcase view, rather than a local copy, it will always be slower than running locally due to the network latency.
Understood, however in the past (with Eclipse 2.x) we have used other Eclipse plug-ins (Object Edge WebLogic plug-in, for example) that allowed us to launch WebLogic in debug mode without any noticable performance impact. One difference I can think of off-hand is that none of the plug-ins we have used before offered the ability to set breakpoints in the actual JSP files themselves – only in java classes. For us that’s fine since about 99% of our code is in java classes and tags – we have very little embedded java. Is it possible that MyEclipse is doing some extra work in order to support JSP debugging? If so, can this functionality be disabled?
Second, in comparing your external startup times from the command line, is Eclipse running at the same time? If not, you’ve got a couple hundred meg of extra ram that you don’t have when Eclipse is up.
Good point. However, I experimented with this a bit and found that even when Eclipse was running, the server started up very quickly when launched from the command-line. Also, looking at the RAM usage in the Windows task manager I don’t believe I am ever running low on memory during the startup.
Third, when starting from the commandline, you’re not starting a full debug install of WebLogic. To compare more fairly, instead of selecting a ‘Debug’ startup in Eclipse, select a ‘Run’ startup. This disables debugging and will yield a fairer comparison. It might be that WebLogic is recompiling all your JSP’s when started through Eclipse, but not from the commandline, for example. Check the temporary compilation directory to see for sure.
I tried changing the MyEclipse WebLogic 8 preferences to start up in “Run mode”. I then cleaned and redeployed the project then tried starting the server multiple times. Interestingly, the performance was pretty much the same as in “Debug mode”. Also, I periodically checked the WebLogic working directory and regardless of which start mode I choose, I do not see any new “jsp complication”-related files appearing until I actually start hitting the site from a web browser.
Just as a quick update to this issue, I have downloaded the released 3.8 version of MyEclipse and the same behavior remains (slow startup of WebLogic within Eclipse environment).
I was just wondering, is anyone still actively researching this issue? We have continued to experiment here, but have not yet been able to determine the root cause of the poor performance. I’m hopeful that we can find a solution soon, as I am part of a group that is recommending development tools for our entire business unit and I am extremely pleased overall with the MyEclipse product’s features and cost. However, I know that this WebLogic performance issue will make it a much tougher sell for widespread adoption within the company.
