Project

General

Profile

Bug #4894

One slave doesn't respond correctly when having concurrent requests.

Added by jianwu jianwu about 9 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
distributed execution
Target version:
Start date:
03/19/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4894

Description

When two running workflow are requesting concurrently to one slave, the executions will be twisted. Usually only one workflow can get correct results. I think it is because multiple client requests for the same slave only get the same object reference. And the attributes of the current SlaveController class created a stateful server. A discussion about it can be found at
http://www.coderanch.com/t/209597/Distributed-Java/java/Are-RMI-Server-objects-stateful.

A solution to is to refactor the current SlaveController so that its attributes are in a separate class and SlaveController is only a container.

History

#1 Updated by jianwu jianwu about 9 years ago

It is fixed at version 23459. SlaveController use a hashmap to contain the slave objects for different masters.

#2 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 4894

Also available in: Atom PDF