[kepler-dev] [Bug 4894] New: One slave doesn't respond correctly when having concurrent requests.

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=4894

           Summary: One slave doesn't respond correctly when having
                    concurrent requests.
           Product: Kepler
           Version: 1.x dev
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: distributed execution
        AssignedTo: jianwu at sdsc.edu
        ReportedBy: jianwu at sdsc.edu
         QAContact: kepler-dev at kepler-project.org


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.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.