-
Well let me accept the bug with following context.
- Jensor Analysis takes long time for analyzing 250 MB worth of data.
- The slowness is observed only when log sizes grow beyond 50 MB.
This has been fixed in version 1.12. Pls. await release.
2009-10-22 17:36:30 UTC in Jensor Java Profiler
-
Hi,
Am afraid that's not a Jensor or even a Java related problem. Its got to do with the X server you are using. The post itself mentions
"Please file an enhacement request (quoting the above) at: http://bugs.freedesktop.org/enterbug.cgi?product=cairo"
Jensor development happens on Linux and for sure we are able to see Jensor UI on Linux X.
I guess you can try following...
2009-10-22 17:17:18 UTC in Jensor Java Profiler
-
This bug is for Windows version of Jensor 1.11 and is reproducible. Will be fixed in next release.
2009-10-21 03:52:47 UTC in Jensor Java Profiler
-
Hi Felipe,
Appreciate your asking questions. I hope we are able to help.
1) Jensor works on the concept of Byte code instrumentation. Currently, the instrumentation is done manually by using the GUI (Jensor Analysis Workbench) or through a set of command line utilities.
2) For instrumenting an application (jar, war, ear files), one needs to create a project.
3) Then the instrumented...
2009-10-12 05:30:52 UTC in Jensor Java Profiler
-
temp.env itself is used for finding out value of JENSOR_HOME. So writing temp.env to JENSOR_HOME\bin is out of question. However we can look into other options like writing to temp directory or writing to user's home directory where user has write permissions.
2009-10-07 09:40:10 UTC in Jensor Java Profiler
-
Good.
Suggest one reading of Jensor Usage Manual. You should find it under docs folder in Jensor installation directory. All features and operational modalities are documented here.
-Cheers
Amol.
2009-09-24 08:56:41 UTC in Jensor Java Profiler
-
Pls. provide more details. Which version of Jensor are you using? A similar bug titled "Recursive instrumentation" is fixed. Take a look at that response and re-post with your environment details.
2009-08-31 09:38:22 UTC in Jensor Java Profiler
-
Hi Moon,
The fifth column i.e overheads - is value in milliseconds. Jensor monitors and reports its own overheads. This column is that number. There is no level or range for this column.
Usually only first line has a non-zero value. Later it remains uniformly zero most of the times.
Cheers,
Amol.
2009-06-17 04:08:10 UTC in Jensor Java Profiler
-
Hi,
Does only this class from Spring throw this exception or others classes too? Also, is the error reproducible across different stacks?
Right now I have no clue what could be causing this error. That said I have never tested Jensor on 1.6. Looks like there is some homework to do.
- Amol.
2009-06-07 12:12:04 UTC in Jensor Java Profiler
-
Hi Mehul,
You will need to increase the memory alloted to JAW if you will be collating huge files. This change can be made in startup.bat under %JENSOR_HOME%\bin
Next, to reduce the filesize i.e the data logged into these files you can explore usage of Selective instrumentation and Selective Profiling (Filters). Procedures for the same are documented in user manual.
- Amol.
2009-05-28 07:05:25 UTC in Jensor Java Profiler
