Guillaume Nodet (JIRA | 6 May 08:41 2015
Picon

[jira] [Updated] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


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

Guillaume Nodet updated GERONIMO-6543:
--------------------------------------
    Attachment: GERONIMO-6543.patch

Possible patch ...

> Aries/Geronimo XA transaction recovery not working for heuristically completed transactions
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6543
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6543
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: Apache Karaf 2.3.0, JBoss Fuse 6.1-redhat-610379
>            Reporter: Jörn Gersdorf
>            Assignee: Guillaume Nodet
>         Attachments: GERONIMO-6543.patch
>
>
> We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
> The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):
> •	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
> •	{{GenericResourceManager}} is starting recovery
(Continue reading)

David Jencks (JIRA | 6 May 07:21 2015
Picon

[jira] [Commented] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


    [
https://issues.apache.org/jira/browse/GERONIMO-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529944#comment-14529944
] 

David Jencks commented on GERONIMO-6543:
----------------------------------------

Your analysis looks reasonable to me.  Is there any chance you would like to supply a patch?

> Aries/Geronimo XA transaction recovery not working for heuristically completed transactions
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6543
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6543
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: Apache Karaf 2.3.0, JBoss Fuse 6.1-redhat-610379
>            Reporter: Jörn Gersdorf
>            Assignee: Guillaume Nodet
>
> We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
> The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):
> •	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
> •	{{GenericResourceManager}} is starting recovery
> •	The {{NamedXAResourceFactory}} is enlisted
> •	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
(Continue reading)

Guillaume Nodet (JIRA | 5 May 17:49 2015
Picon

[jira] [Assigned] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


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

Guillaume Nodet reassigned GERONIMO-6543:
-----------------------------------------

    Assignee: Guillaume Nodet

> Aries/Geronimo XA transaction recovery not working for heuristically completed transactions
> -------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-6543
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-6543
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: transaction manager
>         Environment: Apache Karaf 2.3.0, JBoss Fuse 6.1-redhat-610379
>            Reporter: Jörn Gersdorf
>            Assignee: Guillaume Nodet
>
> We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
> The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):
> •	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
> •	{{GenericResourceManager}} is starting recovery
> •	The {{NamedXAResourceFactory}} is enlisted
> •	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
> •	Websphere MQ reports a XID which is to be recovered, Aries TxManager does not know about the XID so it
(Continue reading)

angosso | 5 May 02:55 2015
Picon

angosso web

ServletListener.java
request to /Angosso
org.apache.geronimo.samples.javaee6.web/ is the main body of the web
application
following.

+-WEB-INF

|_ web.xml

|_ geronimo-web.xml

|_ index.html

|_ header.html

|_ Angosso!!!-angosso.html
...
    <welcome-file-list>
        <welcome-file>index.html</welcome-file>
    </welcome-file-list>
    <servlet>
        <servlet-name>Angosso!!!</servlet-name>
        <servlet-class>Angosso!!!</servlet-class>
        <load-on-startup>Web</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>Angosso</servlet-name>
        <url-pattern>/Angosso!!!/*</url-pattern>
    </servlet-mapping>    
(Continue reading)

Brandon Watson (JIRA | 4 May 19:26 2015
Picon

[jira] [Created] (GERONIMO-6544) Using Static IP as address attribute for Network Listener

Brandon Watson created GERONIMO-6544:
----------------------------------------

             Summary: Using Static IP as address attribute for Network Listener
                 Key: GERONIMO-6544
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6544
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: connector, management
    Affects Versions: 2.2
         Environment: RedHat Linux 5.6 with two NIC's and two internal static IPs 
            Reporter: Brandon Watson

I have a RedHat 5.6 server that has two NIC's (eth0/192.168.1.1 and eth1/192.168.1.2). I want to have two
separate installs of geronimo using one specific NIC only.

Install1
/opt/apache/geronimo-2.2.0
HTTP-192.168.1.1:80
HTTPS-192.168.1.1:443
RMI-192.168.1.1:1099
AJP-192.168.1.1:8099
JMX-192.168.1.1:9999

Install2
/opt/apache2/geronimo-2.2.0
HTTP-192.168.1.2:80
HTTPS-192.168.1.2:443
RMI-192.168.1.2:1099
(Continue reading)

nito | 30 Apr 21:53 2015

Using Static IP as address attribute for Network Listener

I have a RedHat 5.6 server that has two NIC's (eth0/192.168.1.1 and
eth1/192.168.1.2). I want to have two separate installs of geronimo using
one specific NIC only. 

Install1
/opt/apache/geronimo-2.2.0
HTTP-192.168.1.1:80
HTTPS-192.168.1.1:443
RMI-192.168.1.1:1099
AJP-192.168.1.1:8099
JMX-192.168.1.1:9999

Install2
/opt/apache2/geronimo-2.2.0
HTTP-192.168.1.2:80
HTTPS-192.168.1.2:443
RMI-192.168.1.2:1099
AJP-192.168.1.1:8099
JMX-192.168.1.2:9999

<http://apache-geronimo.328035.n3.nabble.com/file/n3988990/ListeningPorts.jpg> 
I was able to get the RMI and JMX ports binded to the IP, via the
'ServerHostname=' attribute.

I started up a default instance and logged in the Geronimo Server Console.
Open Web Server > click 'Edit' on a BIO HTTP Connector > Add IP to
'*address' attribute > Save. Upon start up, I received the below error.

956 ERROR [GBeanInstanceState] Error while starting; GBean is now in the
FAILED state:
(Continue reading)

Jörn Gersdorf (JIRA | 29 Apr 13:30 2015
Picon

[jira] [Updated] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


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

Jörn Gersdorf updated GERONIMO-6543:
------------------------------------
    Description: 
We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):

•	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
•	{{GenericResourceManager}} is starting recovery
•	The {{NamedXAResourceFactory}} is enlisted
•	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
•	Websphere MQ reports a XID which is to be recovered, Aries TxManager does not know about the XID so it
tries to send xa_rollback to MQ
•	MQ already had the XID heuristically rolled back before, so it answers with {{XA_HEURRB (6)}}.
•	Geronimo logs the exception, but does not do anything about it

Since Geronimo does not do anything about the pending transaction, it stays pending withing Websphere MQ,
and the same error will occur upon next restart.

What´s missing here from our perspective is a call to xa_forget after receiving a XA_HEURB.

Btw, in {{org.apache.geronimo.transaction.manager.RollbackTask.run()}} {{XA_HEURRB}} seems to be
handled correctly by sending an xa_forget.

Stack trace below.

(Continue reading)

Jörn Gersdorf (JIRA | 29 Apr 13:24 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:
------------------------------------
    Patch Info: Patch Available

> 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 
>
(Continue reading)

Jörn Gersdorf (JIRA | 29 Apr 13:20 2015
Picon

[jira] [Updated] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


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

Jörn Gersdorf updated GERONIMO-6543:
------------------------------------
    Description: 
We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):

•	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
•	{{GenericResourceManager}} is starting recovery
•	The {{NamedXAResourceFactory}} is enlisted
•	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
•	Websphere MQ reports a XID which is to be recovered, Aries TxManager does not know about the XID so it
tries to send xa_rollback to MQ
•	MQ already had the XID heuristically rolled back before, so it answers with {{XA_HEURB (6)}}.
•	Geronimo logs the exception, but does not do anything about it

Since Geronimo does not do anything about the pending transaction, it stays pending withing Websphere MQ,
and the same error will occur upon next restart.

What´s missing here from our perspective is a call to xa_forget after receiving a XA_HEURB.

Stack trace below.

We´re using following bundles:

{noformat}
(Continue reading)

Jörn Gersdorf (JIRA | 29 Apr 13:19 2015
Picon

[jira] [Updated] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions


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

Jörn Gersdorf updated GERONIMO-6543:
------------------------------------
    Description: 
We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):

•	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
•	{{GenericResourceManager}} is starting recovery
•	The {{NamedXAResourceFactory}} is enlisted
•	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
•	Websphere MQ reports a XID which is to be recovered, Aries TxManager does not know about the XID so it
tries to send xa_rollback to MQ
•	MQ already had the XID heuristically rolled back before, so it answers with {{XA_HEURB (6)}}.
•	Geronimo logs the exception, but does not do anything about it

Since Geronimo does not do anything about the pending transaction, it stays pending withing Websphere MQ,
and the same error will occur upon next restart.

What´s missing here from our perspective is a call to xa_forget after receiving a XA_HEURB.

Stack trace below.

We´re using following bundles:

[ 281] [Active     ] [            ] [       ] [   50] mvn:org.apache.geronimo.components/geronimo-connector/3.1.1
(Continue reading)

Jörn Gersdorf (JIRA | 29 Apr 13:19 2015
Picon

[jira] [Created] (GERONIMO-6543) Aries/Geronimo XA transaction recovery not working for heuristically completed transactions

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

             Summary: Aries/Geronimo XA transaction recovery not working for heuristically completed transactions
                 Key: GERONIMO-6543
                 URL: https://issues.apache.org/jira/browse/GERONIMO-6543
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: transaction manager
         Environment: Apache Karaf 2.3.0, JBoss Fuse 6.1-redhat-610379
            Reporter: Jörn Gersdorf

We´re facing a problem with XA transaction recovery when a resource manager (like in our case Websphere
MQ) is reporting heuristically completed transactions. 
The flow goes like that (see {{org.apache.geronimo.transaction.manager.RecoveryImpl.recoverResourceManager(NamedXAResource)}}):

•	We´re starting JBoss Fuse, data/txlog/* has been deleted before start.
•	{{GenericResourceManager}} is starting recovery
•	The {{NamedXAResourceFactory}} is enlisted
•	Geronimo calls {{xa_recover(TM_STARTRSCAN | TMENDRSCAN)}} on the XA Resource (Websphere MQ)
•	Websphere MQ reports a XID which is to be recovered, Aries TxManager does not know about the XID so it
tries to send xa_rollback to MQ
•	MQ already had the XID heuristically rolled back before, so it answers with {{XA_HEURB (6)}}.
•	Geronimo logs the exception, but does not do anything about it

Since Geronimo does not do anything about the pending transaction, it stays pending withing Websphere MQ,
and the same error will occur upon next restart.

What´s missing here from our perspective is a call to xa_forget after receiving a XA_HEURB.
(Continue reading)


Gmane