[seek-dev] setting schema location port number.

Kevin Ruland kruland at ku.edu
Tue Sep 6 11:16:12 PDT 2005


Jing,

It's a standalone tomcat -- configured to run at port 8080.

Kevin

Jing Tao wrote:

> Hi, Kevin:
>
> Weird, the gt3 will load schema from 8080 port as default. And when I
> setup my local machines port as 8090 rather than 8080, the only thing
> I did is in tomcat's server.xml, change the port from 8080 to 8090,
> then the schema will be load from 8090.
>
> So my question is: the "another" machine is tomcat stand alone or
> combined with appache?
>
> Last week I was in vacation, so just read this email.
>
> Thanks.
>
> Jing
>
> Jing Tao
> National Center for Ecological
> Analysis and Synthesis (NCEAS)
> 735 State St. Suite 204
> Santa Barbara, CA 93101
>
> On Thu, 1 Sep 2005, Kevin Ruland wrote:
>
>> Date: Thu, 01 Sep 2005 08:22:46 -0500
>> From: Kevin Ruland <kruland at ku.edu>
>> To: seek-dev at ecoinformatics.org
>> Subject: [seek-dev] setting schema location port number.
>>
>>
>> On to the last problem, I hope.
>>
>> The latest problem is when the service is activated, it tries to load
>> the WSDL.  It does this by envoking the WSDLGenerator.getServiceWSDL()
>> method.  For some unknown reason, it's trying to pull it from:
>>
>> http://129.237.201.189:80/ogsa/schema/bla/bla.wsdl
>>
>> The key here is it's looking for port 80 which I don't have running.  On
>> kuecogrid, it loads it from:
>>
>> http://kuecogrid.ittc.ku.edu:8080/ogsa/schema/bla/bla.wsdl
>>
>> I've inserted some additional debugging messages in the WSDLGenerator
>> code and it appears that the port number is somehow set correctly in the
>> kuecogrid deployment (as opposed to not being set and defaulted to
>> 8080).
>>
>> It doesn't appear to be related to the publishHostName=true parameter.
>> I turned that on in my test deployment and the url becomes:
>>
>> http://anotherone.nhm.ku.edu:80/....
>>
>> I can manually set the port number by using <parameter name="port"
>> value="8080"/> in the <service> block for
>> EcoGridQueryInterfaceLevelOne.  Alternatively I can use a System
>> property named "org.globus.ogsa.schema.root", or a Container Config
>> property named "schemaRoot".
>>
>> The really puzzling thing is I don't see either of these being set on
>> kuecogrid.
>>
>> Any ideas?
>>
>> Kevin
>> _______________________________________________
>> Seek-dev mailing list
>> Seek-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/seek-dev
>>
>>


More information about the Seek-dev mailing list