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.
Summary: | OutOfMemoryEcxeption, respond slowly | ||
---|---|---|---|
Product: | serverplugins | Reporter: | mgsimon <mgsimon> |
Component: | Tomcat | Assignee: | Sherold Dev <sherold> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P1 | ||
Version: | 4.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: |
Description
mgsimon
2005-06-21 11:43:10 UTC
the ussage of memory first java.exe 288.388 K second java.exe 326.120 K after the first respond. Do you mean that you can see the difference even when using (deploying and running) one project on the same Tomcat started from IDE and started without IDE? No, the ide starts two virtual machines. One for the ide, the other for tomcat. I need help to determine the memory leak, to resolve the very long respond time or exits any possibility to tune the tomcat integration? Now it is not possible to work in this environment. Well I understand, but I have no idea what can be the reason. Could you please try to deploy and run your application: A) on Tomcat started outside of the IDE B) on the same Tomcat added as external Tomcat into IDE and started from IDE? Thanks. The difference (usage of memory after the first request) with and without ide: IDE Netbeans 4.1 (or 3.6): respond time: some minutes java.exe 325.392 K java.exe 288.380 K Tomcat 5 (standalone without IDE): tomcat5.exe 96.168 K (with some more webapps as the ide!) respond time: some seconds This doesn't seem to me like a NB bug very much. Can you please response these questions 1. What throws the OutOfMemoryError, NetBeans or Tomcat? Can you provide the stack trace and Tomcat output? 2. How much memory does your system have? 3. Didn't you modify Tomcat servlet.xml configuration file somehow? 4. Couldn't be to problem caused by some other already deployed application? 1. What throws the OutOfMemoryError, NetBeans or Tomcat? Can you provide the stack trace and Tomcat output? I think Tomcat, how do I can provide the stack trace? 2. How much memory does your system have? I have 2 GB RAM (with swap 4 GB). 3. Didn't you modify Tomcat servlet.xml configuration file somehow? I didn't modify the servlet.xml. 4. Couldn't be to problem caused by some other already deployed application? No other nonstandard-application will be deployed. I have a idea. It is possible that the problem may concerns the http-monitor? Many objects will be saved in the session, it is possible to deactivate the http-monitor for a test? Yes, I wanted to suggest you the very same thing. To deactive the HTTP Monitor go to the Window | Runtime | Servers | your Tomcat instance - > Properties and uncheck the "Enable HTTP Monitor" context menu. Now, restart the Tomcat server for the changes to take effect. Yes, in my context is the problem the http-monitor. I have to talk with the developer to use the sessioncontext carefully. :-) Thank for the help to resolve my problem. Setting the proper resolution. Marking as INVALID. Maybe this performance problem should be explained in the faq? We don't have any example of a real-world WebApp which would cause this problem. I think it can happen only in really extreme WebApps (mostly caused by bugs or misusage of session context etc.) Anyway if you have a real-world example, please let us know. I want to analyze this problem in detail. First how do I can determine the http-monitor protocol? |