Hi Michael,
No, it is not the debug damon port. It is the same exception and stack trace that I get in the Eclipse error log, when I start WDSCi:
Stack trace, when I start the test application:
java.lang.UnsupportedClassVersionError: (com/ibm/cds/CDSHookConfigurator) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$400(Unknown Source)
at java.net.URLClassLoader$ClassFinder.run(Unknown Source)
at java.security.AccessController.doPrivileged(Unknown Source)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.eclipse.osgi.baseadaptor.HookRegistry.loadConfigurators(Unknown Source)
at org.eclipse.osgi.baseadaptor.HookRegistry.initialize(Unknown Source)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.createAdaptor(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.core.launcher.Main.basicRun(Unknown Source)
at org.eclipse.core.launcher.Main.run(Unknown Source)
at org.eclipse.core.launcher.Main.main(Unknown Source)
Entry of the Eclipse error log, when I start WDSCi:
<JIT: FullSpeedDebug: ignoring countString>
!SESSION 2015-12-04 07:25:29.294 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Vista x86-32 j9vmwi3223ifx-20080811 (JIT enabled)
J9VM - 20080809_21892_lHdSMr
JIT - 20080620_1845_r8
GC - 200806_19
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en
Framework arguments: -product com.ibm.etools.iseries.wdsc.welcome.ide -pdelaunch
Command-line arguments: -product com.ibm.etools.iseries.wdsc.welcome.ide -data C:\workspaces\rdp_070\workspace/../runtime-Eclipse-Anwendung -dev file:C:/workspaces/rdp_070/workspace/.metadata/.plugins/org.eclipse.pde.core/iSphere - en/dev.properties -pdelaunch -os win32 -ws win32 -arch x86 -consoleLog -clean
!ENTRY org.eclipse.osgi 4 0 2015-12-04 07:25:29.397
!MESSAGE error loading hook: com.ibm.cds.CDSHookConfigurator
!STACK 0
java.lang.UnsupportedClassVersionError: (com/ibm/cds/CDSHookConfigurator) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:258)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:151)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:589)
at java.net.URLClassLoader.access$400(URLClassLoader.java:123)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1034)
at java.security.AccessController.doPrivileged(AccessController.java:279)
at java.net.URLClassLoader.findClass(URLClassLoader.java:491)
at java.lang.ClassLoader.loadClass(ClassLoader.java:631)
at java.lang.ClassLoader.loadClass(ClassLoader.java:597)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:130)
at org.eclipse.osgi.baseadaptor.HookRegistry.loadConfigurators(HookRegistry.java:158)
at org.eclipse.osgi.baseadaptor.HookRegistry.initialize(HookRegistry.java:97)
at org.eclipse.osgi.baseadaptor.BaseAdaptor.<init>(BaseAdaptor.java:97)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:522)
at org.eclipse.core.runtime.adaptor.EclipseStarter.createAdaptor(EclipseStarter.java:780)
at org.eclipse.core.runtime.adaptor.EclipseStarter.startup(EclipseStarter.java:280)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:618)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:996)
at org.eclipse.core.launcher.Main.main(Main.java:971)
Obviously WDSC can start despite the error, whereas the test application cannot ignore it.
I assume that the current problem is "com.ibm.cds_3.0.1.201410101357.jar", which has been compiled for Java 6. All other versions of the "com.ibm.cds" plug-in have been compiled for Java 1.2 or Java 5.
I wonder why WDSC tries to load that jar although it has a dependency to bundle "org.eclipse.osgi" 3.10.0? I also wonder why the Eclipse Plug-ins view shows "com.ibm.cds (2.0.2.200702070926)", which is the correct plug-in.
Thomas.
-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von MichaelQuigley@xxxxxxxxxx
Gesendet: Donnerstag, 3. Dezember 2015 20:16
An: wdsci-l@xxxxxxxxxxxx
Betreff: Re: [WDSCI-L] Cannot start WDSC 7.0 after having installed RDi 9.5
Thomas,
Is it possible that it's using the same Debug Daemon port (Preferences, Run/Debug, Debug Daemon) as an active RDi session?
Michael Quigley
Computer Services
The Way International
www.TheWay.org
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 12/03/2015 01:00:05 PM:
----- Message from Thomas Raddatz <thomas.raddatz@xxxxxx> on Thu, 3
Dec 2015 07:31:59 +0000 -----
To:
"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Subject:
Re: [WDSCI-L] Cannot start WDSC 7.0 after having installed RDi 9.5
Hm, seems that I am talking to myself. The problem is back again. I
can start WDSCi 7.0, which is good. But I cannot start an Eclipse test
application, which is bad. The symptoms are the same as it has been
with WDSCi. The test application tries to start again and again with
no success, until I click the "Terminate" button of the "Console"
view.
Thomas.
-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von
Thomas Raddatz
Gesendet: Donnerstag, 3. Dezember 2015 08:11
An: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries
Betreff: Re: [WDSCI-L] Cannot start WDSC 7.0 after having installed
RDi
9.5
Never mind.
Although I am pretty sure that I already tried to start it with the
"-clean" option (that is what we all usually do first), it works
again, now. It does not work without "-clean", but that is a minor
issue.
--
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.
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.
midrange.com
