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.
On Tue, May 9, 2017 at 11:44 PM, Dmitriy Setrakyan <[hidden email]> wrote:
It is not clear to me what this issue is. Ranjit, can you explain what this is critical to you?