Hi, you can configure the transaction manager timeout (in tomee.xml) but it means your tx lasts more than 10mn (default)
*Romain Manni-Bucau* *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2012/10/16 membersound <[email protected]> > Hi, > > how can I set the Server timeout to not get a "Transaction has timed out" > exception any more? > > Problem is as follows: I have a JAX-WS Webservice and a client. The client > may call a method from WS, but this method may sometimes last very long > (1h+). I want the connection to be keept alive during the method > processing, > because the return value depends on the long routine and has to be given > back to the client. > > I'm sure this is a server-side problem. Because on client-side, I already > tried several things like BindingProvider or setting HTTPConduit manually, > like: > > > ((BindingProvider)port).getRequestContext().put("com.sun.xml.internal.ws.request.timeout", > 0); > or: > Client client = ClientProxy.getClient(greeter); > HTTPConduit http = (HTTPConduit) client.getConduit(); > HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy(); > httpClientPolicy.setConnectionTimeout(0); > http.setClient(httpClientPolicy); > > > Please can anybody help how I can keep an invoked method request alive for > a > long time until the return response is send? > > Thanks > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Transaction-has-timed-out-how-to-set-the-server-timeout-tp4658090.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
