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: | Cannot start profiler with JBoss | ||
|---|---|---|---|
| Product: | profiler | Reporter: | Jiri Skrivanek <jskrivanek> |
| Component: | Ide | Assignee: | Tomas Hurka <thurka> |
| Status: | VERIFIED WORKSFORME | ||
| Severity: | normal | CC: | hanasaki, hilmer, mmirilovic, phejl, pjiricka |
| Priority: | P3 | ||
| Version: | 7.3.1 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | 200165 |
| Attachments: |
stacktrace
Stack trace from JBoss server log. |
||
|
Description
Jiri Skrivanek
2013-04-23 09:10:30 UTC
Created attachment 133699 [details]
stacktrace
Similar use case but different error: - create web project with JBoss 7.2.0 - try to profile project but it fails with exception in server log Created attachment 133700 [details]
Stack trace from JBoss server log.
Jirko, I'm getting a different exception. The server is complaining about LogManager in my case. Is that the same for you? Yes, it is the second use case (comment 2, attachment 133700 [details]). I'm passing the additional parameter, but it does not really fix the problem. web-main c0cb470e8a00 It looks like JBoss does not play well with agents/environments where logging is initialized sooner than JBoss gets to it. https://issues.jboss.org/browse/AS7-1547 http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.logmanager/jboss-logmanager/1.2.0.GA/org/jboss/logmanager/Logger.java#Logger Tomasi, can you do anything about that in profiler/agent to avoid that? Integrated into 'main-golden', will be available in build *201305142300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/c0cb470e8a00 User: Petr Hejl <phejl@netbeans.org> Log: #228881 - AssertionError: Instance JBoss Application Server started again without proper stop Tomasi is it possible to workaround/fix it in the profiler agent? If not I'll disable profiling for JBoss AS 7. Thanks. According to Tomas Hurka, it is not possible to fix this properly for 7.3.1 - just for 7.4. PetreH, so do you plan to disable profiling of JBoss 7 for 7.3.1? Thanks. (In reply to comment #10) > According to Tomas Hurka, it is not possible to fix this properly for 7.3.1 - > just for 7.4. PetreH, so do you plan to disable profiling of JBoss 7 for 7.3.1? > Thanks. I must say I tried that however only services view respects the profile ability flag. Project still allow user to profile it - I suppose the project/ant does not really check the server. This would need some changes both on project and server side. I think this not worth doing for 7.3.1 considering the risk. Ok, waiving this issue for 7.3.1 (adding 731-not-a-stopper whiteboard). *** Bug 233378 has been marked as a duplicate of this bug. *** If this is hard to fix we could lower it to P3 as issue #202587 is fixed and JBoss 7 now declare it does not support profiling. I verified that the JBoss node in Services does not contain the Start in Profile Mode menu item, and when profiling project that uses JBoss as the target server, a graceful information message about unsupported profiling is displayed. Changing to P3 defect as discussed above, and assigning to profiler. Just installed Netbeans 7.4RC2 to get around this, also tried to use remote profiling but that fails as well. But it does not seam to be fixed for 7.4 yet, can I expect a fix when final comes out? Reported for 7.3.x or earlier, no new info since then -> closing as worksforme, please reopen in case you see it. Not supported. |