Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 57648

Summary:	WebappManager.start(...) is taking 6 minutes to start my Web application
Product:	[Eclipse Project] Platform	Reporter:	Jeffrey Liu <jeffliu>
Component:	User Assistance	Assignee:	Konrad Kolosowski <konradk>
Status:	RESOLVED FIXED	QA Contact:
Severity:	critical
Priority:	P3	CC:	david_williams
Version:	3.0
Target Milestone:	3.0 M9
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Jeffrey Liu

2004-04-06 16:05:47 EDT

I just switched to the Eclipse M8 base and I found that my Web application (the 
Web services explorer) takes a little more than 6 minutes to startup. It used 
to take about 15 to 20 seconds back in the 20040318 build.

I haven't changed the way my Web application is added to the embedded Tomcat 
engine between the two Eclipse base. I've traced down the bottleneck, the 
entire 6 minutes is spent in the following API call:

WebappManager.start(String context, String pluginId, IPath war_Location);

Comment 1 Konrad Kolosowski

2004-04-06 16:15:09 EDT

Could you debug it further, or provide a way for us to reproduce?  I do not 
see a problem when running help webapp.

Comment 2 Jeffrey Liu

2004-04-07 01:25:15 EDT

Looks like the amount of time spent in the WebappManager.start(...) method 
depends on the number of plugins my Web app pulls in...

I've modified my Web app plugin so that it only pulls in the org.eclipse.* 
plugins. At this point of time, it only takes about 23924 ms to startup. 
However, when I started to pull in Studio plugins, that's when things started 
to slow down.

On top of the org.eclipse.* plugins, I added one Studio plugin dependency, 
immediately, the startup time increased to 47228 ms. Then, I added another one, 
the startup time increased to 80876 ms. The next one increased the startup time 
to 129769 ms...

Was there any changes in the way dependencies are loaded in M8 (the OSGI 
layer)? Is there any way to turn on tracing for the WebappManager? If you have 
a debug version of the WebappManager, you can send it to me, I'm willing to try 
it out. I don't see a way to reproduce this unless I sent you the Studio driver.

Thanks.

Comment 3 Jeffrey Liu

2004-04-07 01:43:15 EDT

I am not sure whether this will help you debug the problem or not, but I'll 
mention it anyways. I've modified my Web app plugin so that it imports every 
single Eclipse plugins there is. Immediately, the startup time went through the 
roof. It has been 10 minutes now, and the WebappManager.start(...) method is 
still running...

Thanks.

Comment 4 Konrad Kolosowski

2004-04-09 00:48:43 EDT

I can reproduce.  PluginClassLoaderWrapper has been rewritten recently to 
remove dependency on runtime.compatibility plug-in.
PluginClassLoaderWrapper.getPluginClassPath() needs to be optimized.

Comment 5 Konrad Kolosowski

2004-04-09 02:00:25 EDT

Fixed.  Please verify in builds > 20040409.