From OSB we are calling siebel with uid/pwd and session type as = stateless, and getting the sessiontoken in the header
We are storing the session that is retrieved in the java queue with timeout, and using that sessiontoken to call siebel by putting this session token in header.
Most of the calls are successful, but sometimes we are receiving "Session Token is missing or invalid or has expired". When we enabled
tracing, it is logging too much information and not able to exact header that is send and header that is retrieved.
Wondering whether the header variable in OSB is stateful. May be it is because when call to java call out fails, osb is using
old stored header variable to send to siebel and hence getting the ""Session Token is missing or .." . Can it be possible?
In a request response pipeline of the OSB Proxy, the header/body variable contents will remain intact, unless until they are explicitly altered. Hope this give you more insight to solve the issue you are facing.