aspose file tools*
The moose likes Websphere and the fly likes WAS4.0 - Servlet not providing a service! Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS4.0 - Servlet not providing a service!" Watch "WAS4.0 - Servlet not providing a service!" New topic
Author

WAS4.0 - Servlet not providing a service!

Steve Granton
Ranch Hand

Joined: Jan 13, 2002
Posts: 200
Hi,
Although I've been working with WAS3.5 for sometime I'm new to WAS4.0 - count hours rather than days.
My problem is described below:
We've just migrated an application from Weblogic 6.1 to WAS4.0. We managed to get the EAR file deployed onto the default server - having removed all other applications and servers. This application has a context root of '/' and we can access the images and static files using: //localhost:9080/...
The application uses the Front Controller architecture with a single servlet (the Controller servlet) in the application. This servlet is mapped to the servlet mapping 'controller'
When we start the server, application and web module we see that the init() method of the servlet is executed. However when we call the servlet using //localhost:9080/controller?EventName=Test there is no response from the servlet. We get a 404 error! The servlet doesn't appear to be servicing requests. The are no errors reported and nothing is written to the log files.
Is there any way we can 'ping' the servlet as in WAS3.5 or any way we can see that the servlet is deployed in the application?
Presumably we can use the Resource Analyser to check that the request is being serviced?
Thanks in advance for the help,
Cheers,
Steve
Steve Granton
Ranch Hand

Joined: Jan 13, 2002
Posts: 200
Hi,
It turns out that we hadn't mapped the servlet using the servlet-mapping tag - though since the servlets are not listed individually in the Admin Console (as they are under the web app in WAS 3.5) then we had to examine the deployment descriptor. We also used Resource Analyzer to see that the servlet wasn't being hit at all.
I hope this helps someone else.
Cheers,
Steve
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WAS4.0 - Servlet not providing a service!