Searching the archives for this error suggests a classloader issue: http://www.globus.org/mail_archive/discuss/2005/02/msg00163.html http://www-unix.globus.org/mail_archive/discuss/2004/12/msg00012.html
Cosmin wrote: > Thanks for the idea. > It helped us to identify the problem from the other side of the connection. > So, we've found that, when we're trying that java command and it appears > the exception mentioned earlier, in the catalina.log from it apears the > following problem: > > " > Mar 20, 2009 2:23:33 PM > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler > processConnection > SEVERE: Error reading request, ignored > java.lang.IllegalArgumentException: Unexpected certificate type: class > org.bouncycastle.jce.provider.X509CertificateObject > at > org.globus.gsi.bc.BouncyCastleUtil.getIdentity(BouncyCastleUtil.java:443) > at > org.globus.gsi.proxy.ProxyPathValidator.getIdentity(ProxyPathValidator.java:108) > > at > org.globus.gsi.gssapi.GlobusGSSContextImpl.verifyChain(GlobusGSSContextImpl.java:724) > > at > org.globus.gsi.gssapi.GlobusGSSContextImpl.acceptSecContext(GlobusGSSContextImpl.java:303) > > at > org.globus.gsi.gssapi.net.GssSocket.authenticateServer(GssSocket.java:124) > at > org.globus.gsi.gssapi.net.GssSocket.startHandshake(GssSocket.java:142) > at > org.globus.tomcat.catalina.net.HTTPSSocket.startHandshake(HTTPSSocket.java:46) > > at > org.globus.gsi.gssapi.net.GssSocket.getInputStream(GssSocket.java:172) > at > org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:652) > > at > org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) > > at > org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) > > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) > > at java.lang.Thread.run(Thread.java:595) > > " > > Do you have any idea ? > > > Thank you, > > Cosmin Placinta, > IFIN-HH > Romania > > On 19.03.2009, at 15:46, Jim Basney wrote: > >> Yes, the peer could be on the same machine, i.e., a local socket >> connection. Perhaps both socket endpoints are running inside the same >> Tomcat instance. Still, I suggest finding out what peer is being >> connected to in the java.net.URL.openStream() call and looking for an >> error message on the other side of the connection that explains why it >> is being closed. >> >> Cosmin wrote: >>> The problem described is from a local test. It is a local test which >>> impliese only a single machine with GT 4.0.5 installed on it and OGSADAI >>> 3.0 with a PostgreSQL database server. It uses Tomcat as a webserver. >>> >>> >>> Thanks, >>> >>> Cosmin Placinta >>> >>> >>> On 19.03.2009, at 14:49, Jim Basney wrote: >>> >>>> A java.io.EOFException from GSIGssInputStream.readHandshakeToken tells >>>> me the peer aborted the connection during the GSI handshake. Do you get >>>> any error from the peer? >>>> >>>> Mike Jackson wrote: >>>>> >>>>> Hi Cosmin, Globus users, >>>>> >>>>> I suggested this e-mail list since we in the OGSA-DAI team had run out >>>>> of suggestions for Cosmin to try and thought that maybe someone >>>>> here has >>>>> seen a similar error not necessarily in using OGSA-DAI with GT >>>>> security >>>>> but in using anything with GT security (it'd be useful for us to know >>>>> any possible causes and solutions too!). >>>>> >>>>> Cheers, >>>>> >>>>> mike >>>>> >>>>> On Thu, 19 Mar 2009, Cosmin wrote: >>>>> >>>>>> Dear all, >>>>>> >>>>>> We have implemented GT 4.0.5 on Centos 5 with the desire to use it in >>>>>> combination with ogsa-dai. All the instalation went well. Also in >>>>>> ogsa >>>>>> as well. >>>>>> >>>>>> The problem is that after the instalation of ogsa, there a couple of >>>>>> tests you can perform. >>>>>> One of them is to invoke a method from a client.toolkit class in >>>>>> order >>>>>> to see if there are results coming from the server. >>>>>> >>>>>> So, we've tried the following command: >>>>>> " >>>>>> java uk.org.ogsadai.client.toolkit.gt.example.GTSecureSQLClient -u >>>>>> "https://intrn-dhcp-169.nipne.ro:8444/wsrf/services/dai/"; -d >>>>>> PostgreSQLDataResource -q "SELECT * FROM littleblackbook where id < >>>>>> 10" -tls >>>>>> " >>>>>> >>>>>> and the server gives us the following exception: >>>>>> " >>>>>> Exception in thread "main" >>>>>> uk.org.ogsadai.client.toolkit.exception.ServerURLInvalidException: A >>>>>> problem occured initialising the server. >>>>>> at uk.org.ogsadai.client.toolkit.ServerFactory.getWSDL(Unknown >>>>>> Source) >>>>>> at uk.org.ogsadai.client.toolkit.ServerFactory.getServer(Unknown >>>>>> Source) >>>>>> at uk.org.ogsadai.client.toolkit.ServerProxy.getServer(Unknown >>>>>> Source) >>>>>> at >>>>>> uk.org.ogsadai.client.toolkit.ServerProxy.getDataRequestExecutionResource(Unknown >>>>>> >>>>>> >>>>>> Source) >>>>>> at uk.org.ogsadai.client.toolkit.example.SQLClient.execute(Unknown >>>>>> Source) >>>>>> at >>>>>> uk.org.ogsadai.client.toolkit.gt.example.GTSecureSQLClient.main(Unknown >>>>>> >>>>>> Source) >>>>>> Caused by: java.io.EOFException >>>>>> at >>>>>> org.globus.gsi.gssapi.net.impl.GSIGssInputStream.readHandshakeToken(GSIGssInputStream.java:56) >>>>>> >>>>>> >>>>>> >>>>>> at >>>>>> org.globus.gsi.gssapi.net.impl.GSIGssSocket.readToken(GSIGssSocket.java:60) >>>>>> >>>>>> >>>>>> >>>>>> at >>>>>> org.globus.gsi.gssapi.net.GssSocket.authenticateClient(GssSocket.java:110) >>>>>> >>>>>> >>>>>> >>>>>> at >>>>>> org.globus.gsi.gssapi.net.GssSocket.startHandshake(GssSocket.java:140) >>>>>> >>>>>> at >>>>>> org.globus.gsi.gssapi.net.GssSocket.getOutputStream(GssSocket.java:161) >>>>>> >>>>>> at >>>>>> org.globus.net.GSIHttpURLConnection.getInputStream(GSIHttpURLConnection.java:155) >>>>>> >>>>>> >>>>>> >>>>>> at java.net.URL.openStream(URL.java:1007) >>>>>> ... 6 more >>>>>> " >>>>>> >>>>>> We've ask for help to the ogsadai support team and they send us to >>>>>> this mailing list. >>>>>> Can you help us with this problem ? >>>>>> Has anybody there tried the ogsadai and had the same problems ? >>>>>> >>>>>> >>>>>> Thank you, >>>>>> >>>>>> Cosmin Placinta, >>>>>> IFIN-HH >>>>>> Romania >
smime.p7s
Description: S/MIME Cryptographic Signature
