MSG 500: Service Handler Performed No Action
 Technote (FAQ)
 
Problem
The above message appears at the browser after you have been authenticated or when you access a Web application in the Local Redirector Plug-in.
 
 
Solution
The "Service handler performed no action" message indicates that the HTTP Server was able to match the Uniform Resource Identifier (URI) against a Service directive, but was unable to pass the request to the specified Service (Local Redirector Plug-in). Typically this means one two things:
  • The coding of the service's HFS directory, DLL file or exit point is incorrect (typographical errors can create this problem)
  • The service itself is not initialized (many things can keep a service from initializing.)

  1. Ensure that the Local Redirector Plug-in has properly initialized. Look in the SYSOUT of the HTTP Servers started task and search for the smiley face :-) in the message:

    EJS3035I IBM WebSphere Application Server for OS390 native plug-in initialization went OK :-)
  2. The SYSOUT might provide information as to what is causing the plug-in to fail (as in the above), but not always. The plug-in's native trace might provides information as well, but not always.
  3. Issue a different URL that you know successfully invokes a servlet, such as the supplied /webapp/example/index.html program. If this works, you have validated that the plug-in is up, and that the HTTP Server's service handling function performs properly.
  4. Browse the httpd.conf file, then locate the Service directive that resulted in the "500: Service Handler Performed No Action," and compare it character for character -- with the Service directive you found to work in step 2. The slightest error (for example, WebSphere incorrectly spelled with a lower-case "s") can cause this problem.

Note: the "vv" trace for this problem is very cryptic and does not point explicitly to what is wrong.

  • If the plug-in is not initialized, you must correct whatever problem is causing it to fail. The white paper Problem Determination Methodology for the Web Application Environment, WP100295, provides a chart with common reasons for this failure.
  • If the plug-in is initialized, you must correct the error, which is likely on the Service directive. This is why it is important to identify a working Service directive and then compare the working and the non-working. The default ServerInit, Service and ServerTerm directives are as follows:

ServerInit /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:
init_exit /usr/lpp/WebSphere,/etc/was.conf
ServerTerm /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:
term_exit
Service /PolicyIVP/* /usr/lpp/WebSphere/WebServerPlugIn/
bin/was400plugin.so:service_exit
Service /webapp/examples/* /usr/lpp/WebSphere/WebServerPlugIn/
bin/was400plugin.so:service_exit

Related information

White Paper Problem Determination Methodology for the Web Application Environment, WP100295 (www.ibm.com/support/techdocs)

Additional remarks

There are several different variations of the Error 500 message. Read the entire message associated with Error 500, because they do differ.

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Servlet Engine/Web Container
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1165454
IBM Group: Software Group
Modified date: Apr 7, 2004