For "configuration" kind of errors the first thing that I would try to
correct it is to start RDI with the -clean parameter. Modify the shortcut
used to start RDI by adding " -clean" (sans quotes) then close (if it is
running) and restart RDI. Alternatively try a new workspace to see if it
is tied to your workspace or the install.
The message would indicate that something in the workspace is giving up
waiting for something to spin up. Do you have a code coverage test set up
with a WAS instance on the machine for example? Or there could be a code
coverage job pending with the IBM i and it is waiting to connect to the
host - check the code coverage and debug views for residual stuff?
Maybe even take a peek in the preferences under General > Startup &
Shutdown (or something like that) and disable the activation of possibly
relevant plugins at startup to see if you can track down the cause.
All the best, Mike
Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
From: Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>
To: "Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date: 2016/11/14 04:24
Subject: [WDSCI-L] "An error has occurred" the first time I restart RDi
after reboot
Sent by: "WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Every time I restart my PC (overnight, or during the day) I can not start
RDi the first time. But all subsequent attempts to start RDi are
successful. (Win10, RDi 9.5.1)
An error message pops up titled "Eclipse" saying:
"An error has occurred. See the log file
C:\IBM\SDP|configuration\1479113761760.log"
And the log file contains several stack traces. The first few lines are
repeated here:
!ENTRY org.eclipse.osgi 2 0 2016-11-14 08:56:40.783
!MESSAGE While loading class
"com.ibm.rational.llc.internal.core.CoverageCorePlugin", thread
"Thread[Component Resolve Thread (Bundle 753),10,main]" timed out waiting
(5000ms) for thread "Thread[Component Resolve Thread,5,main]" to finish
starting bundle "org.eclipse.core.runtime_3.10.0.v20140318-2214 [538]". To
avoid deadlock, thread "Thread[Component Resolve Thread (Bundle
753),10,main]" is proceeding but
"com.ibm.rational.llc.internal.core.CoverageCorePlugin" may not be fully
initialized.
!STACK 0
org.osgi.framework.BundleException: Unable to acquire the state change lock
for the module: osgi.identity; osgi.identity="org.eclipse.core.runtime";
type="osgi.bundle"; version:Version="3.10.0.v20140318-2214";
singleton:="true" [id=538] STARTED [STARTED]
at org.eclipse.osgi.container.Module.lockStateChange(Module.java:329)
at org.eclipse.osgi.container.Module.start(Module.java:389)
at org.eclipse.osgi.framework.util.SecureAction.start
(SecureAction.java:454)
...
If I click OK on the error popup then try to start RDi again, it is
successful. In fact, any attempt to start RDi is successful from then on
until I restart my PC. This has been happening since 1st November, 2016.
Anyone know what might be wrong? I'll raise a PMR when I get the necessary
details, but if someone else already knows what is wrong then I'd be
grateful to find out.
-Paul.
--
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.