Leif,

Thanks for your help with this.  Your symptom is the same as was 
reported by another individual, but I was not able to reproduce it, 
because I did not know it was connected to the version of Xerces 
being used.  I will see what older versions of Xerces I can find and 
try to reproduce the problem.

On 13 May 2003 at 9:01, Leif Nilsson TACMa wrote:

>  The service in question returns an XML document either as a String or as an
>  attachment. It was the String cas that gave me problem (of course). What I
>  got was a string where alla <, > and " were removed.
>  Example: <root> <element a1="some value"/> </root> 
>                would return as
>            root element a1=some value root
>  
>  I checked the socket traffic which was OK (the <, > and " where coded
>  correctly (not to be mixed up with the SOAP message XML)) Furthermore it was
>  exactly the same as ever before (note that I have not yet upgraded the
>  service.)
>  
>  /Leif
>  
>  -----Original Message-----
>  From: Scott Nichol [mailto:snicholnews@[...].com]
>  Sent: Monday, May 12, 2003 23:13
>  To: Leif Nilsson TACMa; soap-dev@[...].org
>  Subject: RE: Help soap call hangs
>  
>  
>  Can you be more specific about "my application did not work with the 
>  build in question unless I upgraded..."?  Did you get an exception?  
>  If so, what was it?
>  
>  On 12 May 2003 at 12:54, Leif Nilsson TACMa wrote:
>  
>  > Hi!
>  > 
>  > In order to test the theory of socket connect timeout I've upgraded to 
>  >  nighlty build 2003-05-06.
>  > 
>  > Don't know yet if this solves the problem but I ran into a problem with
>  this
>  >  build however:
>  > 
>  > Some investigation showed that my application did not work with the build
>  in
>  > 
>  >  question unless I upgraded from Xerces 1.4.1 to Xerces 1.4.4 (1.4.3
>  worked
>  > as well,
>  >  have not tried 1.4.2).
>  > 
>  > In the installation part of the soap 2.3.1 documentation (client side) it
>  is
>  > stated 
>  > that it should work with 1.1.2 or higher. 
>  > 
>  > (I understand that this is a nightly build so the documentation might not
>  be
>  > valid but I thought it worth noting.)
>  > 
>  > /Leif
>  > 
>  > -----Original Message-----
>  > From: Scott Nichol [mailto:snicholnews@[...].com]
>  > Sent: Tuesday, May 06, 2003 15:12
>  > To: soap-dev@[...].org
>  > Subject: RE: Help soap call hangs
>  > 
>  > 
>  > Yes, the one timeout value is used for both connect and read/write, 
>  > but only in the nightly builds, not 2.3.1.  Also, you must be using 
>  > JDK 1.4, which added the ability to connect a socket separate from 
>  > instantiating it.
>  > 
>  > On 6 May 2003 at 9:00, Leif Nilsson TACMa wrote:
>  > 
>  > > Hi!
>  > > 
>  > > Hmm. Whether you are right or not this seems to be a good reason 
>  > > for upgrading (some footwork though). Hopefully upgrading to 2.3.1 
>  > > will solve this problem. Is the connect timeout set via 
>  > > SOAPHTTPConnection.setTimeout?
>  > > 
>  > > Are there anymore timeouts to think about?
>  > > 
>  > > /Leif
>  > > 
>  > > -----Original Message-----
>  > > From: Scott Nichol [mailto:snicholnews@[...].com]
>  > > Sent: Monday, May 05, 2003 20:18
>  > > To: Leif Nilsson TACMa; soap-dev@[...].org
>  > > Subject: Re: Help soap call hangs
>  > > 
>  > > 
>  > > Leif,
>  > > 
>  > > I cannot say I've experienced this, but something to notice is that 
>  > > the 2.2 code did not have any timeout for establishing the 
>  > > connection, just for the request/response.  I would think that what 
>  > > you are seeing (no timeout) is possible if the SSL connection is 
>  > > established at the TCP level, but the SSL handshaking does not 
>  > > proceed to conclusion for some reason.  I am not sure how to verify 
>  > > this without either sniffing the line (even then, I'm not sure how 
>  > > you would read some of the  encrypted SSL handshaking) or turning on 
>  > > SSL debugging.
>  > > 
>  > > On 5 May 2003 at 12:08, Leif Nilsson TACMa wrote:
>  > > 
>  > > > Hi!
>  > > > 
>  > > > Has anyone experianced that a SOAP call just hangs for ever and ever ?
>  > > > 
>  > > > We use soap 2.2 for client and server implementatione.
>  > > > The client use https with client and server certificate to call IIS
>  that
>  > > > connects to soap 2.2 via Resin (servlet container).
>  > > > The soap service calls an Oracle DB via jdbc.
>  > > > 
>  > > > We have an installed base of clients continuesly calling our server
>  > > > implementation.
>  > > > 
>  > > > The problem seems to be that calling this service sometimes just
>  hangs.
>  > > > We set the timeout to one hour via SOAPHTTPConnection.setTimeout.
>  > > > We use log4j for tracing and the code looks something like:
>  > > > 
>  > > >     protected Element request(String methodName, String
>  methodEncoding,
>  > > > Vector params) {
>  > > >         Response resp = null;
>  > > >         try {
>  > > >             URL  url  = new URL(m_cfg.getItalkHost());
>  > > >             Call call = buildCall(methodName, methodEncoding, params);
>  > //
>  > > > builds a call object and sets the timeout to one hour via
>  > > > SOAPHTTPConnection.setTimeout
>  > > > 
>  > > >             // Invoke the call.
>  > > >             if (cat.isInfoEnabled()) cat.info("Call " +
>  > > > m_cfg.getItalkService() + "." + methodName + "@" +
>  > m_cfg.getItalkHost());
>  > > >             resp = call.invoke(url, "");
>  > > >         }
>  > > >         catch (MalformedURLException e) {
>  > > >             cat.error("Caught MalformedURLException : " +
>  > e.getMessage());
>  > > >             return null;
>  > > >         }
>  > > >         catch (SOAPException e) {
>  > > >             //e.printStackTrace();
>  > > >             cat.error("Caught SOAPException (" + e.getFaultCode() +
>  "):
>  > "
>  > > +
>  > > > e.getMessage());
>  > > >             return null;
>  > > >         }
>  > > >         catch (Exception e) {
>  > > >             cat.error("Caught some Exception when SOAPing with I-talk:
>  "
>  > +
>  > > > e.getMessage());
>  > > >             return null;
>  > > >         }
>  > > > 
>  > > >         return handleResponse(resp);
>  > > >     }
>  > > > 
>  > > >     private Element handleResponse(Response resp) {
>  > > >         if (cat.isDebugEnabled()) cat.debug("handle response!");
>  > > > 
>  > > >     ......  }
>  > > > 
>  > > > 
>  > > > 
>  > > > As you can see traces will be made just before and just after calling
>  > the
>  > > > request method.
>  > > > (The handle reponse returns an element but most important it works for
>  > > both
>  > > > attachments and no attachments)
>  > > > 
>  > > > When I say that the call hangs we get the trace before calling but no
>  > > trace
>  > > > for the response.
>  > > > 
>  > > > Any clues ????
>  > > > 
>  > > > 
>  > > > Leif Nilsson
>  > > > Software Engineer
>  > > > 
>  > > > TAC AB
>  > > > Jägershillgatan 18
>  > > > SE-213 75 Malmö, Sweden
>  > > > Direct	+46 40 38 69 56
>  > > > Fax	+46 40 21 82 87
>  > > > Mobile	+46 70 299 89 56
>  > > > www.tac-global.com
>  > > > 
>  > > > This email is intended only for the use of the individual or entity to
>  > > whom
>  > > > it is addressed. It may contain information that is privileged,
>  > > confidential
>  > > > or otherwise protected from disclosure under applicable law. If you
>  have
>  > > > received this transmission in error, please delete it immediately and
>  > > notify
>  > > > me by mailing me.
>  > > > 
>  > > > 
>  > > > 
>  > > 
>  > > 
>  > > Scott Nichol
>  > > 
>  > > Do not reply directly to this e-mail address,
>  > > as it is filtered to only receive e-mail from
>  > > specific mailing lists.
>  > > 
>  > > 
>  > 
>  > 
>  > Scott Nichol
>  > 
>  > Do not reply directly to this e-mail address,
>  > as it is filtered to only receive e-mail from
>  > specific mailing lists.
>  > 
>  > 
>  
>  
>  Scott Nichol
>  
>  Do not reply directly to this e-mail address,
>  as it is filtered to only receive e-mail from
>  specific mailing lists.
>  
>  


Scott Nichol

Do not reply directly to this e-mail address,
as it is filtered to only receive e-mail from
specific mailing lists.