- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
"Java.lang .NullPoint erExceptio n" error message when running IxLoad
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-02-2010 01:18 PM
We are getting "Java.lang.NullPointerException" error message when attempting to running IxLoad 4.10.94.82 EA SP1-Patch1 with Itest 3.4.2.
Havs anyone seen this problem before?
Attached are env vairable and error text.
Re: "Java.lang .NullPoint erExceptio n" error message when running IxLoad
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-02-2010 02:10 PM
Can you post the .log file located in the .metadata folder of your workspace?
Re: "Java.lang .NullPoint erExceptio n" error message when running IxLoad
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-02-2010 03:09 PM
Attached .log
Re: "Java.lang .NullPoint erExceptio n" error message when running IxLoad
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-02-2010 04:18 PM
Hi:
I took a look at what may be causing the NullPointer, and I've filed a bug for it (KAZ-20286). However, looking at the cause, it looks to me like something in IxLoad is improperly installed. Let me explain what's happening under the hood a bit so we can verify if this is the cause (and hopefully help you work around it). Firstly, we try to find the IxLoad package through the tcl command "package require IxLoad"
Essentially, we're looking in the registry for an installed version of IxLoad: specifically, we're looking at:
HKEY_LOCAL_MACHINE\Software\Ixia Communications\IxLoad\CURRENT_VERSION\InstallInfo for a value called HOMEDIR. If that's not there, then that value will be null, and you'll get the Null Pointer Exception; the only reason I can think of that this isn't there is that IxLoad isn't installed on your machine or is installed incorrectly.
What is CURRENT_VERSION? Basically, we look at all the nodes under HKEY_LOCAL_MACHINE\Software\Ixia Communications\IxLoad and pick the highest version number (mine is 4.10.94.82).
What I'd suggest is using regedit on the command line to check to make sure those nodes are all there: if they aren't, your IxLoad install may have issues and need to be reinstalled.
Re: "Java.lang .NullPoint erExceptio n" error message when running IxLoad
[ Edited ]
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-05-2010 08:25 AM - last edited on 04-05-2010 08:25 AM
My current IXLOAD version is 4.10.94.82.
I had a newer version installed 4.10.94.84, but I uninstalled it because it wasn't compatible with my version of IXOS.
There were 3 versions listed under HKEY_LOCAL_MACHINE\Software\Ixia Communications\IxLoad\CURRENT_VERSION\InstallInfo
Restrated the PC and it is working.
Another question: Which folder is iTest looking when you run the comand >>SHOW TEST
in other words where should I save my IXLOAD test files .rxf in order to load them in iTest?
Thanks
Re: "Java.lang .NullPoint erExceptio n" error message when running IxLoad
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-05-2010 09:58 AM
Well, in the IxLoad Session Profile, there's a configuration file that you can specify (see the attached screenshot). So, really, you can have the .rxf files anywhere and just point to them in your session profile, although I usually recommend having them in your workspace so the tests aren't reliant on any particular folder configuration. There's also a results folder: this specifies where the .csvs and such that get generated go.
Out of curiosity, had you restarted your iTest after uninstalling that version of IxLoad? If not, I can see how that NPE could have been generated; the registry copy that we get is updated when iTest opens, so it would have been looking at that older version to find something that isn't there.
Either way, I'm glad restarting fixed it: we've fixed up the NPE, and it should be available in future versions of iTest (legal issues prevent me from actually specifying which one).
