Bug 1069850 – [GSS] (6.3.0) Prevent NullPointerException in JDR CommandLineMain

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1069850 - [GSS] (6.3.0) Prevent NullPointerException in JDR CommandLineMain

Summary:	[GSS] (6.3.0) Prevent NullPointerException in JDR CommandLineMain

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	JDR (Show other bugs)
Sub Component:
Version:	6.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR2
Target Release:	EAP 6.3.0
Assigned To:	Brad Maxwell
QA Contact:
Docs Contact:	Scott Mumford

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1069894
	Show dependency tree / graph

Reported:	2014-02-25 14:02 EST by Brad Maxwell
Modified:	2014-06-29 18:31 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	In previous versions of JBoss EAP 6, an NullPointerException would be thrown whenever an exception was thrown from JDR CommandLineMain. This issue has been corrected in this release.
Story Points:	---
Clone Of:
Clones:	1069894 (view as bug list)
Environment:
Last Closed:	2014-06-28 11:32:03 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	smumford: needinfo-

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-3016	Major	Resolved	Prevent NullPointerException in JDR CommandLineMain	2014-08-04 15:22:13 EDT

Groups: None (edit)

Description Brad Maxwell 2014-02-25 14:02:38 EST

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)

Comment 1 JBoss JIRA Server 2014-02-25 14:22:13 EST

Brad Maxwell <bmaxwell@redhat.com> updated the status of jira WFLY-3016 to Coding In Progress

Comment 2 Brad Maxwell 2014-02-25 14:24:29 EST

Move the prints into the try { } since if standaloneCollect throws an exception, the response object will be null

Comment 4 Petr Kremensky 2014-03-10 05:14:21 EDT

Verified on EAP 6.3.0.DR2.

Comment 5 Scott Mumford 2014-04-24 01:13:30 EDT

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.

Note You need to log in before you can comment on or make changes to this bug.