Guillaume Nodet | 17 Apr 13:24 2015
Picon

[VOTE] Release Transaction Manager 3.1.2

I've uploaded a 3.1.2 release of the transaction manager component at
  https://repository.apache.org/content/repositories/orgapachegeronimo-1018

This fixes the following issues:
  * GERONIMO-6541: NPE during XAResource recovery with invalid Xids
  * GERONIMO-6372: RecoveryImpl completing in-progress transactions, XidFactoryImpl needs to be smarter with matching
  * GERONIMO-6373: Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
  
Please review and vote !

Cheers,
Guillaume Nodet

Jörn Gersdorf (JIRA | 15 Apr 15:04 2015
Picon

[jira] [Updated] (GERONIMO-6542) Logging of XIDs/TransactionIds is wrong


     [
https://issues.apache.org/jira/browse/GERONIMO-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Gersdorf updated GERONIMO-6542:
------------------------------------
    Description: 
Transaction IDs are logged in a wrong format by {{XidImpl.toString()}}.

We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.

However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid

{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 

will be logged as 

{{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.

This makes it hard to find and correlate transaction Xids in the log.

Reason lies in {{XidImpl.toString()}} and is twofold:

1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").

2. If {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").

Patch solving these issues is attached.

  was:
Transaction IDs are logged in a wrong format by XidImpl.toString().

We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.

However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid

{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 

will be logged as 

{{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.

This makes it hard to find and correlate transaction Xids in the log.

Reason lies in {{XidImpl.toString()}} and is twofold:

1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").

2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").

Patch solving these issues is attached.

> Logging of XIDs/TransactionIds is wrong
> ---------------------------------------
>
>                 Key: GERONIMO-6542
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6542
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: JBoss Fuse 6.1-610379, Apache Geronimo TransactionManager 3.3.1
>            Reporter: Jörn Gersdorf
>            Priority: Minor
>         Attachments: GERONIMO-6542__Fix_wrong_logging_of_transaction_ids.patch
>
>
> Transaction IDs are logged in a wrong format by {{XidImpl.toString()}}.
> We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.
> However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid 
>
{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 
> will be logged as 
> {{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.
> This makes it hard to find and correlate transaction Xids in the log.
> Reason lies in {{XidImpl.toString()}} and is twofold:
> 1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").
> 2. If {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged
as "ffffffab").
> Patch solving these issues is attached.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jörn Gersdorf (JIRA | 15 Apr 13:27 2015
Picon

[jira] [Updated] (GERONIMO-6542) Logging of XIDs/TransactionIds is wrong


     [
https://issues.apache.org/jira/browse/GERONIMO-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Gersdorf updated GERONIMO-6542:
------------------------------------
    Attachment: GERONIMO-6542__Fix_wrong_logging_of_transaction_ids.patch

> Logging of XIDs/TransactionIds is wrong
> ---------------------------------------
>
>                 Key: GERONIMO-6542
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6542
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: JBoss Fuse 6.1-610379, Apache Geronimo TransactionManager 3.3.1
>            Reporter: Jörn Gersdorf
>            Priority: Minor
>         Attachments: GERONIMO-6542__Fix_wrong_logging_of_transaction_ids.patch
>
>
> Transaction IDs are logged in a wrong format by XidImpl.toString().
> We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.
> However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid 
>
{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 
> will be logged as 
> {{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.
> This makes it hard to find and correlate transaction Xids in the log.
> Reason lies in {{XidImpl.toString()}} and is twofold:
> 1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").
> 2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").
> Patch solving these issues is attached.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jörn Gersdorf (JIRA | 15 Apr 13:23 2015
Picon

[jira] [Updated] (GERONIMO-6542) Logging of XIDs/TransactionIds is wrong


     [
https://issues.apache.org/jira/browse/GERONIMO-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Gersdorf updated GERONIMO-6542:
------------------------------------
    Description: 
Transaction IDs are logged in a wrong format by XidImpl.toString().

We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.

However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid

{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 

will be logged as 

{{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.

This makes it hard to find and correlate transaction Xids in the log.

Reason lies in {{XidImpl.toString()}} and is twofold:

1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").

2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").

Patch solving these issues is attached.

  was:
Transaction IDs are logged in a wrong format by XidImpl.toString().

We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.

However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid
{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}}
will be logged as {{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.

Reason lies in {{XidImpl.toString()}} and is twofold:

1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").

2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").

Patch solving these issues is attached.

> Logging of XIDs/TransactionIds is wrong
> ---------------------------------------
>
>                 Key: GERONIMO-6542
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6542
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: JBoss Fuse 6.1-610379, Apache Geronimo TransactionManager 3.3.1
>            Reporter: Jörn Gersdorf
>            Priority: Minor
>
> Transaction IDs are logged in a wrong format by XidImpl.toString().
> We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.
> However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid 
>
{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}} 
> will be logged as 
> {{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.
> This makes it hard to find and correlate transaction Xids in the log.
> Reason lies in {{XidImpl.toString()}} and is twofold:
> 1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").
> 2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").
> Patch solving these issues is attached.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jörn Gersdorf (JIRA | 15 Apr 13:22 2015
Picon

[jira] [Created] (GERONIMO-6542) Logging of XIDs/TransactionIds is wrong

Jörn Gersdorf created GERONIMO-6542:
---------------------------------------

             Summary: Logging of XIDs/TransactionIds is wrong
                 Key: GERONIMO-6542
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6542
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: transaction manager
         Environment: JBoss Fuse 6.1-610379, Apache Geronimo TransactionManager 3.3.1
            Reporter: Jörn Gersdorf
            Priority: Minor

Transaction IDs are logged in a wrong format by XidImpl.toString().

We are currently investigating issues in a distributed transaction setup involving WebsphereMQ and try
to correlate hanging transactions from MQ with transaction behaviour by Aries/Geronimo. Therefore we
set loglevel {{org.apache.geronimo.transaction.manager}} to {{TRACE}} which lets
{{WrapperNamedXAResource}} nicely log all XA activities.

However, transaction XIDs are logged in a wrong format. E. g. the transaction Xid
{{363720AB4C0100006F72672E6170616368652E61726965732E7472616E73616374696F6E00000000000000000000000000000000000000000000000000000000}}
will be logged as {{363720ffffffab4c1006f72672e6170616368652e61726965732e7472616e73616374696f6e0000000000000000000000000000}}.

Reason lies in {{XidImpl.toString()}} and is twofold:

1. {{Integer.toHexString(bgid[i])}} will append a single byte as just one character for byte values {{0
<= bgid[i] <= 15}} (e. g. "1" instead of "01").

2. {{bgid[i]}} is a signed byte value. Negative values will be logged wrongly (e. g. "ab" will be logged as "ffffffab").

Patch solving these issues is attached.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Guillaume Nodet | 15 Apr 10:02 2015
Picon

[DISCUSS] Release Transaction manager 3.1.2

I've fixed a small bug in the transaction manager this week, and there are one or two others fixed in the current trunk, so I was wondering about releasing this component.

Any objection ?

Cheers,
Guillaume Nodet

Guillaume Nodet (JIRA | 13 Apr 17:58 2015
Picon

[jira] [Resolved] (GERONIMO-6541) NPE during XAResource recovery with invalid Xids


     [
https://issues.apache.org/jira/browse/GERONIMO-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet resolved GERONIMO-6541.
---------------------------------------
    Resolution: Fixed

http://svn.apache.org/viewvc?view=revision&revision=1673231

> NPE during XAResource recovery with invalid Xids
> ------------------------------------------------
>
>                 Key: GERONIMO-6541
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6541
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>
> In rare cases, the Oracle database may return Xid with null global transaction id.  While those are clearly
invalid, it can cause NPE in the transaction manager during the recovery phase, causing the application
to not restart properly.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Guillaume Nodet (JIRA | 13 Apr 17:57 2015
Picon

[jira] [Updated] (GERONIMO-6541) NPE during XAResource recovery with invalid Xids


     [
https://issues.apache.org/jira/browse/GERONIMO-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated GERONIMO-6541:
--------------------------------------
    Summary: NPE during XAResource recovery with invalid Xids  (was: NPE during XAResource recovery)

> NPE during XAResource recovery with invalid Xids
> ------------------------------------------------
>
>                 Key: GERONIMO-6541
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6541
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>            Reporter: Guillaume Nodet
>            Assignee: Guillaume Nodet
>
> In rare cases, the Oracle database may return Xid with null global transaction id.  While those are clearly
invalid, it can cause NPE in the transaction manager during the recovery phase, causing the application
to not restart properly.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Guillaume Nodet (JIRA | 13 Apr 17:41 2015
Picon

[jira] [Created] (GERONIMO-6541) NPE during XAResource recovery

Guillaume Nodet created GERONIMO-6541:
-----------------------------------------

             Summary: NPE during XAResource recovery
                 Key: GERONIMO-6541
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6541
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: transaction manager
            Reporter: Guillaume Nodet
            Assignee: Guillaume Nodet

In rare cases, the Oracle database may return Xid with null global transaction id.  While those are clearly
invalid, it can cause NPE in the transaction manager during the recovery phase, causing the application
to not restart properly.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Romain Manni-Bucau | 7 Apr 23:15 2015
Picon

spec jar and sources

Hi guys,

surely stupid when known but I guess I could loose a lot of time before finding: how can I deply sources and javadoc jars of a snapshot? I always get ianal plugin failure saying license/notice is not included.

I use: mvn source:jar javadoc:jar deploy

Romain Manni-Bucau
<at> rmannibucau |  Blog | Github | LinkedIn | Tomitriber
Alan D. Cabrera | 4 Apr 20:36 2015

Board report time 2015-04

Here's my initial draft:


If I missed something please let me know or go ahead and update the page directly.


Regards,
Alan


Gmane