Bugzilla – Full Text Bug Listing
| Summary: | Errors when starting gEclipse with opened data stager | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Szymon Mueller <mael> |
| Component: | Geclipse | Assignee: | Mathias Stümpert <mathias.stuempert> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | aog-ecl, sxenos |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Szymon Mueller
Not sure if it is core or gria data stager related. Mathias?? I can reproduce it. Strange: Caused by: java.lang.RuntimeException: Cannot find security configuration file crypto.properties in classpath at uk.ac.soton.ecs.iam.grid.comms.client.AbstractTransport.<init>(AbstractTransport.java:126) (...) Caused by: java.util.MissingResourceException: Can't find bundle for base name crypto, locale pl_PL uhuhu... (same for me with "locale en_US"!!) I debugged it and can give some explanation why this is happening: 1. During startup text editor tries to open the data stager file. 2. This triggers fetching the info from the GriaStore. 3. The fetchInfo() method tries to create DataConversation item ( using repository.getOrCreateObject(...) ), which fails because no token is yet created. I tried to run authentication at the start of fetchInfo(), but it results in a token request at gEclipse startup, and file is not opened anyway. This behavior is similar to Bug #241930 for srm and gsiftp. So more general approach is needed for usecase when gEclipse is starting with opened remote file in the text editor. 1) The GRIA related parts of this bug will be completely replaced by the new GRIA AAI stuff, so we have to check again afterwards (hopefully today). 2) The new GRIA AAI will nevertheless not solve the problem with authentication at startup. Nevertheless, of course if I leave a remote thingy open when closing g-Eclipse I should be aware of the fact the I have to go online again at startup. So at least this is not show-stopper here for me and we have to investigate how much work (arounds) is needed in order to fix it. If it turns out to be too complicated I vote for leaving it as is. > The new GRIA AAI will nevertheless not solve the problem with
> authentication at startup
having an auth request at startup would be fine for me if i know a remote file has to be opened... but:
i would probably make sense to force closing all remote editors at shutdown time anyways, it is somehow "cleaner" and more performant than allowing the user keep many remote files open...
i don't know how feasible that would be. And of course if g/eclipse crashes we could still have the same issue...
Some more observation on this: 1) When restarting g-Eclipse with an open GRIA file the problem is not only that the file is not displayed and the above mention exception is thrown but additionally the project view is empty, i.e. the projects do not show up. 2) When restarting g-Eclipse with another connection like gsiftp a token is requested but the file is not opened. The editor then shows an error message like "File [...] does not exist". Conclusion: We need a general solution for this problem, it is not GRIA specific! *** Bug 241930 has been marked as a duplicate of this bug. *** With the change to Ganymede the behaviour with open remote files seems to have changed slightly. Now when Eclipse is closed with a file opened in an editor the editor caches the file locally (temporarily) in order to save its state. That means that the file is copied to the hard disk at shutdown time which does not make any sense for us. So instead of improving their handling with remote files they just made things worse. Keeping this bug up to date as I (hopefully) make some progress towards a solution. It's possible the root cause may be bug 479475. Actually, I'll optimistically mark this as a dupe. Please reopen if it recurs after the fix for bug 479475 goes in. *** This bug has been marked as a duplicate of bug 479475 *** |