-
Type:
Bug
-
Resolution: Resolved Locally
-
Priority:
Low
-
None
-
Affects Version/s: 3.3
-
Component/s: Administration - Others
-
Environment:
Java Version 1.4.2
Java Vendor IBM Corporation
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.4.2
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Classic VM
User Locale English
System Encoding ISO8859-1
Operating System AIX 5.3
OS Architecture ppc
Application Server Container Apache Tomcat/5.5.7
Database type oracle10gJava Version 1.4.2 Java Vendor IBM Corporation JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.4.2 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Classic VM User Locale English System Encoding ISO8859-1 Operating System AIX 5.3 OS Architecture ppc Application Server Container Apache Tomcat/5.5.7 Database type oracle10g
-
3.03
After I click, 'Force garbage collection', the uptime counter is reset. This doesn't seem right! Also, it seems that the session is destroyed, as I need to log back in just after I force garbage collection. If this is the proper behavior, it should be documented with perhaps some explanation as to the rationale.
