I have done something similar, when I used a custom JDBC connection pool library. When loaded, it started a separate thread that woke up every xx seconds to reclaim orphaned connections or pro-actively re- connect when connections were broken. Based on my experience, your technique should work.
On 1 Apr 2003 at 15:43, Malte Kempff wrote: > Hi *.* > > I have got the following problem or situation: > > I have one class for miscellaneous SOAP-services doing SQL-calls. > This class has got the scope of "Application", declared in the > SOAP-deploydescriptor. > Some of the sql-calls give back unpredictable huge resultsets, so I was > forced to block those > and give them to a client by using a selfbuilt mechanism. > That means, that a client gets a quest-handle by the first call and polls > the resultset blockwise by passing the handle > back again to a certain service. > > My possible trouble is that it could happen that memory is not set free, > if a client crashes or a user kills the > client while it was polling such a blocked resultset. > My idea is to look up the quests, which are held by the server within a > HashMap, by a cycle and watch if they have been accessed > during a certain period of time. Therefore timestamps are also to be > recognised. > My question here is whether it is possible or allowed to start > Timer-objects in such a SOAP-service-class, which scope is "Application". > Or is this not a correct solution? > > looking ahead for an advice > > Malte > > > > > > -----Ursprungliche Nachricht----- > Von: Scott Nichol [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 31. Marz 2003 00:45 > An: [EMAIL PROTECTED] > Betreff: Re: Content-length woes. > > > Have you tried posting to [EMAIL PROTECTED] > > On 29 Mar 2003 at 16:17, Reid wrote: > > > > > Please Help! > > > > I am using Apache Axis to send a SOAP reqeust to a remote server, but > I am never getting a response back. My application just "hangs" for a > loooong time. Hours. If I leave it overnight, I come back the next day to > an IO exception stating that the connection timed-out. I have confirmed > that the remote server is receiving my request, that it is properly > formatted, AND that the response is being sent to me. My feeling is that > the remote server is setting the content-length of the message incorrectly > (too large for content of the response), and my code just ends up waiting > for > "the rest of the message" that doesn't exist > > My problem is that I do not understand the content-lenght field, or > rather, what all it includes. The response that I am getting from the > remote server is below. Can anyone tell from the message itself if the > content-lenght is set correctly? The server admin says that he includes > all > leading spaces (to accomplish the indenting/formatting) in the count for the > content length, as well as the cr/lf at the end of each line. I would have > assumed that this should not be included. > > > > Thanks in advance for your response to this question! > > > > Reid > > > > ----------------------------------------------- > > > > HTTP/1.1 200 OK > > > > Date: Fri, 28 Mar 2003 21:43:35 GMT > > > > Content-Type: text/xml > > > > Content-Length: 652 > > > > > > <?xml version="1.0" encoding="UTF-8"?> > > <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";> > > <soap:Body> > > <GetCustomerResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xmlns="http://www.giro.ca/AccesService/";> > > <GetCustomerResult> > > <ResultStatus> > > <Code>CstmNF</Code> > > <Level>Error</Level> > > <Message>Le client 55000 n'existe pas.</Message> > > </ResultStatus> > > </GetCustomerResult> > > </GetCustomerResponse> > > </soap:Body> > > </soap:Envelope> > > > > > 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.
