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 69084 - [tests] resultsAvailable is sometimes not called on solaris intel machine
Summary: [tests] resultsAvailable is sometimes not called on solaris intel machine
Status: CLOSED WONTFIX
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-22 10:19 UTC by ehucka
Modified: 2007-08-15 16:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2005-11-22 10:19:49 UTC
The method AppStatusHandler.resultsAvailable() is sometimes not called during
profiling on a machine with solaris on intel. 
Automated tests usually start to measure an application after the method is called.
Comment 1 ehucka 2005-11-25 11:05:14 UTC
I've seen it on linux machine too.
Comment 2 iformanek 2005-12-07 19:29:30 UTC
Can you specify the profiling settings? Is it specific to certain settings only?
Comment 3 ehucka 2005-12-08 10:48:05 UTC
I have seen it with such settings last time: (it occures with all instr. schemes)

profiler.settings.code.region.cpu.res.buf.size = 1000
profiler.settings.cpu.profiling.type = CPU_INSTR_FULL
profiler.settings.exclude.wait.time = true
profiler.settings.instr.scheme = *
profiler.settings.instrument.empty.methods = false
profiler.settings.instrument.method.invoke = true
profiler.settings.instrument.spawned.threads = true
profiler.settings.instrumentation.filter.string = 
profiler.settings.instrumentation.filter.type = INCLUSIVE
profiler.settings.instrumentation.root.methods.size = 1
profiler.settings.istrument.getter.setter.methods = false
profiler.settings.istrumentation.root.methods- =
simple/cpu/WaitingTest.main([Ljava/lang/String;)V
profiler.settings.n.profiled.threads.limit = 32
profiler.settings.obj.alloc.stack.sampling.depth = -5
profiler.settings.obj.alloc.stack.sampling.interval = 10
profiler.settings.override.jvm.args = 
profiler.settings.override.port.no = 5140
profiler.settings.run.gc.on.get.results.in.memory.profiling = false
profiler.settings.sampling.interval = 10
profiler.settings.sort.results.by.thread.cpu.time = false
profiler.settings.thread.cpu.timer.on = false

Comment 4 iformanek 2005-12-08 19:34:08 UTC
Added debug println if -Dcom.sun.tools.profiler.server.ProfilerServer=true is 
passed to the profiled VM, please run tomorrow's daily build with this. The 
agent should print a message when the results become available on the server.
Comment 5 Tomas Hurka 2007-03-23 17:30:58 UTC
Is it still valid? 
Comment 6 ehucka 2007-03-23 17:48:52 UTC
there do not run any tests for profiler now, you can close it.
Comment 7 ehucka 2007-06-06 12:01:49 UTC
closing as wontfix, the issue is old and the tests are not running now
Comment 8 ehucka 2007-08-15 16:40:07 UTC
verified closed