Build failed in Jenkins: ActiveMQ-Java7 ยป ActiveMQ :: MQTT Protocol #142

2013-02-17 Thread Apache Jenkins Server
See 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/142/

--
[INFO] Downloading: 
http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom
[WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910

[INFO] 
[INFO] Building ActiveMQ :: MQTT Protocol 5.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-mqtt ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-mqtt ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-mqtt ---
[INFO] [WARNING] No proto files found in directory: 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/src/main/proto

[INFO] --- activemq-protobuf:1.1:compile (default) @ activemq-mqtt ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ activemq-mqtt 
---
[INFO] [debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.

[INFO] Copying 5 resources
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-mqtt ---
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [INFO] Compiling 16 source files to 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/classes

[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-mqtt ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] [INFO] Copying 3 resources
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
activemq-mqtt ---
[INFO] [INFO] Compiling 6 source files to 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/test-classes

[INFO] --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ 
activemq-mqtt ---
[INFO] [INFO] Surefire report directory: 
https://builds.apache.org/job/ActiveMQ-Java7/org.apache.activemq$activemq-mqtt/ws/target/surefire-reports

---
 T E S T S
---

---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.10:test (default-test) @ activemq-mqtt ---
Running org.apache.activemq.transport.mqtt.MQTTSSLTest
Running org.apache.activemq.transport.mqtt.MQTTTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 389.512 sec
Running org.apache.activemq.transport.mqtt.MTQQNioTest
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 391.34 sec

Results :

Tests run: 27, Failures: 0, Errors: 0, Skipped: 0



Build failed in Jenkins: ActiveMQ-Java7 #142

2013-02-17 Thread Apache Jenkins Server
See https://builds.apache.org/job/ActiveMQ-Java7/142/changes

Changes:

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4000 Added test for 
multiple durable consumers across the network, per Gary's comments

--
[...truncated 7012 lines...]
[INFO] [INFO] Installing 
https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-tooling/activemq-maven-plugin/target/activemq-maven-plugin-5.9-SNAPSHOT.jar
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-SNAPSHOT.jar

[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
activemq-maven-plugin ---
[INFO] Installing 
https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-tooling/activemq-maven-plugin/pom.xml
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/tooling/activemq-maven-plugin/5.9-SNAPSHOT/activemq-maven-plugin-5.9-SNAPSHOT.pom
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ 
activemq-maven-plugin ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-maven-plugin ---
Feb 17, 2013 1:25:03 PM hudson.maven.ExecutedMojo init
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-maven-plugin 
---
[INFO] META-INF already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] Building jar: 
https://builds.apache.org/job/ActiveMQ-Java7/ws/activemq-tooling/activemq-maven-plugin/target/activemq-maven-plugin-5.9-SNAPSHOT-sources.jar
[INFO] META-INF already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Demo
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Console
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Assembly
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ActiveMQ .. SUCCESS [25.646s]
[INFO] ActiveMQ :: Openwire Generator  SUCCESS [7.935s]
[INFO] ActiveMQ :: Client  SUCCESS [45.093s]
[INFO] ActiveMQ :: Openwire Legacy Support ... SUCCESS [6.985s]
[INFO] ActiveMQ :: JAAS .. SUCCESS [1:07.806s]
[INFO] ActiveMQ :: Broker  SUCCESS [1:09.379s]
[INFO] ActiveMQ :: KahaDB Store .. SUCCESS [4:11.889s]
[INFO] ActiveMQ :: STOMP Protocol  SUCCESS [49:46.711s]
[INFO] ActiveMQ :: MQTT Protocol . FAILURE [18:07.130s]
[INFO] ActiveMQ :: JDBC Store  SUCCESS [3.672s]
[INFO] ActiveMQ :: LevelDB Store . SUCCESS [2:29.842s]
[INFO] ActiveMQ :: RA  SUCCESS [2:46.188s]
[INFO] ActiveMQ :: Pool .. SUCCESS [46.422s]
[INFO] ActiveMQ :: Spring  SKIPPED
[INFO] ActiveMQ :: AMQP .. SKIPPED
[INFO] ActiveMQ 

Build failed in Jenkins: ActiveMQ #1226

2013-02-17 Thread Apache Jenkins Server
See https://builds.apache.org/job/ActiveMQ/1226/changes

Changes:

[ceposta] Fix for https://issues.apache.org/jira/browse/AMQ-4000 Added test for 
multiple durable consumers across the network, per Gary's comments

--
[...truncated 5530 lines...]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ activemq-broker ---
[INFO] Building jar: 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
activemq-broker ---
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ activemq-broker ---
[INFO] Building jar: 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT-tests.jar
[INFO] [INFO] Checking legal files in: activemq-broker-5.9-SNAPSHOT.jar
[INFO] Checking legal files in: activemq-broker-5.9-SNAPSHOT-tests.jar

[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ 
activemq-broker ---
[INFO] Installing 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT.jar
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.jar
[INFO] [INFO] Installing 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/pom.xml to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT.pom
[INFO] Installing 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT-tests.jar
 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-broker/5.9-SNAPSHOT/activemq-broker-5.9-SNAPSHOT-tests.jar

[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
activemq-broker ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-broker ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-broker ---
Feb 17, 2013 1:33:01 PM hudson.maven.ExecutedMojo init
WARNING: Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.1.2:jar (default-cli) @ activemq-broker ---
[INFO] META-INF already added, skipping
[INFO] META-INF already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] Building jar: 
https://builds.apache.org/job/ActiveMQ/ws/activemq-broker/target/activemq-broker-5.9-SNAPSHOT-sources.jar
[INFO] META-INF already added, skipping
[INFO] META-INF already added, skipping
[INFO] META-INF/NOTICE already added, skipping
[INFO] META-INF/LICENSE already added, skipping
[INFO] META-INF/DEPENDENCIES already added, skipping
[INFO] Downloading: 
http://repo.maven.apache.org/maven2/org/eclipse/jetty/maven-jetty-plugin/7.6.7.v20120910/maven-jetty-plugin-7.6.7.v20120910.pom
[WARNING] The POM for org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910: Plugin 
org.eclipse.jetty:maven-jetty-plugin:7.6.7.v20120910 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.eclipse.jetty:maven-jetty-plugin:jar:7.6.7.v20120910

[INFO] 
[INFO] Building ActiveMQ :: KahaDB Store 5.9-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-kahadb-store 
---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ 
activemq-kahadb-store ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-kahadb-store ---
[INFO] 
[INFO] --- activemq-protobuf:1.1:compile (default) @ activemq-kahadb-store ---
[INFO] Compiling: 
https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/src/main/proto/journal-data.proto
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
activemq-kahadb-store ---
[INFO] [debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/src/main/resources
[INFO] Copying 3 resources

[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
activemq-kahadb-store ---
[INFO] [INFO] Compiling 75 source files to 
https://builds.apache.org/job/ActiveMQ/ws/activemq-kahadb-store/target/classes

[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
activemq-kahadb-store ---
[debug] execute contextualize
[INFO] [INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 

[jira] [Created] (AMQ-4326) Virtual destination and network of brokers

2013-02-17 Thread Brian (JIRA)
Brian created AMQ-4326:
--

 Summary: Virtual destination and network of brokers
 Key: AMQ-4326
 URL: https://issues.apache.org/jira/browse/AMQ-4326
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.8.0, 5.7.0, 5.6.0, 5.5.1
Reporter: Brian
Priority: Critical


---Symptom---
In a network of brokers with a forwarded queue, 
the message flow of the queue is iregular (messages burst)
and messages received are out of order.

---Setup---
- We have 3 brokers linked via network of brokers.
- Brokers 1 and 2 share a topic which is also forwarded to a queue.
- Brokers 1 and 2 has a producer and consumer to the topic
- Broker 3 is connected to the network via the queue

[producer and consumer] [producer and consumer]
||
[Broker 1]  topic  [Broker 2]
||
forward topicforward topic
to queue --- [Broker 3] --- to queue
   |
  [consumer]

--
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


[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers

2013-02-17 Thread Brian (JIRA)

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

Brian updated AMQ-4326:
---

Description: 
--- Symptom ---
In a network of brokers with a forwarded queue, 
the message flow of the queue is iregular (messages burst)
and messages received are out of order.

--- Setup ---
- We have 3 brokers linked via network of brokers.
- Brokers 1 and 2 share a topic which is also forwarded to a queue.
- Brokers 1 and 2 has a producer and consumer to the topic
- Broker 3 is connected to the network via the queue

[producer and consumer] [producer and consumer]
||

[Broker 1]  topic  [Broker 2]
||

forward topic forward topic
to queue --- [Broker 3] --- to queue
   |
  [consumer]

  was:
---Symptom---
In a network of brokers with a forwarded queue, 
the message flow of the queue is iregular (messages burst)
and messages received are out of order.

---Setup---
- We have 3 brokers linked via network of brokers.
- Brokers 1 and 2 share a topic which is also forwarded to a queue.
- Brokers 1 and 2 has a producer and consumer to the topic
- Broker 3 is connected to the network via the queue

[producer and consumer] [producer and consumer]
||
[Broker 1]  topic  [Broker 2]
||
forward topicforward topic
to queue --- [Broker 3] --- to queue
   |
  [consumer]


 Virtual destination and network of brokers
 --

 Key: AMQ-4326
 URL: https://issues.apache.org/jira/browse/AMQ-4326
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0
Reporter: Brian
Priority: Critical
 Attachments: broker1-activemq.xml


 --- Symptom ---
 In a network of brokers with a forwarded queue, 
 the message flow of the queue is iregular (messages burst)
 and messages received are out of order.
 --- Setup ---
 - We have 3 brokers linked via network of brokers.
 - Brokers 1 and 2 share a topic which is also forwarded to a queue.
 - Brokers 1 and 2 has a producer and consumer to the topic
 - Broker 3 is connected to the network via the queue
 [producer and consumer] [producer and consumer]
 ||
 [Broker 1]  topic  [Broker 2]
 ||
 forward topic forward topic
 to queue --- [Broker 3] --- to queue
|
   [consumer]

--
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


[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers

2013-02-17 Thread Brian (JIRA)

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

Brian updated AMQ-4326:
---

Attachment: broker1-activemq.xml

Broker1 conf

 Virtual destination and network of brokers
 --

 Key: AMQ-4326
 URL: https://issues.apache.org/jira/browse/AMQ-4326
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0
Reporter: Brian
Priority: Critical
 Attachments: broker1-activemq.xml


 --- Symptom ---
 In a network of brokers with a forwarded queue, 
 the message flow of the queue is iregular (messages burst)
 and messages received are out of order.
 --- Setup ---
 - We have 3 brokers linked via network of brokers.
 - Brokers 1 and 2 share a topic which is also forwarded to a queue.
 - Brokers 1 and 2 has a producer and consumer to the topic
 - Broker 3 is connected to the network via the queue
 [producer and consumer] [producer and consumer]
 ||
 [Broker 1]  topic  [Broker 2]
 ||
 forward topic forward topic
 to queue --- [Broker 3] --- to queue
|
   [consumer]

--
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


[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers

2013-02-17 Thread Brian (JIRA)

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

Brian updated AMQ-4326:
---

Attachment: setup.png
broker3-activemq.xml
broker2-activemq.xml

Configuration and setup

 Virtual destination and network of brokers
 --

 Key: AMQ-4326
 URL: https://issues.apache.org/jira/browse/AMQ-4326
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0
Reporter: Brian
Priority: Critical
 Attachments: broker1-activemq.xml, broker2-activemq.xml, 
 broker3-activemq.xml, setup.png


 --- Symptom ---
 In a network of brokers with a forwarded queue, 
 the message flow of the queue is iregular (messages burst)
 and messages received are out of order.
 --- Setup ---
 - We have 3 brokers linked via network of brokers.
 - Brokers 1 and 2 share a topic which is also forwarded to a queue.
 - Brokers 1 and 2 has a producer and consumer to the topic
 - Broker 3 is connected to the network via the queue
 [producer and consumer] [producer and consumer]
 ||
 [Broker 1]  topic  [Broker 2]
 ||
 forward topic forward topic
 to queue --- [Broker 3] --- to queue
|
   [consumer]

--
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


[jira] [Updated] (AMQ-4326) Virtual destination and network of brokers

2013-02-17 Thread Brian (JIRA)

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

Brian updated AMQ-4326:
---

Description: 
--- Symptom ---
In a network of brokers with a forwarded queue, 
The queue consumer experiences message bursts (the message flow is iregular)
and messages received are out of order.

--- Setup ---
See attached image from setup

- We have 3 brokers linked via network of brokers.
- Brokers 1 and 2 share a topic which is also forwarded to a queue.
- Brokers 1 and 2 has a producer and consumer to the topic
- Both producers send messages at a rate of at least 15 messages per second.
- Broker 3 is connected to the network via the queue

  was:
--- Symptom ---
In a network of brokers with a forwarded queue, 
the message flow of the queue is iregular (messages burst)
and messages received are out of order.

--- Setup ---
- We have 3 brokers linked via network of brokers.
- Brokers 1 and 2 share a topic which is also forwarded to a queue.
- Brokers 1 and 2 has a producer and consumer to the topic
- Broker 3 is connected to the network via the queue

[producer and consumer] [producer and consumer]
||

[Broker 1]  topic  [Broker 2]
||

forward topic forward topic
to queue --- [Broker 3] --- to queue
   |
  [consumer]


 Virtual destination and network of brokers
 --

 Key: AMQ-4326
 URL: https://issues.apache.org/jira/browse/AMQ-4326
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker
Affects Versions: 5.5.1, 5.6.0, 5.7.0, 5.8.0
Reporter: Brian
Priority: Critical
 Attachments: broker1-activemq.xml, broker2-activemq.xml, 
 broker3-activemq.xml, setup.png


 --- Symptom ---
 In a network of brokers with a forwarded queue, 
 The queue consumer experiences message bursts (the message flow is iregular)
 and messages received are out of order.
 --- Setup ---
 See attached image from setup
 - We have 3 brokers linked via network of brokers.
 - Brokers 1 and 2 share a topic which is also forwarded to a queue.
 - Brokers 1 and 2 has a producer and consumer to the topic
 - Both producers send messages at a rate of at least 15 messages per second.
 - Broker 3 is connected to the network via the queue

--
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


[jira] [Commented] (AMQNET-405) Messages are not dequeued when using Two Phase Commit for DTC Transaction

2013-02-17 Thread Daniel Marbach (JIRA)

[ 
https://issues.apache.org/jira/browse/AMQNET-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13580461#comment-13580461
 ] 

Daniel Marbach commented on AMQNET-405:
---

See also patch provided in https://issues.apache.org/jira/browse/AMQNET-413 
which also fixes this problem

 Messages are not dequeued when using Two Phase Commit for DTC Transaction
 -

 Key: AMQNET-405
 URL: https://issues.apache.org/jira/browse/AMQNET-405
 Project: ActiveMQ .Net
  Issue Type: Bug
  Components: ActiveMQ
Affects Versions: 1.5.6
 Environment: Windows 7, AMQ 5.7
Reporter: Remo Gloor
Assignee: Jim Gomes

 Messages are not removed from the queue even though they are processes 
 correctly in the following scenaro:
 Create a NetTxConnection and NetTxSession. Create a consumer for some queue 
 and register the Listener event. Create a new TransactionScope in the event 
 handler. Inside the consumer you send a new message to some other queue using 
 the session of the consumer. Do now some action that uses the Distributed 
 Transaction from another system (e.g. writing to a database) to force that 
 two phase commit is used instead of Single Phase Commit. Complete the and 
 dispose the TransactionScope.
 I'd expect that that the sent message is delivered to the queue, the database 
 is modified and the received message is removed from the input queue. But the 
 behavior is that the last expectation is not met. The message remains in the 
 input queue.
 If you use an own session for sending the messages the problem does not 
 occur. But this has the disadvantage the you will always do two phase commits 
 even if AMQ is the only system that takes part in the Distrubuted Transaction.
 Code demonstrating the problem:
 namespace ConsoleApplication1
 {
 using System;
 using System.Transactions;
 using Apache.NMS;
 using Apache.NMS.ActiveMQ.Commands;
 using Apache.NMS.Util;
 class Program
 {
 private static INetTxSession activeMqSession;
 private static IMessageConsumer consumer;
 private static INetTxConnection connection;
 static void Main(string[] args)
 {
 using (connection = CreateActiveMqConnection())
 using (activeMqSession = connection.CreateNetTxSession())
 using (consumer = 
 activeMqSession.CreateConsumer(SessionUtil.GetQueue(activeMqSession, 
 queue://foo.bar)))
 {
 consumer.Listener += OnMessage;
 connection.Start();
 Console.WriteLine(Started);
 Console.WriteLine(Press any key to exit);
 Console.ReadKey();
 }
 }
 private static INetTxConnection CreateActiveMqConnection()
 {
 var connectionFactory = new 
 Apache.NMS.ActiveMQ.NetTxConnectionFactory(activemq:tcp://localhost:61616)
 {
 AcknowledgementMode = AcknowledgementMode.Transactional
 };
 return connectionFactory.CreateNetTxConnection();
 }
 private static void OnMessage(IMessage message)
 {
 var x = new TestSinglePhaseCommit();
 using (var session2 = connection.CreateNetTxSession())
 using (var tx = new 
 TransactionScope(TransactionScopeOption.RequiresNew))
 {
 Console.WriteLine(Message Received);
 // Force two phase commit, In reality this happens by using 
 another system that takes part in the 
 // distributed transaction like a database.
 Transaction.Current.EnlistDurable(Guid.NewGuid(), x, 
 EnlistmentOptions.None);
 // The proble occurs only if a message is sent using the same 
 session like the receiver
 using (var producer = 
 session2.CreateProducer(SessionUtil.GetQueue(session2, queue://foo.baz)))
 {
 producer.Send(new ActiveMQTextMessage(foo));
 }
 tx.Complete();
 }
 }
 }
 internal class TestSinglePhaseCommit : ISinglePhaseNotification
 {
 public void Prepare(PreparingEnlistment preparingEnlistment)
 {
 preparingEnlistment.Prepared();
 }
 public void Commit(Enlistment enlistment)
 {
 enlistment.Done();
 }
 public void Rollback(Enlistment enlistment)
 {
 enlistment.Done();
 }
 public void InDoubt(Enlistment enlistment)
 {
 enlistment.Done();
 }
 public void SinglePhaseCommit(SinglePhaseEnlistment 
 singlePhaseEnlistment)
 {
 singlePhaseEnlistment.Committed();