Build failed in Jenkins: ActiveMQ-Trunk-Deploy #1615

[Apache Jenkins Server]

See 

Changes:

[tabish121] Fix failing test in CI.  Subscribe should request receipts so that 
the

[tabish121] Fix test timing out on slow spinning disks.

--
[...truncated 220 lines...]
[INFO] Skipping ActiveMQ :: All JAR bundle
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Log4j Appender
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Apache Karaf
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: RAR
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Run Jar
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Shiro
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Memory Usage Test Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Performance Test Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: StartUp/Stop Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[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 :: OSGi bundle
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Blueprint
[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 

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ #1615

[Apache Jenkins Server]

See 


--
Established TCP socket on 37931
maven3-agent.jar already up to date
maven3-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
<===[JENKINS REMOTING CAPACITY]===>   channel started
Executing Maven:  -B -f 

 -Dmaven.repo.local=/home/jenkins/jenkins-slave/maven-repositories/1 -fae -B -e 
-U clean deploy -Pdeploy -Dtest=0
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] ActiveMQ
[INFO] ActiveMQ :: Openwire Generator
[INFO] ActiveMQ :: Client
[INFO] ActiveMQ :: Openwire Legacy Support
[INFO] ActiveMQ :: JAAS
[INFO] ActiveMQ :: Broker
[INFO] ActiveMQ :: KahaDB Store
[INFO] ActiveMQ :: STOMP Protocol
[INFO] ActiveMQ :: MQTT Protocol
[INFO] ActiveMQ :: JDBC Store
[INFO] ActiveMQ :: LevelDB Store
[INFO] ActiveMQ :: Generic JMS Pool
[INFO] ActiveMQ :: Pool
[INFO] ActiveMQ :: RA
[INFO] ActiveMQ :: Spring
[INFO] ActiveMQ :: AMQP
[INFO] ActiveMQ :: Console
[INFO] ActiveMQ :: Partition Management
[INFO] ActiveMQ :: Runtime Configuration
[INFO] ActiveMQ :: Tooling
[INFO] ActiveMQ :: JUnit Rule
[INFO] ActiveMQ :: Unit Tests
[INFO] ActiveMQ :: Camel
[INFO] ActiveMQ :: HTTP Protocol Support
[INFO] ActiveMQ :: All JAR bundle
[INFO] ActiveMQ :: Log4j Appender
[INFO] ActiveMQ :: Apache Karaf
[INFO] ActiveMQ :: RAR
[INFO] ActiveMQ :: Run Jar
[INFO] ActiveMQ :: Shiro
[INFO] ActiveMQ :: Memory Usage Test Plugin
[INFO] ActiveMQ :: Performance Test Plugin
[INFO] ActiveMQ :: StartUp/Stop Plugin
[INFO] ActiveMQ :: Web
[INFO] ActiveMQ :: OSGi bundle
[INFO] ActiveMQ :: Blueprint
[INFO] ActiveMQ :: Web Demo
[INFO] ActiveMQ :: Web Console
[INFO] ActiveMQ :: Karaf Integration Tests
[INFO] ActiveMQ :: Integration Test :: Spring 3.1
[INFO] ActiveMQ :: Assembly
[INFO] 
[INFO] 
[INFO] Building ActiveMQ 5.14.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-parent ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (default) @ activemq-parent ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-parent ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
activemq-parent ---
[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
activemq-parent ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (default) @ activemq-parent ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
activemq-parent ---
[WARNING] Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ activemq-parent ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @ activemq-parent 
---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] 
[INFO] --- ianal-maven-plugin:1.0-alpha-1:verify-legal-files (default) @ 
activemq-parent ---
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
activemq-parent ---
[INFO] Installing 

 to 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/activemq/activemq-parent/5.14.0-SNAPSHOT/activemq-parent-5.14.0-SNAPSHOT.pom
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ activemq-parent 
---
Downloading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-parent/5.14.0-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata 
org.apache.activemq:activemq-parent:5.14.0-SNAPSHOT/maven-metadata.xml from/to 
apache.snapshots.https 
(https://repository.apache.org/content/repositories/snapshots): Failed to 
transfer file: 
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-parent/5.14.0-SNAPSHOT/maven-metadata.xml.
 Return code is: 503, ReasonPhrase:Service Unavailable.

[GitHub] activemq-artemis pull request: A few fixes I have been working on

[clebertsuconic]

GitHub user clebertsuconic opened a pull request:

https://github.com/apache/activemq-artemis/pull/522

A few fixes I have been working on



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/clebertsuconic/activemq-artemis master-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/522.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #522


commit ec52693513b2f3a4a63f9cf4089bb8213ac8468c
Author: Clebert Suconic 
Date:   2016-05-17T18:36:59Z

Individualizing traces and debug on client

commit 1f02ad4cd9ac2d36ffe20c54a1d79bf83d06d421
Author: Clebert Suconic 
Date:   2016-05-17T19:06:02Z

ARTEMIS-524 Paging could lose data eventually after crashes

https://issues.apache.org/jira/browse/ARTEMIS-524

I am keeping all the debug ad tracing I added during the debug of this 
issue,
for that reason this commit may look longer than expected

The fix will be highlited by the tests added on 
org.apache.activemq.artemis.tests.integration.client.PagingTest

commit da101e7f3a7339669eaf37bf82536dae06ab9dd0
Author: Clebert Suconic 
Date:   2016-05-17T23:33:36Z

ARTEMIS-525 Interrupted Thread should throw JMS Exceptions over the JMS 
layer




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: ARTEMIS-523 re-order SASL mechs

[jbertram]

GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/521

ARTEMIS-523 re-order SASL mechs



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-523

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/521.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #521


commit dd0e207a0d01452d6312860be9a0a82c40809da6
Author: jbertram 
Date:   2016-05-17T19:56:46Z

ARTEMIS-523 re-order SASL mechs




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[Stomp/ActiveMQ CMS] Stomp Delivery Mode

[ActiveMQ Investigation]

Hello,

I am testing ActiveMQ as alternative of SonicMQ for our systems (OpenEdge).
I have done a Stomp Layer on OpenEdge Application to communicate with
ActiveMQ. Please note that hardware is identical to do all these tests.

When I send 25000 messages on a queue via Stomp to ActiveMQ consumer then it
takes around 4 seconds. When I do it via ActiveMQ CMS c++ client using open
wire, it takes approx 4 seconds if setDeliveryMode is
DeliveryMode::NON_PERSISTENT. If I comment this code (which means Persistent
Mode by default) or use DeliveryMode::PERSISTENT then it takes 32 seconds to
delivery all these messages.

If I do it on Topic on C++ client, irrespective of Delivery Mode setup, it
takes approx 4 seconds to delivery all messages to a non durable subscriber.

My Query due to difference in time metrics is:

> Do I need to explicitly send delivery mode via Stomp as Persistent/Non
> Persistent i.e doesn't it reciprocate Default Persistence of ActiveMQ
> (based on time taken of 4 seconds agains C++ open wire of 32 seconds).

> if yes, then what header do I use and should it be in every message I send
> or just in connect?

> How come topic takes same approx 4 seconds irrespective of Delivery Mode.

Please note that I am not using Async etc to affect this perforamance. It's
a default configuration of ActiveMQ install I have.

Any help will be appreciated.

Thanks
AJ




--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Stomp-ActiveMQ-CMS-Stomp-Delivery-Mode-tp4712043.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[GitHub] activemq-artemis pull request: ARTEMIS-522 fix AMQP ANON advert

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/519


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] activemq-artemis pull request: using 1.18 on winsw

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/520


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [Stomp/ActiveMQ CMS] Delivery Mode

[Timothy Bish]

On 05/17/2016 10:25 AM, ActiveMQ Investigation wrote:

Thank you for explanation Tim.

Actually I am using Stomp only for our application which is written in
OpenEdge as it doesn't provide any JMS implementation/ API or protocol to
connect to ActiveMQ. So stomp was the way. I am not using STOMP in ActiveMQ
CPP as openwire is already there.


Sending 25K took 4 seconds via Stomp Layer which is acceptable for our use
case.

Now there was another part of system in C++. To check performance for C++
side, I used default setup of ActiveMQ CPP (openwire) and it did send 25k
message in 4 seconds if Delivery Mode is non-persistent. If I make it
persistent, it takes 32 secs on a Queue.


This caused me to investigate what Stomp is doing with Delivery Mode. Is it
sending messages persistently or Non persistently. I expect it should take
approx 32 seconds via stomp as well because Default ActiveMQ mode is
Persistent.

Is there anyway I can check what delivery mode is being used for a
connection.All I have is a native Apache Console to see what Queues /
Topics/connections are there and counter of messages on it.


Any help is appreciated.

Thanks
AJ





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Stomp-ActiveMQ-CMS-Delivery-Mode-tp4712048p4712053.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

If you want to replicate what the CMS or JMS clients do via OpenWire 
then you need to set the persistent header in the STOMP message headers 
(persistent=true) and request a receipt be returned to you via the 
standard STOMP header for doing such (receipt:).


http://activemq.apache.org/stomp.html
http://stomp.github.io/stomp-specification-1.2.html#Header_receipt

--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/

Re: [Stomp/ActiveMQ CMS] Delivery Mode

[ActiveMQ Investigation]

Thank you for explanation Tim.

Actually I am using Stomp only for our application which is written in
OpenEdge as it doesn't provide any JMS implementation/ API or protocol to
connect to ActiveMQ. So stomp was the way. I am not using STOMP in ActiveMQ
CPP as openwire is already there. 


Sending 25K took 4 seconds via Stomp Layer which is acceptable for our use
case.

Now there was another part of system in C++. To check performance for C++
side, I used default setup of ActiveMQ CPP (openwire) and it did send 25k
message in 4 seconds if Delivery Mode is non-persistent. If I make it
persistent, it takes 32 secs on a Queue.


This caused me to investigate what Stomp is doing with Delivery Mode. Is it
sending messages persistently or Non persistently. I expect it should take
approx 32 seconds via stomp as well because Default ActiveMQ mode is
Persistent. 

Is there anyway I can check what delivery mode is being used for a
connection.All I have is a native Apache Console to see what Queues /
Topics/connections are there and counter of messages on it.


Any help is appreciated.

Thanks
AJ





--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Stomp-ActiveMQ-CMS-Delivery-Mode-tp4712048p4712053.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [Stomp/ActiveMQ CMS] Delivery Mode

[Timothy Bish]

On 05/17/2016 09:18 AM, ActiveMQ Investigation wrote:

Hello,

I am testing ActiveMQ as alternative of SonicMQ for our systems (OpenEdge).
I have done a Stomp Layer on OpenEdge Application to communicate with
ActiveMQ.

When I send 25000 messages on a queue via Stomp to ActiveMQ consumer then it
takes around 4 seconds. When I do it via ActiveMQ CMS c++ client using open
wire, it takes approx 4 seconds if setDeliveryMode is
DeliveryMode::NON_PERSISTENT. If I comment this code (which means Persistent
Mode by default) or use DeliveryMode::PERSISTENT then it takes 32 seconds to
delivery all these messages.

If I do it on Topic on C++ client, irrespective of Delivery Mode setup, it
takes approx 4 seconds to delivery all messages to a non durable subscriber.
If you are using ActiveMQ-CPP to talk to ActiveMQ then the best solution 
is to use the OpenWire protocol as the STOMP support in that library is 
mainly a legacy feature and not actively maintained, it works but it has 
many limitations and probably more than a few bugs.


The difference in times for sending to Topic vs Queue and PERSISTENT vs 
NON-PERSISTENT comes down to the underlying guarantee if QoS that the 
sender expects.  For reliable messaging the client will request a 
response from the broker that indicates that the message has been 
received and stored before the send call returns so it can throw an 
exception if that fails to happen or the broker tells it about some 
error.  When you are dealing with non-persistent messages you are 
essentially saying that you don't care if the message is lost so the 
client doesn't request a response and sends are basically async (fire 
and forget).



My Query due to difference in time metrics is:


Do I need to explicitly send delivery mode via Stomp as Persistent/Non
Persistent i.e doesn't it reciprocate Default Persistence of ActiveMQ
(based on time taken of 4 seconds agains C++ open wire of 32 seconds).
if yes, then what header do I use and should it be in every message I send
or just in connect?
How come topic takes same approx 4 seconds irrespective of Delivery Mode.

Please note that I am not using Async etc to affect this performance. It's a
default configuration of ActiveMQ install I have.

Any help will be appreciated.

Thanks
AJ



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Stomp-ActiveMQ-CMS-Delivery-Mode-tp4712048.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/

[GitHub] activemq-artemis pull request: using 1.18 on winsw

[clebertsuconic]

GitHub user clebertsuconic opened a pull request:

https://github.com/apache/activemq-artemis/pull/520

using 1.18 on winsw



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/clebertsuconic/activemq-artemis winsw

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/520.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #520


commit b7f6c14425a3c5ce5da640f7aea6ba3526511862
Author: Clebert Suconic 
Date:   2016-05-17T14:03:02Z

using 1.18 on winsw




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[Stomp/ActiveMQ CMS] Delivery Mode

[ActiveMQ Investigation]

Hello,

I am testing ActiveMQ as alternative of SonicMQ for our systems (OpenEdge).
I have done a Stomp Layer on OpenEdge Application to communicate with
ActiveMQ. 

When I send 25000 messages on a queue via Stomp to ActiveMQ consumer then it
takes around 4 seconds. When I do it via ActiveMQ CMS c++ client using open
wire, it takes approx 4 seconds if setDeliveryMode is
DeliveryMode::NON_PERSISTENT. If I comment this code (which means Persistent
Mode by default) or use DeliveryMode::PERSISTENT then it takes 32 seconds to
delivery all these messages.

If I do it on Topic on C++ client, irrespective of Delivery Mode setup, it
takes approx 4 seconds to delivery all messages to a non durable subscriber.

My Query due to difference in time metrics is:

> Do I need to explicitly send delivery mode via Stomp as Persistent/Non
> Persistent i.e doesn't it reciprocate Default Persistence of ActiveMQ
> (based on time taken of 4 seconds agains C++ open wire of 32 seconds).

> if yes, then what header do I use and should it be in every message I send
> or just in connect?

> How come topic takes same approx 4 seconds irrespective of Delivery Mode.

Please note that I am not using Async etc to affect this performance. It's a
default configuration of ActiveMQ install I have. 

Any help will be appreciated.

Thanks
AJ



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Stomp-ActiveMQ-CMS-Delivery-Mode-tp4712048.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[GitHub] activemq-artemis pull request: ARTEMIS-522 fix AMQP ANON advert

[jbertram]

GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/519

ARTEMIS-522 fix AMQP ANON advert



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-522

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/519.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #519


commit ca8c9afcef35255a6e4ebb5403bd858598b55d04
Author: jbertram 
Date:   2016-05-17T13:46:36Z

ARTEMIS-522 fix AMQP ANON advert




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---