Bug 22290

Summary: Running Infocenter as Web Application in WebSphere 4.0 Advanced Edition doesn't work
Product: [Eclipse Project] Platform Reporter: Ilko Iliev <i.iliev>
Component: User AssistanceAssignee: Konrad Kolosowski <konradk>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: P3    
Version: 2.0   
Target Milestone: 2.0.1   
Hardware: Other   
OS: AIX Motif   
Whiteboard:

Description Ilko Iliev CLA 2002-08-09 04:51:47 EDT
Installing Infocenter on WebSphere 4.0.3 AE causes an exception by starting the
application. Running it on the Single Server AE (known as AEs) works ok.
Simulated on Windows 2000, AIX 4.3.3 and RedHat 7.3 OS. Exception stack trace:
[8/8/02 17:48:03:859 CEST] 6e550580 WebGroup      X Servlet Error-[init]: Failed
 to load servlet: java.lang.reflect.InvocationTargetException: java.lang.reflect
.InvocationTargetException: java.lang.IllegalStateException
        at org.eclipse.core.internal.plugins.PluginDescriptor.getInstallURL(Plug
inDescriptor.java:272)
        at org.eclipse.core.internal.plugins.PluginClassLoader.<init>(PluginClas
sLoader.java:44)
        at org.eclipse.core.internal.plugins.PluginDescriptor.getPluginClassLoad
er(PluginDescriptor.java:315)
        at org.eclipse.core.internal.runtime.InternalPlatform.createXMLClassLoad
er(InternalPlatform.java:256)
        at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(Inte
rnalPlatform.java:561)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBoo
tLoader.java:909)
        at org.eclipse.core.boot.BootLoader.startup(BootLoader.java:517)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.help.servlet.Eclipse.init(Eclipse.java:125)
        at org.eclipse.help.servlet.Eclipse.<init>(Eclipse.java:33)
        at org.eclipse.help.servlet.InitServlet.init(InitServlet.java:38)
...
----- Begin backtrace for targetException
java.lang.reflect.InvocationTargetException: java.lang.IllegalStateException
        at org.eclipse.core.internal.plugins.PluginDescriptor.getInstallURL(Plug
inDescriptor.java:272)
        at org.eclipse.core.internal.plugins.PluginClassLoader.<init>(PluginClas
sLoader.java:44)
        at org.eclipse.core.internal.plugins.PluginDescriptor.getPluginClassLoad
er(PluginDescriptor.java:315)
        at org.eclipse.core.internal.runtime.InternalPlatform.createXMLClassLoad
er(InternalPlatform.java:256)
        at org.eclipse.core.internal.runtime.InternalPlatform.loaderStartup(Inte
rnalPlatform.java:561)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.core.internal.boot.InternalBootLoader.startup(InternalBoo
tLoader.java:909)
        at org.eclipse.core.boot.BootLoader.startup(BootLoader.java:517)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.help.servlet.Eclipse.init(Eclipse.java:125)
        at org.eclipse.help.servlet.Eclipse.<init>(Eclipse.java:33)
        at org.eclipse.help.servlet.InitServlet.init(InitServlet.java:38)
        at javax.servlet.GenericServlet.init(GenericServlet.java:258)
        at com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletMan
ager.java:802)
Comment 1 Konrad Kolosowski CLA 2002-08-09 13:07:37 EDT
The problem is real.  The URLProvider setting do not seem to work in the WAS 4 
AE.  We are investigating it further, but it seems like a Websphere bug.

In the meantime, a solution is to add eclipseurl jar to the server VM classpath 
and not set any URLProviders.  This fixes the problem, and works in both AE and 
AEs.  I will update installation instructions, since this is simpler setup than 
setting three URL providers.
Comment 2 Konrad Kolosowski CLA 2002-08-09 13:51:44 EDT
Updated the instructions in 2.0.1 and 2.1 streams.  Will appear in the next 
builds.
Comment 3 Konrad Kolosowski CLA 2002-08-14 17:39:07 EDT
Will mark the bug as fixed, since Infocenter works according to the updated 
(fixed) instructions.
We cannot determine whether URL Providers work in WAS, but do not really need 
to use this feature of WAS.