Jared,

ta for explanation. Any other ports apart from 2901,8500,8081 CF and Jrun
might need, need this info to allow them for ipchains.

I compiled the connector settings as in previous message and CF is working.
>>If the binary doesn't
>>match the API for that build of Apache, you need to recompile the
>>connector to make it work.

restarting httpd I got:
../httpd start
Setting up Web Service: [Sat Apr 23 14:28:49 2005] [warn] Loaded DSO
/home/opt/c
oldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so uses plain Apache 1.3 API,
this m
odule might crash under EAPI! (please recompile it with -DEAPI)
chiliasp: module started, version 3.5.2.31

there may be a patch I need for mod_jrun.so

I'm using the intrnal webserver, its cool the way CF communicates via the
proxy port, and you don't need to
symlink  to cfm pages.

only issue now is rebooting, I don't wish to have to reboot twice each time
I need to reboot, once to run the connector, then reboot again after the
connector runs?

the chiliasp reference to apachectl in my connector script,
apache_connector.sh gave one error
"Exec'ing /home/chiliasp/INSTALL/apachectl restart
Usage: /home/chiliasp/INSTALL/apachectl binary=... conf=...
[start|stop|restart|status]Error running "/home/chiliasp/INSTALL/apachectl
restart": exit code was 1

Error restarting Apache server.  The web server must be restarted to
complete this operation."
I need instead something to refer to ./http start

do you know of any useful java applets free to use with the server.

thanks again

Colm





-----Original Message-----
From: Jared Rypka-Hauer - CMG, LLC [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 23, 2005 9:25 PM
To: CF-Linux
Subject: [work] Re: CF MX 6.1 connector


Colm,

You can't connect to server:2901 via a browser anyway... that port
number is for the Jrun C++ connector to use for speaking to the CF
server. There's nothing there that a browser could use or understand.

Basically the Apache connector takes any requests for CFM pages and
proxies them to the CF server and the CF server then processes the
request and responds. This process takes place via JMS (I think) and
happens at port 2901. So, the CF server and Apache need to be
configure to use the same JMS proxy port or they won't speak.

The issue with the connector is making sure that the Apache plugin API
in the currently running Apache instance matches the Apache plugin API
used to build the CF connector plugin binary. If the binary doesn't
match the API for that build of Apache, you need to recompile the
connector to make it work.

You need to compile the connector for Apache on RH 8 or 9 and SuSE
9... otherwise it will do everything BUT work. The only alernatives
are to use Apache mod_proxy, or to use the internal webserver. So I'd
really recommend you compile yourself a plugin and go for it. You'll
most likely find that if you just do it, it'll work instantudinously.

Let me know what's up...

J

On 4/23/05, Colm Brazel <[EMAIL PROTECTED]> wrote:
> Hi Jared,
>
> The connector script went ok with the changes I made, chiliasp only place
I
> found apachctl. I can't connect though to where I guess the jrun server is
> at, www.mydomain:2901 maybe because I chose standalone embedded version of
> JRUN.Havn't resolved the issue of how to point the CF MX 6.1 to the
> documentroot,Apache supplies a different one for each virtual site. I'll
try
> install with separate JRUN
>
> ../apache_connector.sh
> Found JRun server default at 127.0.0.1:2901
> Using Apache binary /usr/sbin/httpd
> Server version: Apache/1.3.20 Sun Cobalt (Unix)
> Apache 1.3.20 Sun Cobalt (Unix) is supported
> Using Apache control script /home/chiliasp/INSTALL/apachectl
> Parsing Apache configuration file /etc/httpd/conf/httpd.conf
> Exec'ing chmod 777 /home/opt/coldfusionmx/runtime/lib/wsconfig/1
> Set permission to 777 on /home/opt/coldfusionmx/runtime/lib/wsconfig/1
> Exec'ing chmod +x
/home/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so
> Set permission to execute on
> /home/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so
> Created file /home/opt/coldfusionmx/runtime/lib/wsconfig/1/mod_jrun.so
> Wrote file /etc/httpd/conf/httpd.conf
> Added JRun configuration to Apache configuration file
> /etc/httpd/conf/httpd.conf
> Created file /home/opt/coldfusionmx/runtime/lib/wsconfig/1/README.txt
> Wrote file /home/opt/coldfusionmx/runtime/lib/wsconfig/wsconfig.properties
> Exec'ing /home/chiliasp/INSTALL/apachectl restart
> Usage: /home/chiliasp/INSTALL/apachectl binary=... conf=...
> [start|stop|restart|status]Error running "/home/chiliasp/INSTALL/apachectl
> restart": exit code was 1
>
> Error restarting Apache server.  The web server must be restarted to
> complete this operation.
>
> Colm

--
---------------
-------------------------------------
Buy SQLSurveyor!
http://www.web-relevant.com/sqlsurveyor
Never make your developers open Enterprise Manager again.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Sams Teach Yourself Regular Expressions in 10 Minutes  by Ben Forta 
http://www.houseoffusion.com/banners/view.cfm?bannerid=40

Message: http://www.houseoffusion.com/lists.cfm/link=i:14:3914
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/14
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:14
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.14
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to