date:20160113

Jenkins build is back to stable : ActiveMQ-Java8 » ActiveMQ :: Broker #581

2016-01-13 Thread Apache Jenkins Server

See

[1/2] activemq-artemis git commit: fix example compilation

2016-01-13 Thread martyntaylor

Repository: activemq-artemis
Updated Branches:
  refs/heads/master a8443512b -> aab09a77d


fix example compilation


Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/14ad3ebc
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/14ad3ebc
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/14ad3ebc

Branch: refs/heads/master
Commit: 14ad3ebcdf21de937959c3e84cb0d45c243d9db8
Parents: a844351
Author: Andy Taylor 
Authored: Wed Jan 13 10:32:20 2016 +
Committer: Andy Taylor 
Committed: Wed Jan 13 10:32:20 2016 +

--
 .../artemis/jms/example/ClientSideLoadBalancingExample.java  | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/14ad3ebc/examples/features/clustered/client-side-load-balancing/src/main/java/org/apache/activemq/artemis/jms/example/ClientSideLoadBalancingExample.java
--
diff --git 
a/examples/features/clustered/client-side-load-balancing/src/main/java/org/apache/activemq/artemis/jms/example/ClientSideLoadBalancingExample.java
 
b/examples/features/clustered/client-side-load-balancing/src/main/java/org/apache/activemq/artemis/jms/example/ClientSideLoadBalancingExample.java
index 1281017..41a3a64 100644
--- 
a/examples/features/clustered/client-side-load-balancing/src/main/java/org/apache/activemq/artemis/jms/example/ClientSideLoadBalancingExample.java
+++ 
b/examples/features/clustered/client-side-load-balancing/src/main/java/org/apache/activemq/artemis/jms/example/ClientSideLoadBalancingExample.java
@@ -16,6 +16,8 @@
  */
 package org.apache.activemq.artemis.jms.example;
 
+import org.apache.activemq.artemis.core.client.impl.ClientSessionInternal;
+
 import javax.jms.Connection;
 import javax.jms.ConnectionFactory;
 import javax.jms.JMSException;
@@ -67,9 +69,9 @@ public class ClientSideLoadBalancingExample {
  Session sessionB = connectionB.createSession(false, 
Session.AUTO_ACKNOWLEDGE);
  Session sessionC = connectionC.createSession(false, 
Session.AUTO_ACKNOWLEDGE);
 
- System.out.println("Session A - " + 
((org.apache.activemq.artemis.core.client.impl.DelegatingSession) 
((org.apache.activemq.artemis.jms.client.ActiveMQSession) 
sessionA).getCoreSession()).getConnection().getRemoteAddress());
- System.out.println("Session B - " + 
((org.apache.activemq.artemis.core.client.impl.DelegatingSession) 
((org.apache.activemq.artemis.jms.client.ActiveMQSession) 
sessionB).getCoreSession()).getConnection().getRemoteAddress());
- System.out.println("Session C - " + 
((org.apache.activemq.artemis.core.client.impl.DelegatingSession) 
((org.apache.activemq.artemis.jms.client.ActiveMQSession) 
sessionC).getCoreSession()).getConnection().getRemoteAddress());
+ System.out.println("Session A - " + ((ClientSessionInternal) 
((org.apache.activemq.artemis.jms.client.ActiveMQSession) 
sessionA).getCoreSession()).getConnection().getRemoteAddress());
+ System.out.println("Session B - " + 
((ClientSessionInternal)((org.apache.activemq.artemis.jms.client.ActiveMQSession)
 sessionB).getCoreSession()).getConnection().getRemoteAddress());
+ System.out.println("Session C - " + 
((ClientSessionInternal)((org.apache.activemq.artemis.jms.client.ActiveMQSession)
 sessionC).getCoreSession()).getConnection().getRemoteAddress());
 
  // Step 6. We create JMS MessageProducer objects on the sessions
  MessageProducer producerA = sessionA.createProducer(queue);

[2/2] activemq-artemis git commit: Merge #313

2016-01-13 Thread martyntaylor

Merge #313


Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/aab09a77
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/aab09a77
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/aab09a77

Branch: refs/heads/master
Commit: aab09a77d3d94c2467f44a761b73d11e48550d83
Parents: a844351 14ad3eb
Author: Martyn Taylor 
Authored: Wed Jan 13 10:45:59 2016 +
Committer: Martyn Taylor 
Committed: Wed Jan 13 10:45:59 2016 +

--
 .../artemis/jms/example/ClientSideLoadBalancingExample.java  | 8 +---
 1 file changed, 5 insertions(+), 3 deletions(-)
--

[CONF] Apache ActiveMQ > Networks of Brokers

2016-01-13 Thread Dejan Bosanac (Confluence)

Title: Message Title

Dejan Bosanac edited a page

Networks of Brokers

...

property
default
description

name
bridge
name of the network - for more than one network connector between the same two brokers - use different names

dynamicOnly
false
if true, only activate a networked durable subscription when a corresponding durable subscription reactivates, by default they are activated on startup.

decreaseNetworkConsumerPriority
false
if true, starting at priority -5, decrease the priority for dispatching to a network Queue consumer the further away it is (in network hops) from the producer. When false all network consumers use same default priority(0) as local consumers

networkTTL
1
the number of brokers in the network that messages and subscriptions can pass through (sets both message -TTL)

messageTTL
1
(version 5.9) the number of brokers in the network that messages can pass through

consumerTTL
1
(version 5.9) the number of brokers in the network that subscriptions can pass through (keep to 1 in a mesh)

conduitSubscriptions
true
multiple consumers subscribing to the same destination are treated as one consumer by the network

excludedDestinations
empty
destinations matching this list won't be forwarded across the network (this only applies to dynamicallyIncludedDestinations)

dynamicallyIncludedDestinations
empty
destinations that match this list will be forwarded across the network n.b. an empty list means all destinations not in the exluded list will be forwarded

useVirtualDestSubs
false
if true, the network connection will listen to advisory messages for virtual destination consumers

staticallyIncludedDestinations
empty
destinations that match will always be passed across the network - even if no consumers have ever registered an interest

duplex
false
if true, a network connection will be used to both produce AND Consume messages. This is useful for hub and spoke scenarios when the hub is behind a firewall etc.

prefetchSize
1000
Sets the prefetch size on the network connector's consumer. It must be > 0 because network consumers do not poll for messages

suppressDuplicateQueueSubscriptions
false
(from 5.3) if true, duplicate subscriptions in the network that arise from network intermediaries will be suppressed. For example, given brokers A,B and C, networked via multicast discovery. A consumer on A will give rise to a networked consumer on B and C. In addition, C will network to B (based on the network consumer from A) and B will network to C. When true, the network bridges between C and B (being duplicates of their existing network subscriptions to A) will be suppressed. Reducing the routing choices in this way provides determinism when producers or consumers migrate across the network as the potential for dead routes (stuck messages) are eliminated. networkTTL needs to match or exceed the broker count to require this intervention.

bridgeTempDestinations
true
Whether to broadcast advisory messages for created temp destinations in the network of brokers or not. Temp destinations are typically created for request-reply messages. Broadcasting the information about temp destinations is turned on by default so that consumers of a request-reply message can be connected to another broker in the network and still send back the reply on the temporary destination specified in the JMSReplyTo header. In an application scenario where most/all messages use request-reply pattern, this will generate additional traffic on the broker network as every message typically sets a unique JMSReplyTo address (which causes a new temp destination to be created and broadcasted via an advisory message in the network of brokers). When disabling this feature such network traffic can be reduced but then producer and consumers of a request-reply message need to be connected to the same broker. Remote consumers (i.e. connected via another broker in your network) won't be able to send the reply message but instead raise a "temp destination does not exist" exception.

alwaysSyncSend
false
(version 5.6) When true, non persistent messages are sent to the remote broker using request/reply in place of a oneway. This setting treats both persistent and non-persistent messages the same.

staticBridge
false
(version 5.6) If set to true, broker will not dynamically respond to new consumers. It will only use staticallyIncludedDestinations to create demand subscriptions

...

Code Block

xml

Note that at the moment excludedDestinations property

Jenkins build is still unstable: ActiveMQ-Java8 #581

2016-01-13 Thread Apache Jenkins Server

See

Jenkins build is still unstable: ActiveMQ-Java8 » ActiveMQ :: Unit Tests #581

2016-01-13 Thread Apache Jenkins Server

See

svn commit: r977596 - in /websites/production/activemq/content: cache/main.pageCache networks-of-brokers.html

2016-01-13 Thread buildbot

Author: buildbot
Date: Wed Jan 13 12:22:29 2016
New Revision: 977596

Log:
Production update by buildbot for activemq

Modified:
websites/production/activemq/content/cache/main.pageCache
websites/production/activemq/content/networks-of-brokers.html

Modified: websites/production/activemq/content/cache/main.pageCache
==
Binary files - no diff available.

Modified: websites/production/activemq/content/networks-of-brokers.html
==
--- websites/production/activemq/content/networks-of-brokers.html (original)
+++ websites/production/activemq/content/networks-of-brokers.html Wed Jan 13 
12:22:29 2016
@@ -137,7 +137,7 @@
   networkConnector 
uri="masterslave:(tcp://host1:61616,tcp://host2:61616,tcp://..)"/
 /networkConnectors
 
-The URIs are listed in order for: 
MASTER,SLAVE1,SLAVE2...SLAVEhttps://cwiki.apache.org/confluence/s/en_GB/5982/f2b47fb3d636c8bc9fd0b11c0ec6d0ae18646be7.1/_/images/icons/emoticons/thumbs_down.png;
 data-emoticon-name="thumbs-down" alt="(thumbs down)">The same 
configuration options for static: are available for 
masterslave:NetworkConnector 
Propertiespropertydefaultdescriptionnamebridgename of the network -
  for more than one network connector between the same two brokers - use 
different namesdynamicOnlyfalseif true, only activate a networked durable subscription 
when a corresponding durable subscription reactivates, by default they are 
activated on startup.decreaseNetworkConsumerPriorityfalseif true, starting at priority -5, decrease the priority 
for dispatching to a network Queue consumer the further away it is (in network 
hops) from the producer. When false all network consumers use same default 
priority(0) as local consumersnetworkTTL1the number of brokers in the 
network that messages and subscriptions can pass through (sets both 
messageconsumer -TTL)messageTTL1(version 5.9) the number of brokers in the network that 
messages can pass throughconsumerTTL1(version 5.9) the number of brokers in the network that 
subscriptions can pass through (keep to 1 in a mesh)conduitSubscriptionstruemultiple consumers 
subscribing to the same destination are treated as one consumer by the 
networkexcludedDestinationsemptydestinations matching this list won't be forwarded 
across the networkdynamicallyIncludedDestinationsemptydestinations that match this list will 
be forwarded across the network n.b. an empty list means all 
destinations not in the exluded list will be forwardeduseVirtualDestSubs
 falseif true, the 
network connection will listen to advisory messages for virtual destination 
consumersstaticallyIncludedDestinationsemptydestinations that match will always be passed across 
the network - even if no consumers have ever registered an 
interestduplexfalseif true, a network connection will be used to both 
produce AND Consume messages. This is useful for hub 
and spoke scenarios when the hub is behind a firewall etc.prefetchSize1000Sets the prefetch size on the network 
connector's consumer. It must be  0 because network consumers do not poll 
for messagessuppressDuplicateQueueSubscriptionsfalse(from 5.3) if true, duplicate subscriptions 
in the network that arise from network intermediaries will be suppressed. For 
example, given brokers A,B and C, networked via multicast discovery. A consumer 
on A will give rise to a networked consumer on B and C. In addition, C will 
network to B (based on the network consumer from A) and B will network to C. 
When true, the network bridges between C and B (being duplicates of their 
existing network subscriptions to A) will b
 e suppressed. Reducing the routing choices in this way provides determinism 
when producers or consumers migrate across the network as the potential for 
dead routes (stuck messages) are eliminated. networkTTL needs to match or 
exceed the broker count to require this intervention.bridgeTempDestinationstrueWhether to broadcast advisory messages for created temp 
destinations in the network of brokers or not. Temp destinations are typically 
created for request-reply messages. Broadcasting the information about temp 
destinations is turned on by default so that consumers of a request-reply 
message can be connected to another broker in the network and still send back 
the reply on the temporary destination specified in the JMSReplyTo header. In 
an application scenario where most/all messages use request
 -reply pattern, this will generate additional traffic on the broker network as 
every message typically sets a unique JMSReplyTo address (which causes a new 
temp destination to be created and broadcasted via an advisory message in the 
network of brokers).  When disabling this feature such network 
traffic can be reduced but then producer and consumers of a request-reply 
message need to be connected to the same broker. Remote consumers (i.e. 
connected

buildbot failure in ASF Buildbot on activemq-site-production

2016-01-13 Thread buildbot

The Buildbot has detected a new failure on builder activemq-site-production 
while building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/activemq-site-production/builds/4738

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'activemq-site-production' triggered 
this build
Build Source Stamp: [branch activemq/activemq-website] HEAD
Blamelist: 

BUILD FAILED: failed compile

Sincerely,
 -The Buildbot

buildbot success in ASF Buildbot on activemq-site-production

2016-01-13 Thread buildbot

The Buildbot has detected a restored build on builder activemq-site-production 
while building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/activemq-site-production/builds/4737

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: bb-cms-slave

Build Reason: The Nightly scheduler named 'activemq-site-production' triggered 
this build
Build Source Stamp: [branch activemq/activemq-website] HEAD
Blamelist: 

Build succeeded!

Sincerely,
 -The Buildbot

[CONF] Apache ActiveMQ > Apache ActiveMQ 5.12.2 Released

2016-01-13 Thread Christopher L. Shannon (Confluence)

Title: Message Title



 
 
 
 
 
 
 

Christopher L. Shannon created a blog post 
 
 
  
 
 
 
 
 
 
 
  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Apache ActiveMQ 5.12.2 Released 
 
 
  
 
 
 
 
 
 
  The ActiveMQ team is pleased to announce the release of ActiveMQ 5.12.2   A big thanks to everyone who contributed to this release.   We look forward to your feedback.   
 
 
  
 
 
 
 
 
 
 
 
 
 

View blog post
• 
 
 
 
 
 
 

Like 
 
 
  
 
 
  
 
 
  
 
 
  
 
 
 
 
 
 
 
 
 
 
Stop watching space
• 
 
 
 
 
 
 
Manage notifications 
 
 
 
 
 
 
 
 
 
 
  
 
 
This message was sent by Atlassian Confluence 5.8.4

52 matches

Mail list logo