The Netbeans embedded application server automatically shuts down whenever you perform any of the following project operations:
Clean Project
Create Delta Distribution
Create Jar
Debug Project
Manage Embedded Repository
Profile Project
Run Project
The Identity Manager IDE Debugger is sluggish. What could be causing this problem?
Answer:To improve the Debugger’s performance:
Always disable Tomcat’s HTTP Monitor, as follows:
Select the Identity Manager IDE Runtime Tab.
Expand the Servers node and right-click Bundled Tomcat > Properties.
Disable the Enable HTTP Monitor option, and then close the dialog.
The next time you start Tomcat, the HTTP Monitor will be disabled.
If you are not debugging Java, select Project > Run Project, and then select Attach Debugger > Identity Manager XML Object Debugger to use just the XPRESS Debugger.
Selecting Project > Debug Project for a non-remote Identity Manager IDE project starts both the XPRESS Debugger and Java Debugger, and the Java Debugger adds substantial overhead.
I cannot set a breakpoint in the Debugger. What could be causing this problem?
Answer:The following conditions might prevent you from setting a breakpoint:
You just installed the NBM, but did not restart Netbeans.
Your XML contains a <Waveset> wrapper element.
The Identity Manager IDE basically ignores any file that starts with a <Waveset> wrapper element because the Identity Manager IDE parses that element as a multi-object file.
The following features do not work on multi-object files:
Debugger
Rule Tester
Form Previewer
Any of the editors
Import file generator
Upload Object
Diff Object
Basically, all you can do with multi-object files is import them. The only files that should contain <Waveset> wrapper elements are your project’s top-level import files.
I set a breakpoint in the Debugger and it is not suspending on the breakpoint. What could be causing this problem?
Answer:There are two things to check:
Be sure the object name does not contain a CBE replacement string (%%). CBE replacement strings are not allowed in object names.
Verify that the code you think is being executed is actually being executed. Try adding a trace and see if anything prints out.