question

dante347 avatar image
dante347 asked dante347 posted

Creating new response map produces "Unhandled event loop exception" error

Hi,

 

I'm now observing the following error when I attempt to create a new response map from the "Response" view:

 

eclipse.buildId=unknown

java.version=1.6.0_13

java.vendor=Sun Microsystems Inc.

BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US

Command-line arguments:  -os linux -ws gtk -arch x86 -clean

 

 

Error

Wed Mar 31 11:54:31 PDT 2010

Unhandled event loop exception

 

java.lang.NullPointerException

at com.fnfr.svt.mapping.ui.wizards.ResponseMapNewWizardExistingProjectPage.setContainerChoices(ResponseMapNewWizardExistingProjectPage.java:135)

at com.fnfr.svt.mapping.ui.wizards.ResponseMapNewWizardExistingProjectPage.createControl(ResponseMapNewWizardExistingProjectPage.java:80)

at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1147)

at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1139)

at org.eclipse.jface.wizard.WizardDialog$4.run(WizardDialog.java:1128)

at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)

at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1126)

at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:820)

at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:369)

at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)

at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)

at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

at org.eclipse.jface.window.Window.open(Window.java:801)

at com.fnfr.svt.mapping.ui.actions.NewResponseMapWizardAction.run(NewResponseMapWizardAction.java:43)

at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)

at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583)

at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500)

at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)

at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)

at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)

at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)

at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)

at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)

at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)

at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)

at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)

at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)

at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)

at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)

at com.fnfr.svt.rcp.Application.runWorkbench(Application.java:218)

at com.fnfr.svt.rcp.Application.start(Application.java:203)

at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)

at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)

at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)

at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)

at org.eclipse.equinox.launcher.Main.run(Main.java:1236)

 

Note: I've used "iTest -clean" without success.

 

Thanks ahead,

 

Dante

 

iTestresponse map
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
KumarS avatar image
KumarS answered KumarS posted

Which version of iTest are you using?

5 comments
10 |950

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

dante347 avatar image dante347 commented ·

version 3.4.3

0 Likes 0 ·
PaulD avatar image PaulD dante347 commented ·

I took a quick look through the code.  This could only potentially happen, I believe, if we're dealing with a weird case -- like a project that is closed or a reference to a file that doesn't exist.  Is there anything funny about your workspace?  Perhaps your session profile refers to a response map library that doesn't currently exist?

 

In any case, this is a bug.  But in looking at an immediate workaround, I'd suggest looking to see if there is something here referring to something that is closed or doesn't exist.

0 Likes 0 ·
YujieL avatar image YujieL PaulD commented ·

I've filed a bug.

0 Likes 0 ·
dante347 avatar image dante347 YujieL commented ·

Thanks for filing a bug!

0 Likes 0 ·
dante347 avatar image dante347 PaulD commented ·

The project/response map library folder defined in the .fftb exists and has several .ffrm files that can currently be used for response analysis rules. Note: I'm able to create a response map by defining a new response map library.

0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.