bug #6209
closedNPE in DatasourceView
100%
Description
occurres when connection to remote datasource
java.lang.NullPointerException at eu.etaxonomy.taxeditor.datasource.CdmDataSourceRepository.getAll(CdmDataSourceRepository.java:93) at eu.etaxonomy.taxeditor.view.datasource.CdmDataSourceViewPart.refresh(CdmDataSourceViewPart.java:234) at eu.etaxonomy.taxeditor.view.datasource.CdmDataSourceViewPart.createPartControl(CdmDataSourceViewPart.java:203) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.Perspective.showView(Perspective.java:2245) at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1145) at org.eclipse.ui.internal.WorkbenchPage$20.run(WorkbenchPage.java:3921) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:3918) at eu.etaxonomy.taxeditor.model.AbstractUtility.showView(AbstractUtility.java:191) at eu.etaxonomy.taxeditor.store.CdmStore.getDefault(CdmStore.java:136) at eu.etaxonomy.taxeditor.store.CdmStore.getCurrentApplicationConfiguration(CdmStore.java:304) at eu.etaxonomy.taxeditor.preference.PreferencesUtil.setNomenclaturalCodePreferences(PreferencesUtil.java:500) at eu.etaxonomy.taxeditor.ui.dialog.RemotingLoginDialog.connectButtonPressed(RemotingLoginDialog.java:482) at eu.etaxonomy.taxeditor.ui.dialog.RemotingLoginDialog.access$2(RemotingLoginDialog.java:477) at eu.etaxonomy.taxeditor.ui.dialog.RemotingLoginDialog$6.widgetSelected(RemotingLoginDialog.java:359) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at eu.etaxonomy.taxeditor.ui.dialog.RemotingLoginDialog.open(RemotingLoginDialog.java:209) at eu.etaxonomy.taxeditor.handler.ShowRemotingLoginWindowHandler.execute(ShowRemotingLoginWindowHandler.java:38) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:829) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:815) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:805) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at eu.etaxonomy.taxeditor.Application.start(Application.java:24) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
Related issues
Updated by Katja Luther almost 7 years ago
This was a really confusing error message. The original problem was that the remote database was not available.
Updated by Andreas Müller almost 7 years ago
- Assignee changed from Andreas Müller to Katja Luther
Updated by Andreas Müller almost 7 years ago
- Priority changed from New to Highest
Updated by Katja Luther almost 7 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset taxeditor|af45abb87611c04e93d103bd7c7df6221ca9e877.
Updated by Katja Luther over 6 years ago
- Assignee changed from Katja Luther to Andreas Müller
Updated by Andreas Müller over 6 years ago
- Status changed from Resolved to Feedback
- Assignee changed from Andreas Müller to Katja Luther
The error message is much better now. However, "Problem accessing remote server" is a very short message. We could make it a bit more verbose like "Maybe the server is currently not available. If the problem persists please contact the server admin with the error trace below ...
This is because in this case it is probably not EditSupport responsible but the admin of the server. We may think about providing the admin email for each server instance somehow (new ticket).
Updated by Andreas Müller over 6 years ago
- Has duplicate feature request #5839: Improve error message when server can't be reached added
Updated by Katja Luther over 6 years ago
- Assignee changed from Katja Luther to Andreas Müller
The message is changed and a new ticket for the email of the admin is created (#6335).
Updated by Andreas Müller over 6 years ago
- Status changed from Feedback to Resolved
Updated by Andreas Müller over 6 years ago
- Related to bug #6355: Improve message if server is down added
Updated by Andreas Müller over 6 years ago
- Status changed from Resolved to Closed
- Assignee changed from Andreas Müller to Katja Luther
- % Done changed from 50 to 100
I don't remember how to invoke this message in the moment. But I have seen it recently and I think we can close this ticket. There are follow up tickets and related tickets.
Updated by Andreas Müller over 6 years ago
- Copied to feature request #6335: Providing the admin email for each server installation added