If an exception is throw, it leads to a null pointer: Failed to complete the JDR report: JBAS013352: Zipfile could not be created. Exception in thread "main" java.lang.NullPointerException at org.jboss.as.jdr.CommandLineMain.main(CommandLineMain.java:96) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) at java.lang.reflect.Method.invoke(Method.java:613) at org.jboss.modules.Module.run(Module.java:292) at org.jboss.modules.Main.main(Main.java:455)
Brad Maxwell <bmaxwell> updated the status of jira WFLY-3016 to Coding In Progress
Move the prints into the try { } since if standaloneCollect throws an exception, the response object will be null
Verified on EAP 6.3.0.DR2.
Brad, you say in comment 2 "...since if standaloneCollect throws an exception, the response object will be null". I was wondering if you could clarify if the response object being null was the cause of, or the solution to, the NPE problem.