Bug 4968 - [devbranch] bitbake server must handle read-only requests on a separate thread
Summary: [devbranch] bitbake server must handle read-only requests on a separate thread
Status: CLOSED INVALID
Alias: None
Product: Toaster
Classification: Build System, Metadata & Runtime
Component: toaster (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided critical
Target Milestone: ---
Assignee: Alexandru Damian
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-07-31 12:44 UTC by Alexandru Damian
Modified: 2014-01-21 15:57 UTC (History)
0 users

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Damian 2013-07-31 12:44:36 UTC 
Currently, the XMLRPC server executes web commands and idle functions sequentially, and will not process a request while it is running a command.

This stalls all read-only requests until an idle functions, such as buildTarget, are done, and will create a stalling problem, and a possible deadlock, which severely affects the performance and resolution of the webhob observer interface.

It is expected for bitbake to not block readonly commands on the running of async commands.
Comment 1 Alexandru Damian 2014-01-21 15:57:04 UTC 
This requirement is no longer applicable.