We still see this issue in the latest packs. We need to fix this or recommend users to disable LT when installing P2-features.
/Charitha On Fri, Oct 12, 2012 at 8:22 AM, Amila Suriarachchi <[email protected]> wrote: > I think we need to thing the problem from the beginning. > > We use this dual channel technique for this to avoid http connection time > outs. We use addressing order to send the reply in a separate channel > (using addressing replyTo header) to avoid time outs of thread that invokes > the stub. > > With local transport we don't have such time outs. We can send and receive > in the same thread as in any other local transport call. > > thanks, > Amila. > > > On Fri, Oct 12, 2012 at 7:55 AM, Pradeep Fernando <[email protected]>wrote: > >> Hi, >> what if we populate the carbonContext upon receiving the context. This >> is the exact thing that happens in servletTransport >> (CarbonContextCreator). >> >> The context information get lost due to spawning of a another thread. >> The other workaround would be to set the existing CarbonContextDetails >> (taken from the front-end side) to the messageContext, since the >> getCurrentContext looks at other scopes first before retrieving from >> the thread local. I think prabath did something similar to this , to >> restore missing headers. (with localTransport) >> >> All the above things should be only applied after localTransport check. >> >> just my thoughts, >> >> --Pradeep >> > > > > -- > *Amila Suriarachchi* > > Software Architect > WSO2 Inc. ; http://wso2.com > lean . enterprise . middleware > > phone : +94 71 3082805 > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
