Task #2976 (closed)
Opened 14 years ago
Closed 12 years ago
Bug: communicator destroy prevents files from being added
Reported by: | jamoore | Owned by: | |
---|---|---|---|
Priority: | critical | Milestone: | OMERO-4.4 |
Component: | Import | Version: | n.a. |
Keywords: | n.a. | Cc: | cxallan |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | 2012-01-17 (6) |
Description
If the server is restarted (and the clients communicator destroyed), the "logout" symbol in the status bar is correctly displayed, but the standard out is filled with exceptions of the form:
Exception in thread "AWT-EventQueue-0" Ice.CommunicatorDestroyedException at IceInternal.Instance.objectAdapterFactory(Instance.java:122) at Ice.ObjectPrxHelperBase.createDelegate(ObjectPrxHelperBase.java:997) at Ice.ObjectPrxHelperBase.__getDelegate(ObjectPrxHelperBase.java:946) at omero.api.IAdminPrxHelper.getEventContext(IAdminPrxHelper.java:1348) at omero.api.IAdminPrxHelper.getEventContext(IAdminPrxHelper.java:1322) at ome.formats.OMEROMetadataStoreClient.getExperimenterID(OMEROMetadataStoreClient.java:2118) at ome.formats.OMEROMetadataStoreClient.getProjects(OMEROMetadataStoreClient.java:2180) at ome.formats.importer.gui.ImportDialog.<init>(ImportDialog.java:149) at ome.formats.importer.gui.FileQueueHandler.handleFiles(FileQueueHandler.java:398) at ome.formats.importer.gui.FileQueueHandler.addSelectedFiles(FileQueueHandler.java:277) at ome.formats.importer.gui.FileQueueHandler.doSelection(FileQueueHandler.java:205) at ome.formats.importer.gui.FileQueueHandler.propertyChange(FileQueueHandler.java:453) at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339) ... at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
which prevents the user from using the "+" button. This makes sense, but is very suprising. A popup with a login dialog or similar should be shown.
Change History (4)
comment:1 Changed 13 years ago by jburel
- Cc bwzloranger added
comment:2 Changed 12 years ago by jmoore
- Cc jburel bwzloranger removed
- Owner set to jburel
Jean-Marie: passing to you. Do we have a container of these importer issues which may/may not get cleaned up? I added it to #2118 which might be a good candidate.
comment:3 Changed 12 years ago by jburel
- Owner jburel deleted
I do not have a story. The one you picked is perfect for that.
As discussed today, we need a decision sooner rather than later. I do not have time to maintain the old importer and I do not see the benefit now that. If you look at the tasks attached to the story, many have been implemented in insight-importer.
we can run the insight-importer as a standalone app (similar to editor). This will obviously affect the build targets too
comment:4 Changed 12 years ago by jmoore
- Cc cxallan added
- Milestone changed from Unscheduled to OMERO-Beta4.4
- Resolution set to wontfix
- Sprint set to 2012-01-17 (6)
- Status changed from new to closed
Marking as "wontfix" then. If we decide to clean the importer code, then we can re-open.
Problem still there.