Message-Id: <199607021405.KAA29847@squaw-valley.openmarket.com> To: firstname.lastname@example.org (Marco Baggi) Subject: Java & FastCGI & Apache server In-Reply-To: Your message of "Tue, 02 Jul 1996 10:31:37 +0200." <9607020831.AA17445@txt.it> Date: Tue, 02 Jul 1996 10:05:56 -0400 From: Steve Harris <email@example.com> The answer to your 3 questions: 1. portNum1 and portNum2 should be the same. Cgi-fcgi and TinyFCGI will be communicating over the socket created on that port. 2. These should NOT be the same as your server port. 3. Sequence: Invoke java on TinyFCGI with the -DFCGI_PORT option and then point your browser at the CGI script that runs cgi-fcgi. 4. TinyFCGI should run when invoked "java -DFCGI_PORT=nnnn TinyFCGI". How do you know that the socket has not been created? If the FastCGI interface did not recognize FCGI_PORT, (i.e., if you put in "fcgi_port", or mistyped), the interface would run TinyFCGI as plain CGI and TinyFCGI would write its HTML to stdout, which in this case would still be your command line. If it just dies, it may be some problem with the port number you chose (it might be in use). In any event, I need more info on just where it dies. Since you have the source, you could put some Print statements in FCGIInterface. You should write to a file, since if the socket creation did work, System.out may have been redirected to it.