We had the same issue. I believe the "cause" is that unlike browsers, SOAP clients don't maintain session state so the mid-tier assumes that each new request is a new session - and thus a different user for connection limiting purposes. Support provided us a "fixed" patch 16. I believe it was being handed out only if explicitly requested at the time. So Remedy knows about it, they have a fix for you if you ask for it (and have current support) - although hopefully it's fixed in p19. -Brian ________________________________
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Barb Wagner Sent: Thursday, December 21, 2006 7:35 AM To: [email protected] Subject: Webservices and 9093 errors ** Howdy All Does anyone have information/experience with resolving 9093 errors (user already connected) with web services? Is there a way to force the web service logout after completing the call? Should a well behaved web service automatically terminate it's session? Just looking for some ideas/suggestions of where we can look to resolve our issue ... also any thoughts on if it's not a Remedy Issue what might be the culprit System Info: Remedy v6.3 patch 15 (a little behind on the patches) Thanks in advance for any info! Barb Wagner __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
