This is probably due to there are some components/code-segments which are not re-factored the CarbonContext from jaggery webapp deployment side. Can we debug jaggery webapp deployer at #handleWebappDeployment method? Also what is the jaggery version here? Is that version is CC re-factored?
On Thu, Apr 10, 2014 at 12:11 PM, Anjana Fernando <anj...@wso2.com> wrote: > Hi, > > There is an issue reported for BAM here [1], in a scenario when tenant is > unloaded and loaded again, and when a Jaggery web app deployment happens, a > call to > "org.wso2.carbon.context.internal.CarbonContextDataHolder.getCurrentCarbonContextHolder()" > seems to be called recursively indefinitely, which causes a > StacKOverflowError. Can someone from the Carbon Core team please look into > it. > > [1] https://wso2.org/jira/browse/BAM-1513 > > Cheers, > Anjana. > -- > *Anjana Fernando* > Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Kishanthan Thangarajah* Senior Software Engineer, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
