Bug 748863 - Unexpected numbers of the received messages with xa recovery
Summary: Unexpected numbers of the received messages with xa recovery
Keywords:
Status: CLOSED DUPLICATE of bug 733383
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-java
Version: 2.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 2.0.4
: ---
Assignee: messaging-bugs
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On: 752946
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 14:03 UTC by Pavel Slavicek
Modified: 2011-11-17 13:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-17 13:13:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Part of the app server log - arjuna at debug level (99.15 KB, text/x-log)
2011-10-25 14:03 UTC, Pavel Slavicek
no flags Details

Description Pavel Slavicek 2011-10-25 14:03:26 UTC
Created attachment 530100 [details]
Part of the app server log - arjuna at debug level

Hi Weston,
I am executing automated test for xa recovery but I am hitting issue because I am receiving more messages than it was expected. Could you take a look to the configuration and implementation, please? It seems that I have missed something in my configuration, implementation etc. Thank you. 

Description of problem:
# Scenario corresponds with test cases “9.3.4 MDB deliveries message in transaction (EAP server is killed)"
# Client sends 5000 messages into the input queue
# MDB consumes messages from input queue and re-sends them into output queue and server is killed several times during this process and restarted
# Client reads more than 5000 message from the output queue (5028, …). Application server's log contains WARNs: Arjuna is not able to XAResource.
# Implementation contains two tests 1) without killing and restarting app server and 2) with killing and restarting server. 1) is fine without any issues, 2) receives more messages that it was expected. For this reason it seems that mechanism for re-sending messages used in test should work fine.

Server log:
2011-10-25 07:57:06,134 WARN  [com.arjuna.ats.jta.logging.loggerI18N] (Thread-19) [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 27, 25, 49459749485397515258565454100585210197549751971015898505397494853975152585654541005852101975497519710158985056 >

Part of the app server's og at DEBUG level for arjuna.com will be attached.

jbossts-properties.xml:
https://svn.devel.redhat.com/repos/jboss-qa/mrg/qpid-java-jca/jbossts-properties.xml
…
<property name="com.arjuna.ats.jta.recovery.XAResourceRecovery.QPID1"            value="org.jboss.mrg.jca.tm.QpidXAResourceRecovery;amqp://guest:guest@/test?brokerlist=&apos;tcp://mrg01.mw.lab.eng.bos.redhat.com:5682&apos;"/>
<property name="com.arjuna.ats.jta.xaRecoveryNode" value="1"/>
…

jbossts-properties.xml:
https://svn.devel.redhat.com/repos/jboss-qa/mrg/qpid-java-jca/qpid-jca-ds.xml
Port 5672 is replaced before test with new value 5682.

MDB:
https://svn.devel.redhat.com/repos/jboss-qa/mrg/tests/xarecovery/mdb-ejb/src/main/java/org/jboss/test/mdb/MRGJCAMessageBean.java
…
    @Resource(mappedName = "java:/QpidJMSXA")
    private ConnectionFactory connectionFactory;
…

MRG server:
New instance for each test execution (with clean data dir), mrg01.mw.lab.eng.bos.redhat.com:5682.

Comment 1 Weston M. Price 2011-11-17 13:13:18 UTC

*** This bug has been marked as a duplicate of bug 733383 ***


Note You need to log in before you can comment on or make changes to this bug.