× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



The workspace log is in the ".metadata" folder in the workspace.
It is called ".log" (dot log).

That should contain all the java exceptions that you are getting.

To recover you should first try to run RDI with the "-clean" option. In your RDI shortcut add -clean at the very end of the "Target".
Then start RDI and it might fix itself.

If that doesn't work then make a backup copy of your broken workspace. I suggest compressing it into a zip file. This is so if you try the next steps and don't get a desired result you can press the undo button.

Now, the spool file you tried to open is probably stuck in the list of files that are to be opened every time the workspace starts up.
Those entries are contained in the workbench.xmi file.
\.metadata\.plugins\org.eclipse.e4.workbench\workbench.xmi

Now, if you don't want to fiddle with the workbench file and you are not concerned with preserving your perspectives or views then the easiest solution would be to just remove the folder.
\.metadata\.plugins\org.eclipse.e4.workbench\

Once you restart RDI it will recreate the folder and all of your views will be reset back to defaults.

If you want to keep all of your perspectives and view positions, then you will want to open the file and try to locate and remove the reference to the spool file you tried to open.
The java exception from the workspace log will sometimes give you the xmi:id of the element that it was unable to open.

I have been able to successfully remove these entries from the file but it was nontrivial.
You have to remove the xml element for the file and then make sure that an outer xml element does not reference the element you just removed.

Chris Hiebert
Senior Programmer/Analyst
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Stuart Rowe
Sent: Thursday, October 13, 2016 6:39 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxx>
Subject: [WDSCI-L] RDi suddenly will not start

Dang I have work to do.

So I thought I would try the spooled file viewer that comes in RDi to see if it makes the toolbar appear (from another thread). Well, that blew up
-- hard -- with an out-of-memory error, crashed RDi (but not with a JAVA excpetion stack, it looked like an OS dialog).

Now RDi will not start up!

I rebooted the PC (Windows 10).

I am clueless about logs and such, and troubleshooting this thing. Any clues where logs may be spewing out in failure cases?

It will start up with a new workspace of course (the miracle that is
Eclipse) but I have a ton of filters and syntax highlighting settings I'd like to somehow dig out of the old workspace. Any help with that would be appreciated as well.
--
This is the Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.