Hi, my web service runs in scope="soapsession" up on a client request, call it session 1, the following functions are called in sequence for my login cycle init(), login(), fktmap(), fktmap(), fktmap(),
then I start the next client, calle it session 2) and the following functions should becalled init(), login(), fktmap(), fktmap(), fktmap(), but the following functions are called in sequence destroy(), init(), login(), fktmap(), fktmap(), fktmap(), in bold the axis2 requierd functions one needs to implement for scope="soapsession" destroy() is the bad guy which deletes me the previous created instance; hence thereafter client 1 / session 1 is inoperable and returns a fault to the client telling me that ServicegroupId is invalid but that is not true, as TcpMonitor proves the opposit for every more session 1 calls to fktmap() Question: under which conditions, httpMessageRequestHeader issue, http protocol dependent, is destroy() called? Note: with the primary call action="urn:login" the server responses with a setCooky and passes me the cooky=JSnnnnn... what httpRequestMessageHeader must be there or absent that a first request from a new session does not call destry() Only then will consecutive requests with the same ServiceGroupId in fact reach the old service instance to which it belongs; So a request with action="urn:login" shall hit init(), then login(), in absence of a ServicegroupId, but at no time destroy() Josef
