Bug 900289 (JBPAPP6-1490)
| Summary: | Domain management API does not expose JTS orphans from the transaction object store | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Ivo Studensky <istudens> |
| Component: | Transaction Manager | Assignee: | Ivo Studensky <istudens> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ondrej Chaloupka <ochaloup> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.4.0 | CC: | hhovsepy, istudens, kkhan, mmusgrov, ochaloup, smaestri, tom.jenkinson |
| Target Milestone: | DR1 | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBPAPP6-1490 | ||
| Whiteboard: | eap601candidate | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The transaction subsystem contained in JBoss EAP 6 maintains a log of pending transactions. This log is exposed to the console user.
In some circumstances a resource has a log of an in-doubt transaction branch for which there is no corresponding top level transaction log (but on disk there is a participant log). Such logs are called "orphans" and by default these were not exposed in previous versions.
As a result, if the transaction subsystem was configured to use JTS then these orphan records were not automatically removed resulting in a leak of available storage space.
In this release, the console user can override the default by setting the transaction subsystem property `expose-all-logs` to `true`. Then the console user has the option to manually delete these logs, preventing the leak.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 12:42:04 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: | |||
| Bug Depends On: | 1028032 | ||
| Bug Blocks: | |||
|
Description
Ivo Studensky
2012-04-24 12:35:06 UTC
Link: Added: This issue is related to JBQA-6260 The Object Store tooling creates MBeans for transaction records and then creates MBeans to represent their participants. Since an orphan doesn't have a corresponding transaction MBeans are not created for them. So I would need to add code to JBossTS to expose orphans as MBeans and then update the AS management subsystem to add a new child resource for exposing them. ie we need another release of JBossTS to get this fixed. Labels: Added: eap6_need_triage Labels: Removed: eap6_need_triage Added: eap601candidate Link: Added: This issue is a dependency of JBTM-1148 Link: Added: This issue depends AS7-4331 Link: Added: This issue is a dependency of AS7-4331 Docs QE Status: Removed: NEW Reassingning to Heiko because the only dependency left is assigned to him To expose all the transaction logs we need an extra attribute on the transactions subsystem in the AS management model. The subsystem manages transaction logs via MBeans. So something like
String EXPOSEALLLOGS = "expose-all-logs";
...
ObjectName on = new ObjectName("jboss.jta:type=ObjectStore")
MBeanServer mbs = TransactionExtension.getMBeanServer(context)
and then use the mbean server to update the MBean atribute
mbs.setAttribute(on, new Attribute("ExposeAllRecordsAsMBean", Boolean.TRUE)
This operation will now expose all transaction logs.
Hi Ivo, I noticed your change has been merged to WF, do you intend to perform the backport for this too? Thanks very much, Tom Yes, I am going to port this back. Now setting "expose-all-logs" to true allows to show orphaned JTS logs. Verified on jboss-eap-6.4.0.DR2 |