Tim Moores wrote:If it's not a setting in the Axis Admin web app then it's something in the deployment descriptor. Either way, the Axis documentation should cover it.
HTTP pipelining is a client-side issue. Are you using the same HTTP connection for both requests? If not, then pipelining wouldn't happen to begin with.
Tim Moores wrote:This seems highly relevant: http://www.mail-archive.com/[email protected]/msg17545.html (5th result I got by searching for "axis multithreading", by the way).
Tim Moores wrote:It's not so much Axis handling requests in parallel, as the underlying servlet container handling simultaneous requests. If those requests use a shared resource (like the same DB tables), then you should pay attention to resource congestion there. For a DB, that would be things like table-level locking vs. row-level locking, and transaction handling. Not sure if that answers your question, which is rather broad; maybe you can narrow it down to something more specific.
Winston Gutkowski wrote:
Sumukh Deshpande wrote:I have a situation where I have to put getters and setters for a sublass reference in superclass...
I'd go a bit further than the others and say that it doesn't make much sense to me - certainly the "setter" part. The "getter" part is, however, possible with generics, viz:No concrete class should ever need to extend it directly, but it could be useful for "skeleton" classes that need to return properly typed instances, because it saves an explicit cast operation.
However, I can't think of any reason why you would need a subclass setter in a superclass. Maybe you could explain why you think you need it?
Winston