logo       

Re: Re: Enhydra: Running under Apache 2.0: msg#00007

java.enhydra.general

Subject: Re: Re: Enhydra: Running under Apache 2.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi!

I will try to be quick. :)

Steve Riley wrote:

Hi, I'm trying to get this working.

I have apache configured as prescribed in the Documentation, I run
multiserver with Enhydra 5.1, I get the following output for the app:

2003-09-04 10:46:25,936: INFO: Enhydra Java Application Server
2003-09-04 10:46:25,937: INFO: Enhydra 5.1
2003-09-04 10:46:25,937: INFO: Together the Workgroup 2003
2003-09-04 10:46:25,937: INFO: Starting Enhydra Multiserver
2003-09-04 10:46:27,537: INFO: Starting servlet/application Command
2003-09-04 10:46:27,537: INFO: Application Command has URL prefix
/command

Everything ok untl next line

2003-09-04 10:46:27,537: INFO: Command is listening (ENHYDRADIRECTOR) on
port: 9005

You have configured your application as using enhydra director connections.
To work properly the Apache will need to by using the Enhydra Director module.
If you try to use the Apache as proxy to access the application that is expecting to talk with the director module you get an error as above.


When I try to connect via the browser, I get: Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /command

Reason: Error reading from remote server

On the apache server error log, I get:
[Thu Sep 04 11:44:36 2003] [error] [client 192.168.1.151] proxy: error
reading status line from remote server myserver
[Thu Sep 04 11:44:36 2003] [error] [client 192.168.1.151] proxy: Error
reading from remote server returned by /command

Am I missing something?

Yup!

The ideia is:

Enhydra App with connection type HTTP -> use Apache Proxy
Enhydra App with connection type Director -> use Apache with module Director

I hope this will help.

Regards.
João Paulo Ribeiro

PS: if you want to change the connection type just search for this line in the multiserver.conf
Connection.<connection_name>.Type = director
and change it to
Connection.<connection_name>.Type = http
Be carefully and only change the Connection of your application if you have more than one application configured in your multiserver.conf


On Thu, 2003-08-28 at 15:07, Alfred Madl wrote:

Right ! This is NO solution with Director. Just a solution to make Enhydra work behind Apache 2 currently.

We are still evaluating the future direction for Director development. For Enhydra 6.0 we are planning the separation of Servlet Server(s) and Enhydra. A prototype (with all demo applications and without changes in the application code) is already running under Tomcat 4, Jetty and Websphere...

Since Tomcat seems to have its own powerfull web connector (AJP) we are not sure if it is worth the extra effort to port Director to talk to Tomcat. Based on this strategic decision we will support Apache 2 for Director in the future or simply switch to use native Servlet Server connectors in the future.

Feedback is very welcome !

Greetings.

Alfred


From: Srinivas Yermal <syermal@xxxxxxxxxxx>
Reply-To: enhydra@xxxxxxxxxxx
To: enhydra@xxxxxxxxxxx
Subject: Re: Enhydra: Running under Apache 2.0
Date: Wed, 27 Aug 2003 17:20:13 -0700

Thanks for the tip. Found it as Enhydra/doc/enhydra/apache2_conf.html
But what it talks about is apache running as a proxy for multiserver. That implies that the multiserver now should open and serve through multiserver connections and not director connection and the director is completely bypassed. Am I right?

Thanks,
Srini.

Alfred Madl wrote:


Hi !

Director 5.1 still needs APache 1.3.x

Yes, Enhydra can be run with Apache 2 proxy configuration. Enhydra 5.1 Beta 8 contains the documentation about that...

Greetings.

Alfred



From: Srinivas Yermal <syermal@xxxxxxxxxxx>
Reply-To: enhydra@xxxxxxxxxxx
To: enhydra@xxxxxxxxxxx
Subject: Re: Enhydra: Director 5.1 RC 1 released
Date: Sun, 24 Aug 2003 19:08:53 -0700

Great! Does this have the Apache 2.0 support? Please let us know since we have a production website which needs to be updated to Apache 2.0.

Somebody on the list was mentioning about running the director with Apache's proxy support. Was wondering how that can be done. Please help.
Thanks,
Srini.

Madl Alfred wrote:


Director 5.1 RC 1 is released. Have a look at
http://director.enhydra.org !

Greetings.

Alfred Madl

_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra




_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra

_________________________________________________________________
Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail

_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra


_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

_______________________________________________
Enhydra mailing list
Enhydra@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/enhydra


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/V3k1bwM7R+C+9B0RAg8oAJ4mUaWg1SwUNQjYvccfRVJzAabWWgCgmI+i
DsrCQMXWQcLvpPaGWmC2WsI=
=CeGt
-----END PGP SIGNATURE-----


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise