[
https://issues.jboss.org/browse/TEIID-2137?page=com.atlassian.jira.plugin...
]
Andriy Rokhmanov commented on TEIID-2137:
-----------------------------------------
Yes, it seems the occasional NPE caused by this statement in my translator:
public void close() {
this.executionContext = null;
}
When I remove the assignment to null I see no more NPE. I tested with 30 parallel
executions.
I think this approach was taken by me from
TestWaitUntilDataNotFoundWithExecutionReuse.java test case, attached to
https://issues.jboss.org/browse/TEIID-2130 . I was under impression that the
executionContext reset to null in close(), dispose() and cancel() methods is needed as
part of fix in TEIID-2103.
If this is expected - feel free to close this defect please.
NPE in ExecutionContext.getCommandContext()
-------------------------------------------
Key: TEIID-2137
URL:
https://issues.jboss.org/browse/TEIID-2137
Project: Teiid
Issue Type: Bug
Affects Versions: 8.1
Environment: Java(TM) SE Runtime Environment (build 1.7.0_05-b05) , Windows 7,
Teiid 8.1.CR1
Reporter: Andriy Rokhmanov
Assignee: Steven Hawkins
Attachments: server.log.txt
I start 10 simultaneous continuous executions against my custom ResultSetExecution
translator.
This piece of code causes NPE once per several seconds:
public void execute() throws TranslatorException {
...
CommandContext ctx = executionContext.getCommandContext();
...
}
Exception dump from server.log attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira