Update JBoss Serialization
--------------------------
Key: JBAS-3665
URL: http://jira.jboss.com/jira/browse/JBAS-3665
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Clebert Suconic
Priority: Critical
Fix For: JBossAS-4.0.5.GA
There is a bug parsing Big Strings (between 30k and 64k bytes) on JBoss Serialization that I would like to have it fixed before a new release.
--
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
[ http://jira.jboss.com/jira/browse/JBTM-87?page=all ]
Kevin Conner resolved JBTM-87.
------------------------------
Fix Version/s: 4.2.2
Resolution: Done
> Put back LRCO JTA interface
> ---------------------------
>
> Key: JBTM-87
> URL: http://jira.jboss.com/jira/browse/JBTM-87
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTA Implementation
> Affects Versions: 4.2
> Reporter: Mark Little
> Assigned To: Kevin Conner
> Priority: Minor
> Fix For: 4.2.2
>
>
> The last resource commit optimisation for JTA is missing the JTA marker interface, which was removed during the move from Arjuna to JBoss. We should be able to add this back now.
--
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
[ http://jira.jboss.com/jira/browse/JBTM-87?page=comments#action_12343936 ]
Kevin Conner commented on JBTM-87:
----------------------------------
The LRCO functionality has been added back in revision 6409
> Put back LRCO JTA interface
> ---------------------------
>
> Key: JBTM-87
> URL: http://jira.jboss.com/jira/browse/JBTM-87
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: JTA Implementation
> Affects Versions: 4.2
> Reporter: Mark Little
> Assigned To: Kevin Conner
> Priority: Minor
>
> The last resource commit optimisation for JTA is missing the JTA marker interface, which was removed during the move from Arjuna to JBoss. We should be able to add this back now.
--
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
[ http://jira.jboss.com/jira/browse/JBTM-67?page=all ]
Kevin Conner closed JBTM-67.
----------------------------
> The installation notes incorrectly specify the initialisation of both TS interceptors.
> --------------------------------------------------------------------------------------
>
> Key: JBTM-67
> URL: http://jira.jboss.com/jira/browse/JBTM-67
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Documentation
> Affects Versions: 4.2
> Reporter: Kevin Conner
> Assigned To: Kevin Conner
> Fix For: 4.2.1
>
> Time Spent: 1 day, 6 hours
> Remaining Estimate: 0 minutes
>
> The installation notes incorrectly specify the initialisation of both the standard context interceptor and the interposition interceptor. These interceptors are mutually exclusive.
> The symptom exhibited by this problem is OutOfMemoryErrors being logged to the standard output. This occurs because the interposition interceptor incorrectly interprets part of a text string as a length (approx 1GB).
--
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
[ http://jira.jboss.com/jira/browse/JBTM-83?page=all ]
Kevin Conner closed JBTM-83.
----------------------------
> Multiple recovery threads get initialised when embedded in the application server
> ---------------------------------------------------------------------------------
>
> Key: JBTM-83
> URL: http://jira.jboss.com/jira/browse/JBTM-83
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA Implementation, JTS Implementation
> Affects Versions: 4.2
> Reporter: Kevin Conner
> Assigned To: Kevin Conner
> Fix For: 4.2.1
>
> Attachments: jbossjta-integration.jar, jbossjts-integration.jar
>
> Time Spent: 1 hour
> Remaining Estimate: 0 minutes
>
> The TransactionManagerServiceMBean implementations initialise the recovery manager directly instead of using the singleton. The result of this is that the recovery manager is initialised twice, when other code calls the singleton, and two recovery threads are subsequently created.
--
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
[ http://jira.jboss.com/jira/browse/JBTM-78?page=all ]
Kevin Conner closed JBTM-78.
----------------------------
> JTA installation does not include the XARecoveryModule
> ------------------------------------------------------
>
> Key: JBTM-78
> URL: http://jira.jboss.com/jira/browse/JBTM-78
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA Implementation
> Affects Versions: 4.2
> Reporter: Kevin Conner
> Assigned To: Kevin Conner
> Fix For: 4.2.1
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> The properrties file included in the JTA distribution does not include the XARecoveryModule
--
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
[ http://jira.jboss.com/jira/browse/JBTM-84?page=all ]
Kevin Conner closed JBTM-84.
----------------------------
> The Xid implementation should implement the hashCode and equals methods from Object
> -----------------------------------------------------------------------------------
>
> Key: JBTM-84
> URL: http://jira.jboss.com/jira/browse/JBTM-84
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.2
> Reporter: Kevin Conner
> Assigned To: Kevin Conner
> Fix For: 4.2.2
>
>
> XidImpl does not implement the equals and hashCode methods. This prevents Xid being used in hash maps/sets.
--
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
The transaction manager implementation in JNDI should implement the org.jboss.tm.TransactionTimeoutConfiguration interface
--------------------------------------------------------------------------------------------------------------------------
Key: JBTM-125
URL: http://jira.jboss.com/jira/browse/JBTM-125
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.2
The jta/jts transaction manager delegates should provide an implementation of the TransactionTimeoutConfiguration interface.
--
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
atsintegration must have its own logging
----------------------------------------
Key: JBTM-124
URL: http://jira.jboss.com/jira/browse/JBTM-124
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.2.1
Environment: The atsintegration contains internationalised logging but does not have a logging class. The associated resource file is not generated by the build.
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.2
--
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
JTS XATerminator references arjunacore classes
----------------------------------------------
Key: JBTM-126
URL: http://jira.jboss.com/jira/browse/JBTM-126
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTS Implementation
Affects Versions: 4.2.1
Environment: The JTS XATerminator references the classes in arjunacore instead of jts.
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2.2
--
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