i found this in logs, can be bug ?
I saw this problem recently on a plugin that used wrongly Env.setCtx - the comment on that method says:
Replace the contents of the current session/process context.
Don't use this to setup a new session/process context, use ServerContext.setCurrentInstance instead.
Also, see the comment here:
A background process, can define its own context but that should be through the ServerContext.setCurrentInstance(Properties) method, not by passing a plain Properties object around. After the setCurrentInstance call, Env.getCtx() should be use after that.
thanks. for the suggestion.