Sameer Kekade wrote:
Hey All,
I tried to configure apache as stated in the documentation,
To configure the Apache web server for ColdFusion MX on UNIX:
1 Enter the following command on a single line:
java_root /bin/java -jar cf_root /runtime/lib/wsconfig.jar -ws Apache
-dir <apache config directory >-map .cfm,.cfc,.cfml -coldfusion -v
/ /
/Note:/You must enter the previous command as a single (long)line.
The following is a sample command:
/opt/coldfusionmx/jre/bin/java -jar
/opt/coldfusionmx/runtime/lib/wsconfig.jar -ws Apache
-dir /etc/httpd/conf -map .cfm,.cfc,.cfml,.jsp,.jws -coldfusion -v
but i get this following error,
bluesky:/export/home/cfuser/jrun4/lib>java -jar wsconfig.jar -ws Apache
-bin /usr/local/apache2/bin/httpd -script
/usr/local/apache2/bin/apachectl -dir /usr/local/apache2/conf -map
.cfm,.cfc,.jsp,.cfml -coldfusion -v
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/naming/Referenceable
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass0(Compiled Code)
at java.lang.ClassLoader.defineClass(Compiled Code)
ETC.
Can someone please help!!
For more recent versions of Apache you will need to rebuild the Jrun
connector from source. Attached is the method shown in the support
documentation for the CF MX updater. Each time you update MX you will
need to redo this. I was getting similar errors installing CF MX on
Apache 2.x on Red Hat Linux 8.0 which this cured.
==================================================================
JRun Apache connector build for ColdFusion MX Updater 3 2/4/2003
==================================================================
=============================================================================
Building from source is required for Apache 1.3.x in the following conditions
=============================================================================
1) The Apache 1.3.x version is a mod_ssl or derivative or Apache StrongHold.
2) EAPI warning messages appear on startup
[warn] Loaded DSO /opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so uses plain
Apache 1.3 API, this module might crash under EAPI! (please recompile it with -DEAPI)
=============================================================================
Instructions for building a ColdFusion MX Apache connector from source files
=============================================================================
Terms and Definitions
=====================
Environment variables:
CFMX_CONNECTOR = the ColdFusion web server connector directory.
e.g. /opt/coldfusionmx/runtime/lib/wsconfig/1
or /opt/coldfusionmx/runtime/lib/wsconfig/2 if a second web server is
configured
APACHE_BIN = the Apache binaries directory.
e.g. /usr/sbin or /opt/apache/bin
NOTE: It is assumed that an Apache connector is already configured on the system
which will be replaced by the newly built connector.
1.) Stop Apache (it is not necessary to stop ColdFusion MX)
2.) Place the ApacheModule.zip file in the CFMX_CONNECTOR directory and use the unzip
utility to extract the source files here.
unzip -a ApacheModule.zip
chmod 777 *
3.) Rename or delete the existing mod_jrun.so (Apache 1.3.x) or mod_jrun20.so (Apache
2.0.x) file.
4.) Use the Apache apxs utility to build the JRun connector from the source files:
Apache 1.3.x -
${APACHE_BIN}/apxs -c -Wc,-w -DJRUN_SSL mod_jrun.c \
jrun_maptable_impl.c jrun_property.c jrun_session.c \
platform.c jrun_mutex.c jrun_proxy.c jrun_ssl.c
strip mod_jrun.so
Apache 2.0.x -
${APACHE_BIN}/apxs -c -Wc,-w -n jrun20 -S LIBEXECDIR=${CFMX_CONNECTOR}
mod_jrun20.c \
jrun_maptable_impl.c jrun_property.c jrun_session.c platform.c \
jrun_mutex.c jrun_proxy.c jrun_ssl.c
${APACHE_BIN}/apxs -i -n jrun20 -S LIBEXECDIR=${CFMX_CONNECTOR} mod_jrun20.la
strip mod_jrun20.so
5.) Restart Apache and check the Apache logs/error_log file.
6.) Delete the source files from the CFMX_CONNECTOR directory when you have finished
building the connector.
rm *.h *.c *.o *.lo *.slo *.la
This procedure will need to be repeated after each ColdFusion MX Updater is installed
since
ColdFusion MX updaters usually install updated connectors from the wsconfig.jar file
for all
installed web server connectors overwriting the user-compiled mod_jrun.so or
mod_jrun20.so. The Apache EAPI versions are currently not built automatically in
wsconfig.jar.
==================================
Explanation of switches & options
=================================
unzip options:
-a convert source (text) files line endings as appropriate for platform
apxs options:
-c compile an Apache module
-i install an Apache module
-Wc,-w compiler switch to supress warnings
-DJRUN_SSL define the JRUN_SSL symbol
(note that this refers to SSL between the connector
and JRun, not to Web Server SSL on port 443)
-n jrun20 module name is jrun20
-S LIBEXECDIR=${CFMX_CONNECTOR} create mod_jrun20.so in the current directory
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Versions tested
===============
OK - Linux Redhat 7.2 Apache 2.0.43
OK - Linux Redhat 7.2 Apache 1.3.27
OK - Linux Redhat 7.2 Apache 1.3.27 with mod_ssl ( EAPI build )
OK - Solaris 8 Apache 1.3.27
Note: be sure to set the PATH environment variable as required by your C compiler
FAILED - Solaris 8 Apache 2.0.43 - did not build (mod_jrun20.la incorrect values -
apxs error?). A working mod_jrun20.so can still be built by using the following
command in place of the 'apxs -i' command:
ld -G -o mod_jrun20.so mod_jrun20.o \
jrun_maptable_impl.o jrun_property.o \
jrun_session.o jrun_mutex.o jrun_proxy.o \
platform.o jrun_ssl.o
---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
