Is someone working to fix this bug? asankha wrote: > > Chuck Brinkman wrote: >> We are seeing responses of one type that have the body of another type. >> For example say we have serviceA that returns a serviceAresponse and >> serviceB that returns a serviceBresponse. We have captured the network >> packet and see things like serviceAresponse that has the data from a >> serviceBresponse. It appears to be related to a flash client we have. >> The flash client will open a connection and can send a second request >> using the original connection before it gets a response or a timeout from >> the first request. I'm still working on the issue but it is in some way >> good to know that I'm not the only one thinking Axis2 has a thread safety >> issue. >> > Your flash client is using HTTP pipelining > <http://en.wikipedia.org/wiki/HTTP_pipelining> and this seems like a > limitation/bug on the http/s transport, and not necessarily an Axis2 > thread safety issue. Can you post the tcpdump traces you have? > > asankha > >
-- View this message in context: http://www.nabble.com/Axis2-1.4-not-Thread-safe-%28possible-bug%29-tp17414803p17548699.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
