[JBoss JIRA] Created: (JBAS-5053) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
5:03 p.m.
Access to a TransactionManager from Database*LoginModule should only be required if
suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: JBAS-5053
URL: http://jira.jboss.com/jira/browse/JBAS-5053
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: JBossAS-5.0.0.Beta3
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 p.m.
New subject: [JBoss JIRA] Moved: (SECURITY-98) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
[ http://jira.jboss.com/jira/browse/SECURITY-98?page=all ]
Scott M Stark moved JBAS-5053 to SECURITY-98:
---------------------------------------------
Project: JBoss Security and Identity Management (was: JBoss Application
Server)
Key: SECURITY-98 (was: JBAS-5053)
Fix Version/s: 2.0.2-BETA
(was: JBossAS-5.0.0.Beta3)
Access to a TransactionManager from Database*LoginModule should only
be required if suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: SECURITY-98
URL: http://jira.jboss.com/jira/browse/SECURITY-98
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.0.2-BETA
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:07 p.m.
New subject: [JBoss JIRA] Commented: (SECURITY-98) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
[ http://jira.jboss.com/jira/browse/SECURITY-98?page=comments#action_12390764 ]
Anil Saldhana commented on SECURITY-98:
---------------------------------------
I think the code is already changed to do that in jbossx-2.0.2-alpha1
Something to do with the test setup in the particular AS setup.
Access to a TransactionManager from Database*LoginModule should only
be required if suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: SECURITY-98
URL: http://jira.jboss.com/jira/browse/SECURITY-98
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.0.2-BETA
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 p.m.
New subject: [JBoss JIRA] Commented: (SECURITY-98) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
[ http://jira.jboss.com/jira/browse/SECURITY-98?page=comments#action_12390766 ]
Scott M Stark commented on SECURITY-98:
---------------------------------------
There are two failures in XMLLoginModulesUnitTestCase & LoginModulesUnitTestCase
because of this:
https://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSu...
https://hudson.jboss.org/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-TestSu...
Access to a TransactionManager from Database*LoginModule should only
be required if suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: SECURITY-98
URL: http://jira.jboss.com/jira/browse/SECURITY-98
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Scott M Stark
Fix For: 2.0.2-BETA
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 p.m.
New subject: [JBoss JIRA] Closed: (SECURITY-98) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
[ http://jira.jboss.com/jira/browse/SECURITY-98?page=all ]
Anil Saldhana closed SECURITY-98.
---------------------------------
Resolution: Done
Done.
We missed Scott for a long time now. :)
Access to a TransactionManager from Database*LoginModule should only
be required if suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: SECURITY-98
URL: http://jira.jboss.com/jira/browse/SECURITY-98
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Anil Saldhana
Fix For: 2.0.2-BETA
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:21 p.m.
New subject: [JBoss JIRA] Assigned: (SECURITY-98) Access to a TransactionManager from Database*LoginModule should only be required if suspendResume is true
[ http://jira.jboss.com/jira/browse/SECURITY-98?page=all ]
Anil Saldhana reassigned SECURITY-98:
-------------------------------------
Assignee: Anil Saldhana (was: Scott M Stark)
Access to a TransactionManager from Database*LoginModule should only
be required if suspendResume is true
---------------------------------------------------------------------------------------------------------
Key: SECURITY-98
URL: http://jira.jboss.com/jira/browse/SECURITY-98
Project: JBoss Security and Identity Management
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Scott M Stark
Assigned To: Anil Saldhana
Fix For: 2.0.2-BETA
The suspendResume option to suspend/resume transactions during database operations should
control whether access to a TransactionManager is required. Currently if a
TransactionManager cannot be obtained an IllegalStateException is thrown regardless of the
suspendResume value.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6250
days inactive
6251
days old
5 comments
2 participants
participants (2)
-
Anil Saldhana (JIRA) -
Scott M Stark (JIRA)