This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 24731 - Improve startup performance for Tomcat by disabling class verification
Summary: Improve startup performance for Tomcat by disabling class verification
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Tomcat (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Pavel Buzek
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2002-06-13 09:53 UTC by Petr Jiricka
Modified: 2008-10-24 08:55 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2002-06-13 09:53:15 UTC 
The startup performance for the Tomcat server could be 
somewhat improved by turning off class verification in the 
JVM, like is currently done in the IDE.

This could be optional, so the user can re-enable 
verification on the server instance node, the default 
would be no class verification.
Comment 1 Damian Frach 2002-06-13 16:11:27 UTC 
-
Comment 2 Damian Frach 2002-06-13 16:23:47 UTC 
sorry, I wanted to reassign the 24730
Comment 3 Milan Kuchtiak 2002-06-26 09:57:25 UTC 
Option "-Xverify:none" could be easily added to the Tomcat 
instance.
As there is necessary to add this option as a property to 
the server instance node - this will be done in the next 
release.
The UI for Netbeans 3.4 should be the same as for Orion.
Comment 4 Marek Grummich 2002-07-22 11:40:59 UTC 
Set target milestone to TBD
Comment 5 _ rkubacki 2004-11-22 20:47:50 UTC 
Note that this can be consider dangerous because 3rd party code is
deployed to the container. It means possibility to turn on/off
verification per classloader basis can be good solution as it can
speed up startup and keep safety when deploying new apps.
Comment 6 Jaroslav Tulach 2008-10-24 08:55:00 UTC 
I guess this is some lost performance bug that nobody really wants to fix.