Sun Java System Web Server 7.0 Update 1 Administrator's Guide

Configuring FastCGI Plug-in on Web Server

FastCGI plug-in is bundled with Web Server 7.0. The plug-in is installed at the following location:

32 bit FastCGI plug-in binaries are installed under <install_dir>/plugins/fastcgi directory.

64 bit Solaris SPARC FastCGI plug-in binaries are installed under <install_dir>/lib/plugins/fastcgi/64 directory.

The following FastCGI binaries are installed : (for Solaris/Linux)

fastcgi.dll(for Windows)

Fastcgistub.exe(for Windows) HP-UX)

Fastcgistub (executable)

The FastCGI plug-in is configured using the Web Server configuration files located under <instance-dir>/config directory. To configure the FastCGI plug-in, perform the following steps:

Modify the magnus.conf

Use “load-modules” Init function to load the FastCGI plug-in shared library.

Init fn=flex-init access="access" format.access="%Ses->client.ip%
- %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\"
%Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%"

Init fn="load-modules" shlib="libJava" shlib_flags="(global|now)"

Init fn="load-modules" shlib="" shlib_flags="(global|now)"

Modify the MIME Type (Optional)

Edit the mime.types file to specify the MIME mapping. Modifying the MIME type mapping is an optional step.

For Example,

#--Sun Microsystems Inc. MIME Information

# Do not delete the above line. It is used to identify the file type.


# Copyright 2006 Sun Microsystems, Inc. All rights reserved.

# Use is subject to license terms.


type=application/octet-stream exts=bin

type=application/astound exts=asd,asn



type=magnus-internal/fastcgi exts=php



Modify the obj.conf

Edit obj.conf file to configure FastCGI specific requests using the plug-in SAFs described in the earlier sections.

An example of modified obj.conf file is shown below:


# Copyright 2006 Sun Microsystems, Inc. All rights reserved.

# Use is subject to license terms.


# You can edit this file, but comments and formatting changes

# might be lost when you use the administration GUI or CLI.

<object name = "default">

		AuthTrans fn="match-browser" browser="*MSIE*" 
		NameTrans fn="ntrans-Java EE" name="Java EE"
		NameTrans fn="pfx2dir" from="/mc-icons" 
						dir="/ws7/lib/icons" name="es-internal"
		NameTrans fn="assign-name" from="/fcgi/*" name="fcgi.config"


<Object name="fcgi.config">

		AuthTrans fn="auth-fastcgi" app-path="/fastcgi/apps/c/simpleAuth" 
		Service fn="responder-fastcgi" 


Note that FastCGI SAFs can be invoked in different ways by defining different objects for different URL patterns or mapping the SAFs to different MIME types.

For more information on obj.conf configuration and syntax, refer to the Administration Configuration File Reference Guide.

Troubleshooting FastCGI Plug-in

Fastcgistub is a process manager that manages the lifecycle of the FastCGI application processes. Fastcgistub logs its messages into Fastcgistub.log file under Web Server's temporary directory. In case of any errors, checking this file can help in debugging the problem.

Problem: FastCGI requests are not getting served

Possible cause and solutions are as follows:

  1. Check if the FastCGI plug-in is loaded. If the following msg appears during Web Server startup, then the plug-in is loaded successfully. Else, check the path to the plug-in library within magnus.conf: FCGI1000: Sun Java System Web Server 7.0 Update 1 FastCGI NSAPI Plugin < build info>

  2. Check if the request mapping is correctly specified within obj.conf. For more information on the obj.conf file, see the Sun Java System Web Server Administrator's Configuration Reference File.

  3. Check the errors log for any possible error messages.

  4. Check the permissions of the stub binary and FastCGI applications. If enough permissions are not given, the plug-in fails to start the stub or the application.

  5. Check the Fastcgistub.log file for any possible errors on the stub side.

  6. If possible, run the FastCGI application in standalone mode and check if it runs without any issues.

If any library dependency errors are thrown, specify the LD_LIBRARY_PATH in the obj.conf as app-env parameter with LD_LIBRARY_PATH=<dependency library paths> value .

Problem: FastCGI application is not getting started.

Possible cause and solutions are as follows:

Check Fastcgistub.log file for the following log messages:

<pid> process startup failure, trying to restart
Even after trying <n> time(s), <application path> process failed to more retries

One of the reasons for startup failures can be due to the failure to load the dependent library. This issue can be resolved by specifying the appropriate library path(s) as a app-env parameter value to the FastCGI application configured in the obj.conf file. For example:

Service fn="responder_fastcgi" app-path="/fastcgi/c/tux-app" bind-path="localhost:2112" 

Developing FastCGI Applications

FastCGI applications can be developed using Perl, PHP, C and Java. The following sections briefly describe the procedure to develop the application using some of the popular programming languages.

ProcedureExecuting a FastCGI Application

  1. Stop the Web Server.

  2. Restart the Web Server.

  3. Access the application that has "fcgi" as the application root.

    For Example: http://localhost/fcgi/ListDir.php

Structure of a FastCGI Application

A typical FastCGI application has the following code structure:

Initialization code

Start of response loop
		body of response loop
End of response loop

The initialization code is run only once at the time of the application initialization. Initialization code usually performs time-consuming operations such as opening databases or calculating values for tables or bitmaps. The main task of converting a CGI program into a FastCGI program is to separate the initialization code from the code that needs to run for each request.

The response loop runs continuously, waiting for client requests to arrive. The loop starts with a call to FCGI_Accept, a routine in the FastCGI library. The FCGI_Accept routine blocks program execution until a client requests the FastCGI application. When a client request comes in, FCGI_Accept unblocks, runs one iteration of the response loop body, and then blocks again waiting for another client request. The loop terminates only when a System Administrator or the Web Server kills the FastCGI application.

Using Perl

Download and install the latest FCGI module from CPAN. For ActivePerl, the modules can be downloaded from

For more information on writing FastCGI applications using Perl, see

Using PHP

Beginning with PHP 4.3.0, FastCGI became a supported configuration for the PHP engine. To compile the PHP 4.3.x or greater engine with support for FastCGI, include the configure switch --enable-fastcgi as part of the build process, for example:

./configure <other-options> --enable-fastcgi

After compilation, the php binary will be FastCGI enabled.

When using PHP versions 5.1.2 or earlier (including PHP 4.x) the FastCGI plug-in should be configured with bind-path in host:port format. For example, bind-path = “localhost:3333”.

For PHP versions 5.1.3 and later, the bind-path is optional. If specified, it should not be in “host:port” format. It can be a string. For example, bind-path = “myphpbindpath”.

Using C/Java

FastCGI development kit provides APIs to write FastCGI C/Java applications. You can download the kit from

To build the downloaded FastCGI development kit, perform the following steps:

  1. Unpack the tar file. This action creates a new directory called fcgi-devel-kit

  2. Execute this sequence of commands in the fcgi-devel-kit directory:

    1. ./configure

    2. make

For more information on writing FastCGI applications using C, see

For more information on writing FastCGI applications using Java, see