Re: [Opaltoolkit-users] Opal 2.4 and Tomcat

[Conrad H. <co...@cg...>]

On 1/15/2014 6:14 PM, Luca Clementi wrote:
> On Wed, Jan 15, 2014 at 3:01 PM, Conrad Huang <co...@cg...> wrote:
>> Opal is now working fine for me with tomcat6 when I run it on a single host.
>> My next step is to turn it into a cluster service (Redhat Enterprise Linux 6
>> clustering).  Using the exact same Opal configuration except changing:
>>      tomcat.url=http://crick.cgl.ucsf.edu:8080
>> to
>>      tomcat.url=http://webservices.rbvi.ucsf.edu
>> in etc/opal.properties, I get the error message in the attached catalina.out
>> file.
>>
>> It appears to be a permissions problem, and I have a guess at what it might
>> be.  webservices.rbvi.ucsf.edu:80 is actually an Apache instance configured
>> to forward requests to opal2/* to tomcat.  I'm guessing that somehow the
>> opal/tomcat instance can tell whether the deployment request came from
>> itself.  In the crick:8080 case, it did, and everything worked; in the
>> webservices:80 case, it did not, and resulted in the rejection.  What I do
>> not know is where this permission check occurs (in tomcat or opal).  A
>> couple hours of research suggested that I need to have a
>>      <Valve className="org.apache.catalina.valves.RemoteAddrValve" ...
>> statement somewhere, but I really do not know tomcat or opal well enough to
>> figure it out.
>>
>
> I just push a minor fix for this specific problem. If you pull and
> re-install it should get fixed.
> I don't really like this solution since it uses an hard coded URL
> ("http://localhost:8080/opal2/services") but for the moment it should
> be ok, since that URL is also used in other opal components (at least
> they will all break consistently if you shut down port 8080 :-) ).
>
> Are you trying to run multiple tomcats?
> I fear it might not work (we never tested that configuration).
> Consider that the deployment "configuration" of AXIS is saved in
> webapps/opal2/WEB-INF/server-config.wsdd I don't know how that file
> can be push to the other instances of tomcat.
>
>
> Luca

It got farther, but ran into a similar problem (catalina.out is 
attached).  It started deploying the services, but ran into the same 
permission problem of "Rejected remote access from host /169.230.27.26" 
for each service that it tried to deploy.

We're not trying to run multiple tomcat instances (yet).  We just want 
to have an Apache instance as the main interface for 
webservices.rbvi.ucsf.edu because we expect to run other CGI-type 
services as well and want to use the same umbrella host name.

Conrad