Re: Re: Enhydra: Running under Apache 2.0

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

It seems an URL path problem.
Look at your appconf.
What value have you for: Application.DefaultUrl ?
And what value have you in you multiserver.conf for: 
Channel.<connection_name>.channel.Url ?
Good luck!


Regards,
João Paulo Ribeiro


Steve Riley wrote:

>I appreciate the help.  Fixing it as you say seems to get rid of the
>proxy errors, but now when I browse I just get a 404 page not found
>error. I don't see any other errors in the multiserver output or the
>apache errorlog. This must be something else simple I'm forgetting.
>
>Multiserver now says:
>
>2003-09-04 13:24:13,815: INFO: Enhydra Java Application Server
>2003-09-04 13:24:13,815: INFO: Enhydra 5.1
>2003-09-04 13:24:13,815: INFO: Together the Workgroup 2003
>2003-09-04 13:24:13,816: INFO: Starting Enhydra Multiserver
>2003-09-04 13:24:15,617: INFO: Starting servlet/application Command
>2003-09-04 13:24:15,617: INFO: Application Command has URL prefix
>/command
>2003-09-04 13:24:15,617: INFO: Command is listening (HTTP) on port: 9005
>
>
>On Thu, 2003-09-04 at 12:41, João Ribeiro wrote:
>  
>
>>-----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
>>    
>>
>
>  
>

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

iD8DBQE/WGEhbwM7R+C+9B0RAiISAJ4iXZ4z8WQoE07aXPTL2h0TnSa3SACcCSZh
AsEh1zzOxoX9IHuJtkBiEhw=
=D9LL
-----END PGP SIGNATURE-----