On Wednesday 17 November 2010 7:42:09 am Villoud Pierre Julien wrote: > So I increased the memory, and decreased the ReceiveTimeout and the > ConnectionTimeout down to 1500 milliseconds, and still, at some point, i'm > getting "java.lang.OutOfMemoryError: unable to create new native > thread"... > > I don't know what else to do ! >
Is there a full stack trace for that? Dan > Pierre-Julien > > -----Message d'origine----- > De : Daniel Kulp [mailto:[email protected]] > Envoyé : lundi 15 novembre 2010 17:45 > À : Villoud Pierre Julien > Cc : [email protected] > Objet : Re: Using CXF asynchronously > > On Monday 15 November 2010 11:41:41 am Villoud Pierre Julien wrote: > > Hello an sorry about the very late reply. > > > > I think that the request actually timeouts, but the out of memory errors > > happened when a lot of request are made and my guess is that there are > > more request made than request that timeout. So at some point, a out of > > memory error occurs. I am doubling the memory of my Tomcat and see how it > > goes. I'll keep you posted. > > If you really don't care about the response, you could also decrease the > timeout to something a LOT smaller than 60 seconds. See: > > http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html > > for the ReceiveTimeout setting. Drop it to 2 seconds or something and > they should start timing out pretty quick. > > Dan > > > Thanks again for your help > > > > Pierre-Julien > > > > -----Message d'origine----- > > De : Daniel Kulp [mailto:[email protected]] > > Envoyé : mercredi 10 novembre 2010 19:52 > > À : [email protected] > > Cc : Villoud Pierre Julien > > Objet : Re: Using CXF asynchronously > > > > On Wednesday 10 November 2010 2:50:02 am Villoud Pierre Julien wrote: > > > Hi and thanks for your answer (@Steve I'm sorry, I didn't mean to steal > > > your question...) > > > > > > I'm using the 2.2.10 version. So what happens if a lot of call like > > > this happen : client.invoke(new ClientCallback(), "methodName", > > > params...); > > > > > > You think that the request should timeout ? > > > > Yes, it should. By default it's 60 seconds. That said, if the server > > actually responds, it should just complete normally and the callback > > called. > > > > Is there any chance you could create a small testcase (like modify the > > jaxws_async example) that shows the problems? > > > > Dan > > > > > I'm really not expecting > > > anything in return that's why i'm calling the invoke function like > > > this. I have a Hello World method but I don't have much time to test. > > > If it's not something you already have heard of, I will go back to > > > synchronous calls and work on that as soon as I can. > > > > > > Thanks again > > > > > > Pierre-Julien > > > > -- > > Daniel Kulp > > [email protected] > > http://dankulp.com/blog > > > > > > > > Ce message et les pièces jointes sont confidentiels et réservés à l'usage > > exclusif de ses destinataires. Il peut également être protégé par le > > secret professionnel. Si vous recevez ce message par erreur, merci d'en > > avertir immédiatement l'expéditeur et de le détruire. L'intégrité du > > message ne pouvant être assurée sur Internet, la responsabilité du groupe > > Atos Origin ne pourra être recherchée quant au contenu de ce message. > > Bien que les meilleurs efforts soient faits pour maintenir cette > > transmission exempte de tout virus, l'expéditeur ne donne aucune > > garantie à cet égard et sa responsabilité ne saurait être recherchée > > pour tout dommage résultant d'un virus transmis. > > > > This e-mail and the documents attached are confidential and intended > > solely for the addressee; it may also be privileged. If you receive this > > e-mail in error, please notify the sender immediately and destroy it. As > > its integrity cannot be secured on the Internet, the Atos Origin group > > liability cannot be triggered for the message content. Although the > > sender endeavours to maintain a computer virus-free network, the sender > > does not warrant that this transmission is virus-free and will not be > > liable for any damages resulting from any virus transmitted. > > -- > Daniel Kulp > [email protected] > http://dankulp.com/blog > > > > Ce message et les pièces jointes sont confidentiels et réservés à l'usage > exclusif de ses destinataires. Il peut également être protégé par le > secret professionnel. Si vous recevez ce message par erreur, merci d'en > avertir immédiatement l'expéditeur et de le détruire. L'intégrité du > message ne pouvant être assurée sur Internet, la responsabilité du groupe > Atos Origin ne pourra être recherchée quant au contenu de ce message. Bien > que les meilleurs efforts soient faits pour maintenir cette transmission > exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard > et sa responsabilité ne saurait être recherchée pour tout dommage > résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended solely > for the addressee; it may also be privileged. If you receive this e-mail > in error, please notify the sender immediately and destroy it. As its > integrity cannot be secured on the Internet, the Atos Origin group > liability cannot be triggered for the message content. Although the sender > endeavours to maintain a computer virus-free network, the sender does not > warrant that this transmission is virus-free and will not be liable for > any damages resulting from any virus transmitted. -- Daniel Kulp [email protected] http://dankulp.com/blog
