• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 8342
  • Last Modified:

failed to initialize

Using WAS 4, I generated a .ear file which successfully installed.  When i issued the startserver command all the sample apps came up fine, but my .ear gave a 'failed to initialize' message.  Not much else.  What are some of the possible causes or where do i look to find out the reason for failure.
0
xoxomos
Asked:
xoxomos
  • 9
  • 5
1 Solution
 
jerelwCommented:
What does your 'details' alert say?
0
 
jerelwCommented:
The sample apps all have been pre-configured.

How far into your set up are you?

1. create your virtual host (admin console)
2. create your application server (admin console)
3. create your web module (app assembly toolkit)
4. create your ejb module (app assembly toolkit)
5. create your application (app assembly toolkit)
6. install your application (admin console)
7. regenerate your plugins (admin console)
8. start your application server (admin console)
9. start your enterprise application (admin console)

0
 
xoxomosAuthor Commented:
I installed the application (6) from the command line SEAppinstall - install.  That went ok (successful).
What does 'regenerate your plugins mean?
Application server starts ok and all the sample apps run.  I'll be going home in a bit an try taking another look at that install.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
jerelwCommented:
In the admin console, you should be able to see your topology.

Aside from the actual WebSphere and DB2 applications, I don't install anything from the command line.

How does your application know which virtual host and which application server to bind to?

If you didn't specify any of the above, I think you application is bound to the default_host.

0
 
xoxomosAuthor Commented:
Yeah, it does go to default_host.  This tutorial actually uses the new Application Assembly Tool to generate the WAR and EAR.  In the AAT there is a bindings tab.  Then from the command line you just invoke  SEAppInstall with the .ear file as one of the paramenters
0
 
jerelwCommented:
It seems like something is missing somewhere.

Does your code need any special jars or zips?

Are they in the classpath of your application server?

What files are in you JVM settings on the Application Server you're bound to?
0
 
xoxomosAuthor Commented:
There probably is.  When i was stopped at this point once before, i imported a lot of stuff from VAJ4 WTE , some Sun servlet stuff and who know what else.  That seemed to have done the trick, but i don't know what it was.
0
 
xoxomosAuthor Commented:
Started this thing from scratch, used the admin console to install instead of command line.  Problem look a little different , but similar.  Will try the regenerate plug-ins now.


02.04.21 09:10:51:114 PDT] 55fcf165 ServletInstan X SRVE0100E: Did not realize  init() exception thrown by servlet DatabaseConnLoader: javax.servlet.ServletException
      at com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.java:817)
      at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleServlet.java:137)
      at com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycleServlet.java:243)
      at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleServlet.java:103)
      at com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java:388)
      at javax.servlet.GenericServlet.init(GenericServlet.java:258)
      at com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java:84)
      at com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:226)
      at com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:357)
      at com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:1001)
      at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:133)
      at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:234)
      at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:139)
      at com.ibm.servlet.engine.ServletEngine.addWebApplication(ServletEngine.java:633)
      at com.ibm.ws.runtime.WebContainer.install(WebContainer.java:36)
      at com.ibm.ws.runtime.Server.startModule(Server.java:615)
      at com.ibm.ws.runtime.StandardServer.initializeModules(StandardServer.java:333)
      at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:349)
      at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
      at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)

[02.04.21 09:10:51:435 PDT] 55fcf165 WebGroup      X Servlet Error-[DatabaseConnLoader]: Failed to load servlet: java.lang.NullPointerException
      at IBMConnectionBroker.init(IBMConnectionBroker.java:108)
      at IBMConnectionBroker.<init>(IBMConnectionBroker.java:68)
      at IBMConnectionBroker.instance(IBMConnectionBroker.java:75)
      at DatabaseConnLoader.init(DatabaseConnLoader.java:20)
      at com.ibm.servlet.engine.webapp.StrictServletInstance.doInit(ServletManager.java:802)
      at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._init(StrictLifecycleServlet.java:137)
      at com.ibm.servlet.engine.webapp.PreInitializedServletState.init(StrictLifecycleServlet.java:243)
      at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.init(StrictLifecycleServlet.java:103)
      at com.ibm.servlet.engine.webapp.ServletInstance.init(ServletManager.java:388)
      at javax.servlet.GenericServlet.init(GenericServlet.java:258)
      at com.ibm.servlet.engine.webapp.ServletManager.addServlet(ServletManager.java:84)
      at com.ibm.servlet.engine.webapp.WebAppServletManager.loadServlet(WebAppServletManager.java:226)
      at com.ibm.servlet.engine.webapp.WebAppServletManager.loadAutoLoadServlets(WebAppServletManager.java:357)
      at com.ibm.servlet.engine.webapp.WebApp.loadServletManager(WebApp.java:1001)
      at com.ibm.servlet.engine.webapp.WebApp.init(WebApp.java:133)
      at com.ibm.servlet.engine.srt.WebGroup.loadWebApp(WebGroup.java:234)
      at com.ibm.servlet.engine.srt.WebGroup.init(WebGroup.java:139)
      at com.ibm.servlet.engine.ServletEngine.addWebApplication(ServletEngine.java:633)
      at com.ibm.ws.runtime.WebContainer.install(WebContainer.java:36)
      at com.ibm.ws.runtime.Server.startModule(Server.java:615)
      at com.ibm.ws.runtime.StandardServer.initializeModules(StandardServer.java:333)
      at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:349)
      at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
      at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
0
 
xoxomosAuthor Commented:
Put the nullpointerexception class in ../../WEB-INF/classes
plus in classpath.  Still get the same message.
0
 
xoxomosAuthor Commented:
Yes, these are classes i can't find anywhere.

at com.ibm.ws.runtime.Server.startModule(Server.java:615)
     at com.ibm.ws.runtime.StandardServer.initializeModules(StandardServer.java:333)
     at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:349)
     at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
     at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)

They are not in WTE and doing a search for StandardServer over the entire disk comes up with nothing.  What is happening here, are these classes that are required that i need to find somewhere or what?.  If so where do i look?
Those files are not in classpath or anywhere else that i can detect.
I'm just using default_server, but as far as i can tell those classes are not there.  Still in WTE there is no problem.  The servlets were compiled in VAJ4, They run in WTE except the javascripts don't show up.
0
 
jerelwCommented:
Don't import servlet.jar or server.jar.

WebSphere 4.0 already has these files.
0
 
xoxomosAuthor Commented:
I tried just changing the classpath to point to WTE.
D:\WebSphere\webreg\classes;
D:\WebSphere\AppServer\properties;
d:\Program Files\ibm\VisualAge for Java\ide\project_resources\IBM WebSphere Test Environment;
d:\Program Files\ibm\VisualAge for Java\ide\project_resources\Servlet API Classes;
d:\Program Files\ibm\VisualAge for Java\ide\project_resources\Java Class libraries
This eliminated some of the problems of classes not being found.  Now however it is not finding classes from the servlets that i compiled which are in d:\WebSphere\webreg\classes.  If i put one of the classes in the properties directory, it will find that class, but none of the classes that servlet calls.  It comes up with error 500.  Even though i put d:\WebSphere\classes in the classpath in AAT, the log  file does not show it, nor does it show in the error 500.
Error 500
An error has occured while processing request: http://localhost:9080/servlet/CSUHWelcome
Message: Servlet [CSUHWelcome]: CSUHWelcome was found, but is missing another required class. This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. Check your classpath to ensure that all classes required by the servlet are present. This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath Application classpath=[D:\WebSphere\AppServer\installedApps\sampleApp.ear\default_app.war\WEB-INF\classes;D:\WebSphere\AppServer\installedApps\sampleApp.ear\default_app.war;D:\WebSphere\AppServer\installedApps\sampleApp.ear\examples.war\WEB-INF\classes;D:\WebSphere\AppServer\installedApps\sampleApp.ear\examples.war;D:\WebSphere\AppServer\installedApps\sampleApp.ear\Increment.jar;d:\WebSphere\AppServer\lib\app;D:\WebSphere\AppServer\java\lib;D:\WebSphere\AppServer\java\lib\tools.jar;D:\WebSphere\AppServer\classes;D:\WebSphere\AppServer\lib;D:\WebSphere\AppServer\lib\EJBCommandTarget.jar;D:\WebSphere\AppServer\lib\SoapEnabler.jar;D:\WebSphere\AppServer\lib\WASPostUpgrade.jar;D:\WebSphere\AppServer\lib\WASPreUpgrade.jar;D:\WebSphere\AppServer\lib\aat.jar;D:\WebSphere\AppServer\lib\ace.jar;D:\WebSphere\AppServer\lib\als.jar;D:\WebSphere\AppServer\lib\appclient.jar;D:\WebSphere\AppServer\lib\bootstrap.jar;D:\WebSphere\AppServer\lib\bsf.jar;D:\WebSphere\AppServer\lib\certpath.jar;D:\WebSphere\AppServer\lib\chart.jar;D:\WebSphere\AppServer\lib\checkloadclass.jar;D:\WebSphere\AppServer\lib\cm.jar;D:\WebSphere\AppServer\lib\commands.jar;D:\WebSphere\AppServer\lib\common.jar;D:\WebSphere\AppServer\lib\csicpi.jar;D:\WebSphere\AppServer\lib\databeans.jar;D:\WebSphere\AppServer\lib\deployTool.jar;D:\WebSphere\AppServer\lib\derdbpw.jar;D:\WebSphere\AppServer\lib\dertrjrt.jar;D:\WebSphere\AppServer\lib\drs.jar;D:\WebSphere\AppServer\lib\dynacache.jar;D:\WebSphere\AppServer\lib\eex.jar;D:\WebSphere\AppServer\lib\ejbcontainer.jar;D:\WebSphere\AppServer\lib\firststeps.jar;D:\WebSphere\AppServer\lib\hplwps.jar;D:\WebSphere\AppServer\lib\http.jar;D:\WebSphere\AppServer\lib\httpsession.jar;D:\WebSphere\AppServer\lib\idb.jar;D:\WebSphere\AppServer\lib\idbexmpl.jar;D:\WebSphere\AppServer\lib\ivblogbr.jar;D:\WebSphere\AppServer\lib\ivjbase.jar;D:\WebSphere\AppServer\lib\ivjejb35.jar;D:\WebSphere\AppServer\lib\iwsorb.jar;D:\WebSphere\AppServer\lib\iwstools.jar;D:\WebSphere\AppServer\lib\j2ee-validation.jar;D:\WebSphere\AppServer\lib\j2ee.jar;D:\WebSphere\AppServer\lib\j2eexml-xerces.jar;D:\WebSphere\AppServer\lib\js.jar;D:\WebSphere\AppServer\lib\jsp.jar;D:\WebSphere\AppServer\lib\jts.jar;D:\WebSphere\AppServer\lib\logbrjface.jar;D:\WebSphere\AppServer\lib\lotusxsl.jar;D:\WebSphere\AppServer\lib\ltext.jar;D:\WebSphere\AppServer\lib\mof.jar;D:\WebSphere\AppServer\lib\mofj2ee.jar;D:\WebSphere\AppServer\lib\mofjava.jar;D:\WebSphere\AppServer\lib\nls.jar;D:\WebSphere\AppServer\lib\ns.jar;D:\WebSphere\AppServer\lib\nssrcm.jar;D:\WebSphere\AppServer\lib\ose.jar;D:\WebSphere\AppServer\lib\perf.jar;D:\WebSphere\AppServer\lib\ptfextuninst.jar;D:\WebSphere\AppServer\lib\ras.jar;D:\WebSphere\AppServer\lib\resources.jar;D:\WebSphere\AppServer\lib\runtime.jar;D:\WebSphere\AppServer\lib\seappinstall.jar;D:\WebSphere\AppServer\lib\security.jar;D:\WebSphere\AppServer\lib\sljc.jar;D:\WebSphere\AppServer\lib\sljcx.jar;D:\WebSphere\AppServer\lib\soap-sec.jar;D:\WebSphere\AppServer\lib\soap.jar;D:\WebSphere\AppServer\lib\uddi4j.jar;D:\WebSphere\AppServer\lib\ujc.jar;D:\WebSphere\AppServer\lib\userprofile.jar;D:\WebSphere\AppServer\lib\utils.jar;D:\WebSphere\AppServer\lib\vaprt.jar;D:\WebSphere\AppServer\lib\was_commands.jar;D:\WebSphere\AppServer\lib\webcontainer.jar;D:\WebSphere\AppServer\lib\websphere-validation.jar;D:\WebSphere\AppServer\lib\websphere.jar;D:\WebSphere\AppServer\lib\webtlsrn.jar;D:\WebSphere\AppServer\lib\wlm.jar;D:\WebSphere\AppServer\lib\workloadcontroller.jar;D:\WebSphere\AppServer\lib\ws-base-bindings.jar;D:\WebSphere\AppServer\lib\ws-base-config.jar;D:\WebSphere\AppServer\lib\ws-base-extensions.jar;D:\WebSphere\AppServer\lib\ws-base-resources.jar;D:\WebSphere\AppServer\lib\ws-soap-ext.jar;D:\WebSphere\AppServer\lib\xalan.jar;D:\WebSphere\AppServer\lib\xalanj1compat.jar;D:\WebSphere\AppServer\lib\xerces.jar;D:\WebSphere\AppServer\lib\xmi.jar;D:\WebSphere\AppServer\lib\xmiframework.jar;D:\WebSphere\AppServer\lib\xml4j.jar;D:\WebSphere\AppServer\lib\xss4j-dsig.jar;D:\WebSphere\AppServer\lib\ext;D:\WebSphere\AppServer\web\help;D:\WebSphere\AppServer\bin\lib\ifxjdbcx.jar;D:\WebSphere\AppServer\bin\lib\ifxjdbc.jar;D:\WebSphere\AppServer\bin\(specify path for DB2JAVA.ZIP);D:\WebSphere\AppServer\lib\idb.jar]
StackTrace: javax.servlet.ServletException: Servlet [CSUHWelcome]: CSUHWelcome was found, but is missing another required class. This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. Check your classpath to ensure that all classes required by the servlet are present. This problem can be debugged by recompiling the servlet using only the classes in the application's runtime classpath Application classpath=[D:\WebSphere\AppServer\installedApps\sampleApp.ear\default_app.war\WEB-INF\classes;D:\WebSphere\AppServer\installedApps\sampleApp.ear\default_app.war;D:\WebSphere\AppServer\installedApps\sampleApp.ear\examples.war\WEB-INF\classes;D:\WebSphere\AppServer\installedApps\sampleApp.ear\examples.war;D:\WebSphere\AppServer\installedApps\sampleApp.ear\Increment.jar;d:\WebSphere\AppServer\lib\app;D:\WebSphere\AppServer\java\lib;D:\WebSphere\AppServer\java\lib\tools.jar;D:\WebSphere\AppServer\classes;D:\WebSphere\AppServer\lib;D:\WebSphere\AppServer\lib\EJBCommandTarget.jar;D:\WebSphere\AppServer\lib\SoapEnabler.jar;D:\WebSphere\AppServer\lib\WASPostUpgrade.jar;D:\WebSphere\AppServer\lib\WASPreUpgrade.jar;D:\WebSphere\AppServer\lib\aat.jar;D:\WebSphere\AppServer\lib\ace.jar;D:\WebSphere\AppServer\lib\als.jar;D:\WebSphere\AppServer\lib\appclient.jar;D:\WebSphere\AppServer\lib\bootstrap.jar;D:\WebSphere\AppServer\lib\bsf.jar;D:\WebSphere\AppServer\lib\certpath.jar;D:\WebSphere\AppServer\lib\chart.jar;D:\WebSphere\AppServer\lib\checkloadclass.jar;D:\WebSphere\AppServer\lib\cm.jar;D:\WebSphere\AppServer\lib\commands.jar;D:\WebSphere\AppServer\lib\common.jar;D:\WebSphere\AppServer\lib\csicpi.jar;D:\WebSphere\AppServer\lib\databeans.jar;D:\WebSphere\AppServer\lib\deployTool.jar;D:\WebSphere\AppServer\lib\derdbpw.jar;D:\WebSphere\AppServer\lib\dertrjrt.jar;D:\WebSphere\AppServer\lib\drs.jar;D:\WebSphere\AppServer\lib\dynacache.jar;D:\WebSphere\AppServer\lib\eex.jar;D:\WebSphere\AppServer\lib\ejbcontainer.jar;D:\WebSphere\AppServer\lib\firststeps.jar;D:\WebSphere\AppServer\lib\hplwps.jar;D:\WebSphere\AppServer\lib\http.jar;D:\WebSphere\AppServer\lib\httpsession.jar;D:\WebSphere\AppServer\lib\idb.jar;D:\WebSphere\AppServer\lib\idbexmpl.jar;D:\WebSphere\AppServer\lib\ivblogbr.jar;D:\WebSphere\AppServer\lib\ivjbase.jar;D:\WebSphere\AppServer\lib\ivjejb35.jar;D:\WebSphere\AppServer\lib\iwsorb.jar;D:\WebSphere\AppServer\lib\iwstools.jar;D:\WebSphere\AppServer\lib\j2ee-validation.jar;D:\WebSphere\AppServer\lib\j2ee.jar;D:\WebSphere\AppServer\lib\j2eexml-xerces.jar;D:\WebSphere\AppServer\lib\js.jar;D:\WebSphere\AppServer\lib\jsp.jar;D:\WebSphere\AppServer\lib\jts.jar;D:\WebSphere\AppServer\lib\logbrjface.jar;D:\WebSphere\AppServer\lib\lotusxsl.jar;D:\WebSphere\AppServer\lib\ltext.jar;D:\WebSphere\AppServer\lib\mof.jar;D:\WebSphere\AppServer\lib\mofj2ee.jar;D:\WebSphere\AppServer\lib\mofjava.jar;D:\WebSphere\AppServer\lib\nls.jar;D:\WebSphere\AppServer\lib\ns.jar;D:\WebSphere\AppServer\lib\nssrcm.jar;D:\WebSphere\AppServer\lib\ose.jar;D:\WebSphere\AppServer\lib\perf.jar;D:\WebSphere\AppServer\lib\ptfextuninst.jar;D:\WebSphere\AppServer\lib\ras.jar;D:\WebSphere\AppServer\lib\resources.jar;D:\WebSphere\AppServer\lib\runtime.jar;D:\WebSphere\AppServer\lib\seappinstall.jar;D:\WebSphere\AppServer\lib\security.jar;D:\WebSphere\AppServer\lib\sljc.jar;D:\WebSphere\AppServer\lib\sljcx.jar;D:\WebSphere\AppServer\lib\soap-sec.jar;D:\WebSphere\AppServer\lib\soap.jar;D:\WebSphere\AppServer\lib\uddi4j.jar;D:\WebSphere\AppServer\lib\ujc.jar;D:\WebSphere\AppServer\lib\userprofile.jar;D:\WebSphere\AppServer\lib\utils.jar;D:\WebSphere\AppServer\lib\vaprt.jar;D:\WebSphere\AppServer\lib\was_commands.jar;D:\WebSphere\AppServer\lib\webcontainer.jar;D:\WebSphere\AppServer\lib\websphere-validation.jar;D:\WebSphere\AppServer\lib\websphere.jar;D:\WebSphere\AppServer\lib\webtlsrn.jar;D:\WebSphere\AppServer\lib\wlm.jar;D:\WebSphere\AppServer\lib\workloadcontroller.jar;D:\WebSphere\AppServer\lib\ws-base-bindings.jar;D:\WebSphere\AppServer\lib\ws-base-config.jar;D:\WebSphere\AppServer\lib\ws-base-extensions.jar;D:\WebSphere\AppServer\lib\ws-base-resources.jar;D:\WebSphere\AppServer\lib\ws-soap-ext.jar;D:\WebSphere\AppServer\lib\xalan.jar;D:\WebSphere\AppServer\lib\xalanj1compat.jar;D:\WebSphere\AppServer\lib\xerces.jar;D:\WebSphere\AppServer\lib\xmi.jar;D:\WebSphere\AppServer\lib\xmiframework.jar;D:\WebSphere\AppServer\lib\xml4j.jar;D:\WebSphere\AppServer\lib\xss4j-dsig.jar;D:\WebSphere\AppServer\lib\ext;D:\WebSphere\AppServer\web\help;D:\WebSphere\AppServer\bin\lib\ifxjdbcx.jar;D:\WebSphere\AppServer\bin\lib\ifxjdbc.jar;D:\WebSphere\AppServer\bin\(specify path for DB2JAVA.ZIP);D:\WebSphere\AppServer\lib\idb.jar] at com.ibm.servlet.engine.webapp.InvokerServlet.service(InvokerServlet.java:201) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:159) at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:286) at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:106) at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472) at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012) at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:499) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:278) at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:105) at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:67) at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:123) at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67) at com.ibm.servlet.engine.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106) at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:125) at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315) at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60) at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:313) at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:242) at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)
0
 
xoxomosAuthor Commented:
This isn't supposed to be like this.  I've had to add all these classes from VAJava to get past classnotfound errors.  This eliminates the classes not being found, now it's down to methods missing.  
Error Message: com.ibm.servlet.engine.webapp.ServletReference: method isJspType()Z not found
Error Code: 500
Target Servlet: null
Error Stack:
java.lang.NoSuchMethodError: com.ibm.servlet.engine.webapp.ServletReference: method isJspType()Z not found
     at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:359)

I had to add the com.ibm.servlet.engine.webapp to eliminate classnotfound errors.  Now it finds the class (ServletReference), but not one of the methods.  Looking at the methods in that class the isJspType() method truly does not appear.  Where does this error come from.  It must have been somewhere at the time the servlets were compiles, but where.  Looking at IBM site i find nothing about ServletReference but it's in one of there packages.

     
0
 
xoxomosAuthor Commented:
Wrote to IBM.  Basically they say you have to use WSStudio4 rather than VAge.

Visual Age Java 4.0 does not fully support WebSphere Application Server 4.0. VAJ 4.0 can be used to write, compile and test your applications for the Application Server.
There is another tool WebSphere Studio Application Developer,  which is based on VAJ interface, which fully compatible with WebSphere. If you are interested in the free download please go the following link:

------------------------Customer  Tue May 14 17:55:25 MDT 2002
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 9
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now