You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2008/12/10 08:18:05 UTC
[jira] Closed: (AMQ-2028) ActiveMQSessionExecutor.taskRunner usage
is very non-thread-safe
[ https://issues.apache.org/activemq/browse/AMQ-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed AMQ-2028.
-----------------------------
Resolution: Fixed
Fixed in rev 725020.
> ActiveMQSessionExecutor.taskRunner usage is very non-thread-safe
> ----------------------------------------------------------------
>
> Key: AMQ-2028
> URL: https://issues.apache.org/activemq/browse/AMQ-2028
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 5.3.0
>
>
> cmon guys,
> if (taskRunnerCreated.compareAndSet(false, true)) {
> if (taskRunner == null) {
> taskRunner = session.connection.getSessionTaskRunner().createTaskRunner(this,
> "ActiveMQ Session: " + session.getSessionId());
> }
> }
> taskRunner.wakeup();
> is not anywhere close to thread safe.
> I'm seeing JmsClientAckTest and JmsRedeliveredTest failing due to this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.