Problem:

The FastTrack server dumps core and fails to start when server side java 
is enabled with a "File not found." or similar message.

This is a result of the way that the server executes and the way
that BSD/OS does dynamic linking. The executable file (of the main
program) must be available in the path so that the symbol table can be
read when dymaically linked libraries are loaded.  The Fasttrack server
changes it's working directory to the config directory for the server, and
since the server executable is not in that directory (and not usually in
the path) the binary can not be found to read the symbol table. 

Solution:

Create a symbolic link in the /var/ns-home/<httpd-server-dir>/config which
points to the executable file in the bin directory.  An example of this
would be:

	cd /var/ns-home/httpd-osprey/config
	ln -s  ../../bin/httpd/ns-httpd .


Future Releases:

This is corrected in future releases by having the install process create
the proper sybolic links.