Laura, Ben,
Having double checked how I've typed both the command, these
27 wsrf-query -a -s
https://132.146.233.12:8443/wsrf/services/DefaultIndexService '/*'
28 wsrf-query -s
https://132.146.233.12:8443/wsrf/services/DefaultIndexService '/*'
Both work.
So, I've changed the indexinfo entry to match:
<parameter>
<name>class</name>
<value>org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePrope
rtyQ
ueryNodeSource</value>
</parameter>
<parameter>
<name>endpoint</name>
<value>https://132.146.233.12:8443/wsrf/services/DefaultIndexService</va
lue>
</parameter>
</WebmdsConfig>
But, there is still a tomcat error. The first time I try to query the
index, I get a token length mismatch exception, and subsequent queries
the Connection reset exception is thrown.
The final messages in the container.log are:
[49]:
https://132.146.233.12:8443/wsrf/services/mds/test/execsource/IndexServi
ceEntry
<https://132.146.233.12:8443/wsrf/services/mds/test/execsource/IndexServ
iceEntry>
[50]:
https://132.146.233.12:8443/wsrf/services/mds/test/subsource/IndexServic
e
<https://132.146.233.12:8443/wsrf/services/mds/test/subsource/IndexServi
ce>
[51]:
https://132.146.233.12:8443/wsrf/services/mds/test/subsource/IndexServic
eEntry
<https://132.146.233.12:8443/wsrf/services/mds/test/subsource/IndexServi
ceEntry>
2007-09-07 11:04:34,388 INFO impl.DefaultIndexService
[ServiceThread-11,processConfigFile:107] Reading default registration
configuration from file:
/space/applications/globus/etc/globus_wsrf_mds_index/hierarchy.xml
Nicholas J. Kings (Nick)
Senior Researcher
Next Generation Web Research, BT Group Chief Technology Office
________________________________
From: Laura Pearlman [mailto:[EMAIL PROTECTED]
Sent: 07 September 2007 10:37
To: Kings,NJ,Nick,CXR3 R
Cc: [email protected]
Subject: Re: [gt-user] Tomcat exception while running WebMDS
In your original message, the URL in the indexinfo config file
was
MailScanner warning: numerical links are often malicious:
https://127.0.0.1:8443/wsrf/services/DefaultIndexService
<https://127.0.0.1:8443/wsrf/services/DefaultIndexService>
which is an https url, but the wsrf-query command you ran just
now used an http url. Was that just a typo on the command line (or in
the mail)? Do the URLs at the beginning of your container log file have
http or https?
-- Laura
[EMAIL PROTECTED] wrote:
Laura,
Yes, when I mimic the anonymous access, I get the same
exception on the
command line:
wsrf-query -debug -a -s
MailScanner has detected a possible fraud attempt from
"127.0.0.1:8443" claiming to be
"http://127.0.0.1:8443/wsrf/services/DefaultIndexService";
<http://127.0.0.1:8443/wsrf/services/DefaultIndexService> '/*'
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.SocketException: Broken pipe
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.SocketException: Broken
pipe
at
java.net.SocketOutputStream.socketWrite0(Native Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
The exception in the container.log is below. From
googling around, the
token length exception occurs when trying to talk
"https" over the http
connection (or, visa versa).
2007-09-07 09:36:26,171 ERROR container.GSIServiceThread
[ServiceThread-10,proce
ss:141] Error processing request
java.io.IOException: Token length 1347375956 > 33554432
at
org.globus.gsi.gssapi.net.impl.GSIGssInputStream.readToken(GSIGssInpu
tStream.java:93)
at
org.globus.gsi.gssapi.net.impl.GSIGssInputStream.readHandshakeToken(G
SIGssInputStream.java:54)
at
org.globus.gsi.gssapi.net.impl.GSIGssSocket.readToken(GSIGssSocket.ja
va:60)
Nick
Nicholas J. Kings (Nick)
Senior Researcher
Next Generation Web Research, BT Group Chief Technology
Office
-----Original Message-----
From: Laura Pearlman [mailto:[EMAIL PROTECTED]
Sent: 06 September 2007 20:24
To: Kings,NJ,Nick,CXR3 R
Cc: [email protected]
Subject: Re: [gt-user] Tomcat exception while
running WebMDS
That error message doesn't look like an
authentication
question, but to answer that part of your
question --
currently, webmds works only with index servers
that allow
anonymous access for queries (this is the
default -- you can
check for sure by adding "-a" to the flags in
your wsrf-query
command).
It might be helpful if you could do a wsrf-query
command that
mimicked the conditions that webmds runs under
as closely as
possible, by logging into semantic.info.bt.co.uk
and running
wsrf-query -a "-s
MailScanner warning: numerical links are often
malicious: https://127.0.0.1:8443/wsrf/services/DefaultIndexService
<https://127.0.0.1:8443/wsrf/services/DefaultIndexService> " /
Also, there might be some clues in the Globus
container log.
-- Laura
P.S. If you are restricting access to queries
to your index
server, and you'd like to use webmds to view it,
please let me know.
[EMAIL PROTECTED] wrote:
All,
I get the following exception from
Tomcat, when accessing this URL:
http://semantic.info.bt.co.uk:8080/webmds/webmds?info=indexinf
o&xsl=serv
icegroupxsl
Querying the index server from the
command line works fine:
wsrf-query -s
https://semantic:8443/wsrf/services/DefaultIndexService
'/*'
The configuration in the indexinfo file
is (as Tomcat is running on
semantic):
<name>endpoint</name>
<value>MailScanner warning: numerical links are
often malicious: https://127.0.0.1:8443/wsrf/services/DefaultIndexServic
<https://127.0.0.1:8443/wsrf/services/DefaultIndexServic>
e</value>
Does the tomcat process need it's own
certificate?
Regards,
Nick
exception trace
org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePr
opertySour
ceException: ; nested exception is:
java.net.SocketException:
Connection reset
org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePr
opertyHelp
er.queryResourceProperties(ResourcePropertyHelper.java:121)
org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePr
opertyQuer
yNodeSource.getNode(ResourcePropertyQueryNodeSource.java:82)
org.globus.mds.webmds.xmlSources.xmlDomNode.NodeXmlSource.getX
mlSource(N
odeXmlSource.java:128)
org.globus.mds.webmds.WebmdsServlet.getSource(WebmdsServlet.java:296)
org.globus.mds.webmds.WebmdsServlet.doGet(WebmdsServlet.java:114)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.net.SocketException: Connection
reset
org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
org.apache.axis.strategies.InvocationStrategy.visit(Invocation
Strategy.j
ava:32)
org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
org.apache.axis.client.Call.invokeEngine(Call.java:2727)
org.apache.axis.client.Call.invoke(Call.java:2710)
org.apache.axis.client.Call.invoke(Call.java:2386)
org.apache.axis.client.Call.invoke(Call.java:2309)
org.apache.axis.client.Call.invoke(Call.java:1766)
org.oasis.wsrf.properties.QueryResourcePropertiesSOAPBindingSt
ub.queryRe
sourceProperties(QueryResourcePropertiesSOAPBindingStub.java:415)
org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePr
opertyHelp
er.queryResourceProperties(ResourcePropertyHelper.java:119)
org.globus.mds.webmds.xmlSources.resourceProperties.ResourcePr
opertyQuer
yNodeSource.getNode(ResourcePropertyQueryNodeSource.java:82)
org.globus.mds.webmds.xmlSources.xmlDomNode.NodeXmlSource.getX
mlSource(N
odeXmlSource.java:128)
org.globus.mds.webmds.WebmdsServlet.getSource(WebmdsServlet.java:296)
org.globus.mds.webmds.WebmdsServlet.doGet(WebmdsServlet.java:114)
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Nicholas J. Kings (Nick)
Senior Researcher
Next Generation Web Research, BT Group
Chief Technology Office
