You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Aleksandrov (JIRA)" <ji...@apache.org> on 2018/10/17 13:53:00 UTC

[jira] [Created] (IGNITE-9914) SubjectId for TaskEvents is incorrect for remote clients

Andrey Aleksandrov created IGNITE-9914:
------------------------------------------

             Summary: SubjectId for TaskEvents is incorrect for remote clients
                 Key: IGNITE-9914
                 URL: https://issues.apache.org/jira/browse/IGNITE-9914
             Project: Ignite
          Issue Type: Bug
          Components: clients
    Affects Versions: 2.6
            Reporter: Andrey Aleksandrov
            Assignee: Andrey Aleksandrov
             Fix For: 2.8


In case if the task was initialized from the remote client as web console then taskEvent.subjectId() will return the incorrect value. 

It will contain the subject id for the node where this task was deployed.

Ignite already have the thread local store for subject id but looks like we have a problem in GridTaskProcessor:

UUID subjId = getThreadContext(TC_SUBJ_ID);

But it always is null because of the correct value for TC_SUBJ_ID stored in 

Map<GridTaskThreadContextKey, Object> map = thCtx.get();

So it should be changed to 

UUID subjId = (UUID)map.get(TC_SUBJ_ID);



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)