[JBoss JIRA] (JBTM-1571) Put a message of the day on the blacktie chat room to redirect users to the jbossts room
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1571?page=com.atlassian.jira.plugin.... ]
Mark Little resolved JBTM-1571.
-------------------------------
Resolution: Done
Done
> Put a message of the day on the blacktie chat room to redirect users to the jbossts room
> ----------------------------------------------------------------------------------------
>
> Key: JBTM-1571
> URL: https://issues.jboss.org/browse/JBTM-1571
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Tom Jenkinson
> Assignee: Mark Little
> Fix For: 5.0.0.M3
>
>
> I don't have permissions Mark, I think you are the owner
> I tried:
> /msg ChanServ set #blacktie ENTRYMSG All blacktie discussions are being carried out over on #jbossts, please join us over there
> This suggests you are the owner:
> (05:30:01 PM) tomjenkinson: info #blacktie
> (05:30:02 PM) ChanServ: (notice) Information on #blacktie:
> (05:30:02 PM) ChanServ: (notice) Founder : nmcl
> (05:30:02 PM) ChanServ: (notice) Registered : Dec 22 10:31:29 2008 (4 years, 12 weeks, 5 days, 06:57:28 ago)
> (05:30:02 PM) ChanServ: (notice) Last used : Mar 15 15:29:07 2013 (5 days, 01:59:50 ago)
> (05:30:02 PM) ChanServ: (notice) Mode lock : +ntc-slk
> (05:30:02 PM) ChanServ: (notice) Flags : GUARD
> (05:30:02 PM) ChanServ: (notice) *** End of Info ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1571) Put a message of the day on the blacktie chat room to redirect users to the jbossts room
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1571?page=com.atlassian.jira.plugin.... ]
Mark Little closed JBTM-1571.
-----------------------------
> Put a message of the day on the blacktie chat room to redirect users to the jbossts room
> ----------------------------------------------------------------------------------------
>
> Key: JBTM-1571
> URL: https://issues.jboss.org/browse/JBTM-1571
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Tom Jenkinson
> Assignee: Mark Little
> Fix For: 5.0.0.M3
>
>
> I don't have permissions Mark, I think you are the owner
> I tried:
> /msg ChanServ set #blacktie ENTRYMSG All blacktie discussions are being carried out over on #jbossts, please join us over there
> This suggests you are the owner:
> (05:30:01 PM) tomjenkinson: info #blacktie
> (05:30:02 PM) ChanServ: (notice) Information on #blacktie:
> (05:30:02 PM) ChanServ: (notice) Founder : nmcl
> (05:30:02 PM) ChanServ: (notice) Registered : Dec 22 10:31:29 2008 (4 years, 12 weeks, 5 days, 06:57:28 ago)
> (05:30:02 PM) ChanServ: (notice) Last used : Mar 15 15:29:07 2013 (5 days, 01:59:50 ago)
> (05:30:02 PM) ChanServ: (notice) Mode lock : +ntc-slk
> (05:30:02 PM) ChanServ: (notice) Flags : GUARD
> (05:30:02 PM) ChanServ: (notice) *** End of Info ***
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1614) XA delist with TMFAIL flag
by Mark Little (JIRA)
[ https://issues.jboss.org/browse/JBTM-1614?page=com.atlassian.jira.plugin.... ]
Mark Little commented on JBTM-1614:
-----------------------------------
For completeness, I spoke with Stuart earlier today about this and it's definitely an issue and the fix should be fine.
> XA delist with TMFAIL flag
> --------------------------
>
> Key: JBTM-1614
> URL: https://issues.jboss.org/browse/JBTM-1614
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.2.3, 4.3.0.GA, 5.0.0.M2
> Environment: Fedora 18, Oracle 11 JDBC XAResource, JDK 1.5 & 1.6
> Reporter: Stuart Wheater
> Assignee: Tom Jenkinson
> Priority: Minor
>
> The scenario was as follows:
> enlist jms xaresource
> do some work
> delist jms xaresource
> enlist jdbc xaresource
> do some work which results in a failure(inserting NULL into a non null column for example)
> delist jdbc xaresource with TMFAIL flag.
> call tm.rollback()
> During rollback, an exception in XARerource.end() as follows: oracle.jdbc.xa.OracleXAException with error code=-3
> It appears that end is called, in rollback, although already been called in delist.
> I think the resolution is to change, endAssociation of narayana-full-5.0.0.M2src/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java from:
> if (_theTransaction.getXAResourceState(_theXAResource) == TxInfo.NOT_ASSOCIATED)
> to:
> int txInfo = _theTransaction.getXAResourceState(_theXAResource);
> if ((txInfo == TxInfo.NOT_ASSOCIATED) || (txInfo == TxInfo.FAILED))
> This fix works for JBossTS 4.2.3 and JBossTS 4.3, haven't been able test it Narayana 5.0.0.M2 yet, as Fedora 18 doesn't seem to be a supported build/test environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1614) XA delist with TMFAIL flag
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1614?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1614:
-------------------------------------
Hi Stuart,
It should build just fine on Fedora 18, if you get a chance you could then raise a pull request over here for master: https://github.com/jbosstm/narayana/
If you do decide to raise a pull request, please could I ask you to sign our CLA: https://cla.jboss.org
Tom
> XA delist with TMFAIL flag
> --------------------------
>
> Key: JBTM-1614
> URL: https://issues.jboss.org/browse/JBTM-1614
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JTA
> Affects Versions: 4.2.3, 4.3.0.GA, 5.0.0.M2
> Environment: Fedora 18, Oracle 11 JDBC XAResource, JDK 1.5 & 1.6
> Reporter: Stuart Wheater
> Assignee: Tom Jenkinson
> Priority: Minor
>
> The scenario was as follows:
> enlist jms xaresource
> do some work
> delist jms xaresource
> enlist jdbc xaresource
> do some work which results in a failure(inserting NULL into a non null column for example)
> delist jdbc xaresource with TMFAIL flag.
> call tm.rollback()
> During rollback, an exception in XARerource.end() as follows: oracle.jdbc.xa.OracleXAException with error code=-3
> It appears that end is called, in rollback, although already been called in delist.
> I think the resolution is to change, endAssociation of narayana-full-5.0.0.M2src/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java from:
> if (_theTransaction.getXAResourceState(_theXAResource) == TxInfo.NOT_ASSOCIATED)
> to:
> int txInfo = _theTransaction.getXAResourceState(_theXAResource);
> if ((txInfo == TxInfo.NOT_ASSOCIATED) || (txInfo == TxInfo.FAILED))
> This fix works for JBossTS 4.2.3 and JBossTS 4.3, haven't been able test it Narayana 5.0.0.M2 yet, as Fedora 18 doesn't seem to be a supported build/test environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1614) XA delist with TMFAIL flag
by Stuart Wheater (JIRA)
Stuart Wheater created JBTM-1614:
------------------------------------
Summary: XA delist with TMFAIL flag
Key: JBTM-1614
URL: https://issues.jboss.org/browse/JBTM-1614
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JTA
Affects Versions: 5.0.0.M2, 4.3.0.GA, 4.2.3
Environment: Fedora 18, Oracle 11 JDBC XAResource, JDK 1.5 & 1.6
Reporter: Stuart Wheater
Assignee: Tom Jenkinson
Priority: Minor
The scenario was as follows:
enlist jms xaresource
do some work
delist jms xaresource
enlist jdbc xaresource
do some work which results in a failure(inserting NULL into a non null column for example)
delist jdbc xaresource with TMFAIL flag.
call tm.rollback()
During rollback, an exception in XARerource.end() as follows: oracle.jdbc.xa.OracleXAException with error code=-3
It appears that end is called, in rollback, although already been called in delist.
I think the resolution is to change, endAssociation of narayana-full-5.0.0.M2src/ArjunaJTA/jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/XAResourceRecord.java from:
if (_theTransaction.getXAResourceState(_theXAResource) == TxInfo.NOT_ASSOCIATED)
to:
int txInfo = _theTransaction.getXAResourceState(_theXAResource);
if ((txInfo == TxInfo.NOT_ASSOCIATED) || (txInfo == TxInfo.FAILED))
This fix works for JBossTS 4.2.3 and JBossTS 4.3, haven't been able test it Narayana 5.0.0.M2 yet, as Fedora 18 doesn't seem to be a supported build/test environment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1613) Allow deserializer(s) to be plugged in during recovery of XAResourceRecord in JTS mode
by jaikiran pai (JIRA)
jaikiran pai created JBTM-1613:
----------------------------------
Summary: Allow deserializer(s) to be plugged in during recovery of XAResourceRecord in JTS mode
Key: JBTM-1613
URL: https://issues.jboss.org/browse/JBTM-1613
Project: JBoss Transaction Manager
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: JTS, Recovery
Affects Versions: 5.0.0.M2, 4.17.3
Reporter: jaikiran pai
Assignee: Tom Jenkinson
Unlike the JTA mode recovery where the XAResourceRecord allows SerializableXAResourceDeserializer(s) to deserialize the XAResource, the JTS mode XAResourceRecord has no such provision. This can lead to problems with deserialization of the XAResource since the transaction management code won't typically know the classloader to use while deserializing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months
[JBoss JIRA] (JBTM-1607) Hardcoded path in qa run.sh
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/JBTM-1607?page=com.atlassian.jira.plugin.... ]
Tom Jenkinson commented on JBTM-1607:
-------------------------------------
oops, that file shouldn't be checked in sorry, thanks for the heads up, I will remove it
> Hardcoded path in qa run.sh
> ---------------------------
>
> Key: JBTM-1607
> URL: https://issues.jboss.org/browse/JBTM-1607
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Configuration, Testing
> Affects Versions: 5.0.0.M2
> Reporter: Mark Little
> Assignee: Tom Jenkinson
>
> qa/run.sh
> #!/bin/bash
> sed -i TaskImpl.properties -e "s#^COMMAND_LINE_0=.*#COMMAND_LINE_0=java#"
> ant -Ddriver.url=file:///home/tom/narayana/dbdrivers get.drivers dist
> ant -f run-tests.xml ci-tests
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 5 months