From: Rob M. <Rob.Mew@NetBenefit.com> - 2002-08-02 13:29:45
|
Dan, It is very strange. I did ask Neulevel about it but they said they didn't support the Tucows rtk. Could it be the way our system is set up. We are using a singleton object to maintain the connection (EPPClient). We have a separate thread running that polls the registry every few minutes to maintain the connection. We have multiple simultaneous commands like domain.check(), contact.add(), domain.add() being issued using the singleton object for connection. Thanks for you help. Cheers Rob Here's another one below for contact.add(). Notice the <?xml version='1.0' encoding='UTF-8'?> is missing... Fri Aug 02 08:51:16 GMT 2002:<I> <NNE> com.tucows.oxrs.epp.rtk.biz.EPPClient.processXML(String) {Fri Aug 02 08:51:16 GMT 2002}[ 2] : Response XML is [ <response> <msg lang="en-US">Command completed successfully</msg> <value>SRS Minor Code: 20027</valu e> </result> <domain:chkData xmlns="urn:iana:xml:ns:domain-1.0" xmlns:domain="urn:iana:xml:ns:domain-1.0" xsi:schemaLocation ="urn:iana:xml:ns:domain-1.0 domain-1.0.xsd"> </domain:chkData> <trID> <svTRID>7678X5Z65CWVMSD-0ITHOW-SERVER</svTRID> </re sponse><?xml version="1.0" encoding="UTF-8"?><epp xmlns="urn:iana:xml:ns:epp-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-i nstance" xsi:schemaLocation="urn:iana:xml:ns:epp-1.0 epp-1.0.xsd"> <response> <result code="1000"> <msg lang="en-US">Command completed successfully</msg> <value>SRS Major Code: 2000</value> <value>SRS Minor Code: 20009</value> <value>--CONTACT_S UCCESSFULLY_ADDED</value> </result> <resData> <contact:creData xmlns="urn:iana:xml:ns:contact-1.0" xmlns:contact="urn:iana: xml:ns:contact-1.0" xsi:schemaLocation="urn:iana:xml:ns:contact-1.0 contact-1.0.xsd"> <contact:id>62220632-NETBENA</contact: id> </contact:creData> </resData> <trID> <clTRID>YTEGM3ZFNQ6TSZS</clTRID> <svTRID>YTEGM3ZFNQ6TSZS-0ITHOW-SERVER</svTRID > </trID> </response></epp>] Fri Aug 02 08:51:16 GMT 2002:<I> <NNE> com.tucows.oxrs.epp.rtk.biz.xml.EPPXMLErrors.store(SAXParseException, String) {Fri Aug 0 2 08:51:16 GMT 2002}[0] : Exception in XML Parsing: [2 at line number, 1: The element type "response" must be terminated by the matching end-tag "</response>". ] -----Original Message----- From: Daniel Manley [mailto:dm...@tu...] Sent: 02 August 2002 13:47 To: Rob Mew Cc: 'Andrew Sullivan'; 'epp...@li...' Subject: Re: [Epp-rtk-devel] anybody else getting sax parser errors with r tk 0.38? BLUEHILL Rob, looking at the original email you posted on the list, it looks like the .biz server is not ending the <check> response with </epp>, so the RTK parser keep waiting on the socket for more data. When the RTK throws the SAX exception is it the handler of the <check> or the <poll> that throws the exception? Do you know where that other </epp> is going? Maybe Neulevel isn't sending it at all, but that would mean that our usage of that RTK would show the same errors... hmmm... mysterious. Dan Rob Mew wrote: >yep you're right we are still getting the SAX errors... > >-----Original Message----- >From: Andrew Sullivan [mailto:an...@li...] >Sent: 01 August 2002 21:30 >To: 'Andrew Sullivan'; 'epp...@li...' >Subject: Re: [Epp-rtk-devel] anybody else getting sax parser errors with >r tk 0.38? BLUEHILL > > >On Thu, Aug 01, 2002 at 10:40:21AM +0100, Rob Mew wrote: > > >>Andrew, >> >>Do you think it's something to do with the client transaction id? I know >>for domain checks I use the same static value for both our servers. I've >> >> > >That shouldn't make any difference. Several users never change the >client TRID at all. > >A > > This email has been scanned for viruses by NetBenefit using Sophos anti-virus technology This email has been scanned for viruses by NetBenefit using Sophos anti-virus technology |