You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment:
JVM Monitor 3.8.1.201302030008
What steps will reproduce the defect?
1. Open JVM monitor perspective
2. Add remote server ( add ip n port )
3. go to properties
4. go to CPU tab
5) Configure BCI and add copule of packages
6) Click ok and see the Call tree graph for couple of mints
...
What is the expected behavior?
- IT SHOULD MONITOR CONTINUALLY
What was the actual behavior?
- Property window suddenly despairer
What errors are shown on Error Log view or at <workspace>/.metadata/.log?
- attached
What is your environment for Eclipse?
Eclipse Java EE IDE for Web Developers.
Version: Kepler Release
Build id: 20130614-0229
(c) Copyright Eclipse contributors and others 2005, 2013. All rights reserved.
Visit http://www.eclipse.org/webtools
UBUNTU Release 12.04 (precise) 32-bit
Kernel Linux 3.5.0-40-generic
3.7 GiB RAM
Intel® Core™ i3 CPU M 380 @ 2.53GHz × 4
What is your environment for the monitored JVM?
15:26:08,801 INFO [ServerInfo] Java version: 1.7.0_03,Oracle Corporation
15:26:08,801 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM
22.1-b02,Oracle Corporation
15:26:08,801 INFO [ServerInfo] OS-System: Linux 2.6.18-348.4.1.el5,i386
Original issue reported on code.google.com by kchatura...@gmail.com on 6 Nov 2013 at 10:40
I can confirm this bug and have exactly the same stack trace.
Software:
- JVM Monitor 3.8.1.201302030008
- Eclipse IDE for Java Developers 4.4.0 (Luna)
- #java -version
java version "1.7.0_55"
OpenJDK Runtime Environment (IcedTea 2.4.7) (Gentoo build 1.7.0_55-b14)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
- Gentoo Linux 64 Bit
Hardware:
- Core i7-3770
- 16G RAM
Original comment by schallus...@gmail.com on 24 Sep 2014 at 1:10
Original issue reported on code.google.com by
kchatura...@gmail.com
on 6 Nov 2013 at 10:40Attachments:
The text was updated successfully, but these errors were encountered: