Re: [Opaltoolkit-users] Opal 2.4 and Tomcat

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

On 1/16/2014 12:39 PM, Luca Clementi wrote:
> On Thu, Jan 16, 2014 at 9:23 AM, Conrad Huang <co...@cg...> wrote:
>> On 1/15/2014 6:14 PM, Luca Clementi wrote:
>
> [...]
>
>>>
>>> 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.
>>
>
> That's why I didn't like my previous fix. :-(
>
> With a little more time, I crafted a patch which should fix both
> problems and has a much nicer approach.
>
>> 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.
>>
>
> OK that must work.
>
> Thanks again for you very helpful testing.
>
> Luca
>

Yes!  It's working!

Thank you so much for not only getting it to work, but so very quickly.

Conrad