HI Dmitriy, We are getting the same exception as mentioned in this Jira bug, I still need to check why it is happening. We have a go live date sometime around in june, thats why i was checking and wondering if this can be fixed by than.
Thanks, Ranjit On Tue, May 9, 2017 at 11:44 PM, Dmitriy Setrakyan <[email protected]> wrote: > It is not clear to me what this issue is. Ranjit, can you explain what > this is critical to you? > > On Tue, May 9, 2017 at 9:55 AM, Ranjit Sahu <[email protected]> wrote: > >> When will that be ? >> >> On Tue, 9 May 2017 at 10:10 PM, Andrey Gura <[email protected]> wrote: >> >>> No, it isn't fixed yet. Should be fixed in Ignite 2.1 I hope. >>> >>> On Tue, May 9, 2017 at 6:52 PM, Ranjit Sahu <[email protected]> >>> wrote: >>> > Hi Team, >>> > >>> > Is this issue fixed ? If yes on which version? IS there any work >>> around to >>> > avoid this ? >>> > >>> > Thanks, >>> > Ranjit >>> >> >
