Bug 867657
| Summary: | [Maven Client] org.apache.maven.lifecycle.LifecycleExecutionException when pushing | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Zanata | Reporter: | Ding-Yi Chen <dchen> | ||||
| Component: | Component-Maven | Assignee: | Carlos Munoz <camunoz> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ding-Yi Chen <dchen> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | development | CC: | zanata-bugs | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 2.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 1.8.0-SNAPSHOT (20121022-1434) | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-11-07 06:18:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ding-Yi Chen
2012-10-18 00:18:35 UTC
This is a problem with the way Seam runs asynchronous processes. The asynchronous process doesn't inherit the contexts from the invocation that started it. Hence, no session information is carried forward and the push fails as the security checks for some of the activities might fail. Added a way to specify the identity with which to run the async process (so far only works with the REST API). See: https://github.com/zanata/zanata/commit/2c5ef50c198e43b4db9ae89cbdb2f82c8d3cb15d Tested with Zanata version 1.8.0-SNAPSHOT (20121018-1429). The push still failed when pushing from different terminal with translation. The error is not always reproduceable, but frequent enough. Step to reproduce 1. Prepare project freeciv: a. Create project freeciv b. Create version master c. wget http://www.cazfi.net/freeciv/translations/S2_5/freeciv.pot d. wget http://www.cazfi.net/freeciv/translations/S2_5/zh-CN.po.bz2 bunzip2 zh-CN.po.bz2 mkdir zh-Hans mv zh-CN.po zh-Hans/freeciv.po e. wget http://www.cazfi.net/freeciv/translations/S2_5/zh-TW.po.bz2 bunzip2 zh-TW.po.bz2 mkdir zh-Hant mv zh-TW.po zh-Hant/freeciv.po f. Editing zanata.xml and pom.xml accordingly 2. Open 2 terminal 3. On terminal 1, run: mvn -B -e zanata:push -Dzanata.pushType=both 4. No need to wait for step 3 finish, on terminal 2, run: mvn -B -e zanata:push -Dzanata.pushType=both Actual: [ERROR] Failed to execute goal org.zanata:zanata-maven-plugin:1.8.0-SNAPSHOT:push (default-cli) on project null: Zanata mojo exception: Failed while pushing document translations: [] -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.zanata:zanata-maven-plugin:1.8.0-SNAPSHOT:push (default-cli) on project null: Zanata mojo exception Expected: Push without error Reassigned. It seems large documents (in this case translated documents) were still generating transaction timeouts on the server. The server will now break up client translation pushes into several transactions to avoid this problem. This means that errors or client cancellations will not rollback all changes to that point. It also means that subsequent pushes of the same document will not repeat any work already done. See: https://github.com/zanata/zanata/commit/c11c40ccc4bd0c15834ab1a93a9a52c326ebf680 VERIFIED with Zanata version 1.8.0-SNAPSHOT (20121022-1434) [INFO] client API version: 1.8.0-SNAPSHOT, server API version: 1.8.0-SNAPSHOT Fix released in Zanata 2.0. |