Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 597067 - NumberFormatException: For input string: "" in JBossSoftwareContentSourceAdapter.initialize
NumberFormatException: For input string: "" in JBossSoftwareContentSourceAda...
Product: RHQ Project
Classification: Other
Component: Plugins (Show other bugs)
All Linux
low Severity medium (vote)
: ---
: ---
Assigned To: John Mazzitelli
Mike Foley
Depends On:
Blocks: jon3
  Show dependency treegraph
Reported: 2010-05-27 23:56 EDT by Ondřej Žižka
Modified: 2014-05-29 14:14 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-29 14:14:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log snippet (11.80 KB, text/plain)
2010-05-28 00:04 EDT, Ondřej Žižka
no flags Details

  None (edit)
Description Ondřej Žižka 2010-05-27 23:56:13 EDT
Version-Release number of selected component (if applicable):
JON 2.3.0

Steps to Reproduce:

1. Create a CSP Content source with 
  anr appropriate credentials 

2. tail -f rhq-server/logs/...

3. Click Test / Synchronize

4. See the exception in the log

Stack trace attached.
Comment 1 Ondřej Žižka 2010-05-28 00:04:33 EDT
Created attachment 417461 [details]
log snippet
Comment 2 Ondřej Žižka 2010-05-28 00:58:24 EDT
This is probably caused by an attempt to parse an empty Proxy Settings, which values are not set as unset by default.

first fix the NPE (validate proxy values properly), 
then set those values as unset by default.
Comment 3 Ondřej Žižka 2010-07-02 16:48:44 EDT
Steps to reproduce, should happen every time:

1) Create a CSP account, but ommit the Name field. JON will complain.
2) Fill the Name. And submit. JON will eat this.
3) tail -f -n 1000 log ,  and see the attached exception there.
Comment 4 Simeon Pinder 2010-07-02 17:00:43 EDT
Looks like we're not checking or enforcing that the name field is filled in when it obviously must be and we're assuming that it already filled in in the code.

Need to add required field check in UI and double check in code to prevent using bad data.

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