- This topic has 26 replies, 4 voices, and was last updated 20 years, 5 months ago by Riyad Kalla.
-
AuthorPosts
-
rparr123MemberHi,
I am trying to start a WebSphere V5 server but I fail. I get the following exception.
I am using: Eclipse 2.1.2; Java 1.4.2 and Win2000Any hint will be appreciated.
Kind regards,
Ralf Parr!MESSAGE com/genuitec/eclipse/easie/websphere5/B (Illegal Field name “?”)
!STACK 0
java.lang.ClassFormatError: com/genuitec/eclipse/easie/websphere5/B (Illegal Field name “?”)
at java.lang.ClassLoader.defineClass0(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$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClass(DelegatingURLClassLoader.java:922)
at org.eclipse.core.internal.plugins.PluginClassLoader.internalFindClassParentsSelf(PluginClassLoader.java:166)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.findClassParentsSelf(DelegatingURLClassLoader.java:485)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:882)
at org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(DelegatingURLClassLoader.java:862)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at com.genuitec.eclipse.easie.websphere5.A.?(Unknown Source)
at com.genuitec.eclipse.easie.websphere5.A.?(Unknown Source)
at com.genuitec.eclipse.easie.websphere5.A.?(Unknown Source)
at com.genuitec.eclipse.easie.websphere5.C.?(Unknown Source)
at com.genuitec.eclipse.easie.core.ui.action.ServerStartAction.basicRun(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.run(Unknown Source)
at com.genuitec.eclipse.core.ui.action.LicenseValidatingAction.runWithEvent(Unknown Source)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:456)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetEvent(ActionContributionItem.java:403)
at org.eclipse.jface.action.ActionContributionItem.access$0(ActionContributionItem.java:397)
at org.eclipse.jface.action.ActionContributionItem$ActionListener.handleEvent(ActionContributionItem.java:72)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:840)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:1838)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1545)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1402)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1385)
at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
Scott AndersonParticipantRalf,
The problem is that you’re trying to launch WebSphere with a non-IBM JDK. IBM heavily modifies the JDK shipped with WebSphere and those changes are vital for proper functionality. WebSphere won’t run on a Sun JDK at all, as far as I know. Reconfiguring your WebSphere connector to use the JDK that IBM ships with the product should resolve this issue.
–Scott
MyEclipse Support
rparr123MemberDear Scott,
I launched WebSphere with the IBM JDK skipped with
WebSphere. Does not solve the problem. Also I tried to start Eclipse
with the IBM-JDK. Does also not solve the problem.
Scott AndersonParticipantRalf,
I’ll have to dig deeper on this. Can you post the full platform information we request in the Posting Guidelines thread?
–Scott
MyEclipse Support
rparr123MemberDear Scott,
I checked my path, classpath and removed all plugins I installed additionally. Now it works fine. Looks like a configuration problem
of my eclipse installation. Thanks for your efforts!
Ralf
Scott AndersonParticipantRalf,
Good to hear you’re up and running. Thanks for the followup as I like nothing better than to close support threads. 🙂
–Scott
MyEclipse Support
RenuTBIMemberI get the very same stack trace in the .log file when I try to launch websphere 5 in debug mode.
Could you please tell me what changes I should make to get websphere 5 working through MyEclipse? Where do I check the path, classpath and plugins as mentioned by Ralf in the previous message? FYI, I only have Perforce plugin installed additionally.
Thanks,
Renu
Riyad KallaMemberWhere do I check the path, classpath and plugins as mentioned by Ralf in the previous message?
I believe he was referring to the Window > Preferences > MyEclipse > App. Servers > Websphere 5 > Paths dialog.
RenuTBIMemberwell, I don’t have any entries in the paths dialog.
Riyad KallaMemberRenuTBI,
You could try PM’ing the user you wanted to ask the question to, he will get a popup next time he visits the site.
RenuTBIMemberWe have a $30 paid subscription, can we get telphone support?
Riyad KallaMemberRenuTBI,
I have asked Scott or Michael to handle this thread as I am not farmiliar with WebSphere.
RenuTBIMemberThanks Riyad. In any case, do you provide telephone support or is it just online support?
Riyad KallaMemberdo you provide telephone support or is it just online support?
Sorry I missed that in the previous post, we currently only offer online support but I believe this is flexible depending on the number of licenses that the business has. You can email support@genuitec.com for futher details.
Scott AndersonParticipantRenuTBI,
I checked my path, classpath and removed all plugins I installed additionally. Now it works fine. Looks like a configuration problem
of my eclipse installation.It seems that rparr123’s problem was environmental so we don’t know what he changed to correct the issue. From the looks of it, I’d suggest running Eclipse with a different JDK, perhaps 1.4.1 or IBM’s JDK, to see if the issue is an incompatibility there.
-
AuthorPosts