Bug 109054
Summary: | c.a.runtime.Script should verify DB transaction committed (Was: Unable to create a new content item) | ||
---|---|---|---|
Product: | [Retired] Red Hat Enterprise CMS | Reporter: | Daniel Berrangé <berrange> |
Component: | other | Assignee: | ccm-bugs-list |
Status: | CLOSED WONTFIX | QA Contact: | Jon Orris <jorris> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | nightly | CC: | richardl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-09-02 17:27:51 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 111508 |
Description
Daniel Berrangé
2003-11-04 17:53:06 UTC
Vadim, can you try to reproduce if possible? If it affects you, you should run into it in the course of fixing whatever you're working on. scott can't reproduce it with oracle/resin/ibm jdk1.3. I cannot reproduce it with oracle 9.2.0.1/resin/ibm jdk 1.3 and RH 7.3 Unable to reproduce. So far have attempted: RH 8 2.4.20-20.8 DBS: Postgres 7.3.3 Oracle 9.2.0.2 JVMS: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28) Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-20030618 (JIT enabled: jitc)) RHEL 2.1 2.4.9-e.16 DBS: Postgres 7.3.3 Oracle 9.2.0.2 JVMS: Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1) Classic VM (build 1.3.1, J2RE 1.3.1 IBM build cxia32131-20030329 (JIT enabled: jitc)) I can create an Article in the "content" content section. | $ java -version | java version "1.3.1_09" | Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_09-b03) | Java HotSpot(TM) Client VM (build 1.3.1_09-b03, mixed mode) | $ rpm -q postgresql-server | postgresql-server-7.2.3-5.80 Ok, I'm going to strip my server right back to just include core, cms & agenda (ie removing all the APLAWS apps), to try & isolate the problem. Don't bother spending more time trying to reproduce until I find more useful information. The problem turned out to be an Initializer which didn't explicitly commit the transaction after doing some DB work. THus when time came to create an item, the DB would block the SQL for creating the item, until the initializer threads' DB connection had committed. This isn't a problem when the running of the initializers was lazily started when the first request arrived, but I add 'load-on-startup' flag to the web.xml to get around some dodgy edge cases with lazy initialization. Recommendation: c.a.runtime.Startup should commit (or, abort, or throw Exception?) if an initializer fails to close a DB transaction before allowing control to return from init() events. retargeting for rc0 since no longer blocker Altering summary to relect the cause of the problem & downgrading severity. Closing old tickets |