Bug 959875
| Summary: | ISPN 5.2.6.Final: Failed to passivate (unloaded) session: IllegalArgumentException: Cannot create a transactional context without a valid Transaction instance. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jitka Kozana <jkudrnac> | ||||
| Component: | Clustering | Assignee: | Paul Ferraro <paul.ferraro> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 6.1.0 | CC: | brian.stansberry, dandread, jdoyle, jkudrnac, lthon, mmarkus, myarboro, paul.ferraro, rjanik, rsvoboda, ttarrant | ||||
| Target Milestone: | ER7 | Keywords: | Regression | ||||
| Target Release: | EAP 6.1.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-07-23 18:35:06 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: | |||||||
| Bug Blocks: | 900549 | ||||||
| Attachments: |
|
||||||
|
Description
Jitka Kozana
2013-05-06 07:32:53 UTC
Setting blocker flag to "?", since this looks like fallout from: https://github.com/jbossas/jboss-eap/commit/4db033959d89b46990b54f62b938e7b7158d57e9 Though, honestly, I don't immediately know why this would be happening, since the lock is performed within the context of a tx (via BatchCacheInvoker). The TransactionManager that looks up the transaction associated with the current thread doesn't find any transaction associated with the current thread. Two possible causes for this are: the transaction wasn't started (or was completed by the time the lock() is invoked) or the TransactionManager the cache is using is different than the one configured for the cache. I've created: https://issues.jboss.org/browse/ISPN-3077 JIRA also contains a workaround for the problem. What are our prospects for getting this fix or workaround into the release. Looks like either one requires a code change. I've implemented a workaround for ISPN-3077: https://github.com/jbossas/jboss-eap/pull/140 So then, we are taking Paul's fix XOR Mircea's ISPN-3077 fix? The ISPN-3077 fix would need to be ported to the 5.2.x branch, released as 5.2.7, and the component upgraded and tested in EAP. If this is possible within the remaining time, great - but Dimitris is right, we don't need/want both fixes, only one or the other. I think we should take Paul's workaround given the time pressure. Have we already missed our window for the build? We can take the workaround in the github PR for ER7. @Paul or @Rado, once the pull 140 is merged, can I have a jar to test with, please? Thanks! Should we proceed with the merge, anyway? The test failure on lightning looks transient to me. Verified. |