Re: what is the root cause and how to resolve the error i.e javax.jms.JMSException: No buffer space available (maximum connections reached?

2014-09-23 Thread venkatesh
Hi Tim,

Please find more details related to this issue and also answers for your
below questions

Your Question: Was there anything unusual in the logs around the time the
errors were seen?  
Answer: Actually No, But there is one scenario during our performance test
where this issue occurs but it's not a valid scenario  

Your Question: Finally, your stack trace from several days ago shows that 
com.spacetimeinsight.alerts.util.MessagingUtils.sendMessage() calls 
org.apache.activemq.ActiveMQConnection.createSession().  

Answer: Please find below code snippet once.
try {
ConnectionFactory connectionFactory = 
(ConnectionFactory)
JNDIUtils.getJNDIResouceSource(resourceName);
connection = connectionFactory.createConnection();
Session session = connection.createSession(false,
Session.CLIENT_ACKNOWLEDGE);
connection.start();
MessageProducer producer = 
session.createProducer((Destination)
JNDIUtils.getJNDIResouceSource(destinationName));
producer.send(buildMessage(msg, msgType, 
session,props));
} catch (Exception e) {
//some code here
} finally {
if (connection != null) {
try {
connection.close();
} catch (JMSException e) {
// TODO Auto-generated catch block
Logger.error(Exception is sendMessage  
while close connection ,
MessagingUtils.class, e);
}
}

Question: Do you create a new AMQ session for every message you send?  
Answer: Yes

Question: Is there any caching/pooling being done?
Answer: No


Thanks,
Venkatesh



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/what-is-the-Root-cause-and-how-to-resolve-the-error-i-e-javax-jms-JMSException-No-buffer-space-avail-tp4685440p4685778.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Session is closed exception

2014-09-23 Thread Hilderich
Hello All,

We are using in Talend activemq under the hood by component tJMSInput. This
DI Job runs all the time but we get sometimes the exception:



First question: Is the cause client or server (broker)?
Seciond question: If it is the client what can it do to avoid this exception
maybe by establish a new connection/session?

See also:  http://www.talendforge.org/forum/viewtopic.php?id=38444
http://www.talendforge.org/forum/viewtopic.php?id=38444  

The client is using activemq version 5.7.0

Kind regards
Hilderich



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Session-is-closed-exception-tp4685797.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Replicated LevelDB store issues

2014-09-23 Thread davidvg77
Hi all,


I'm getting this exception when starting ActiveMQ with following persistence
configuration.
Currently, an instance is elected as a master, but in that moment, i get
this exception:

java.io.IOException:
com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39)
at
org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:552)
at
org.apache.activemq.leveldb.LevelDBClient.replay_init(LevelDBClient.scala:657)
at
org.apache.activemq.leveldb.LevelDBClient.start(LevelDBClient.scala:558)
at org.apache.activemq.leveldb.DBManager.start(DBManager.scala:648)
at
org.apache.activemq.leveldb.LevelDBStore.doStart(LevelDBStore.scala:235)
at
org.apache.activemq.leveldb.replicated.MasterLevelDBStore.doStart(MasterLevelDBStore.scala:110)
at
org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
at
org.apache.activemq.leveldb.replicated.ElectingLevelDBStore$$anonfun$start_master$1.apply$mcV$sp(ElectingLevelDBStore.scala:226)
at
org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:330)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:701)
Caused by: java.lang.NoSuchMethodError:
com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
at org.iq80.leveldb.impl.MMapLogWriter.close(MMapLogWriter.java:83)
at
org.iq80.leveldb.impl.VersionSet.initializeIfNeeded(VersionSet.java:111)
at org.iq80.leveldb.impl.VersionSet.init(VersionSet.java:91)
at org.iq80.leveldb.impl.DbImpl.init(DbImpl.java:178)
at org.iq80.leveldb.impl.Iq80DBFactory.open(Iq80DBFactory.java:59)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply$mcV$sp(LevelDBClient.scala:661)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply(LevelDBClient.scala:657)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply(LevelDBClient.scala:657)
at
org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:549)
... 11 more

Persistence configuration:
persistenceAdapter

replicatedLevelDB
  directory=activemq-data
  replicas=3
  bind=tcp://0.0.0.0:
  zkAddress=172.0.3.25:2181
  zkPassword=
securityToken=abcd
  zkPath=/activemq/leveldb-stores
  /

/persistenceAdapter



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Replicated-LevelDB-store-issues-tp4685793.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Re: Apollo: Messages always persists

2014-09-23 Thread Hiram Chirino
That's just the way apollo works.  It does not guarantee
non-persistent messages will survive a restart, but it does not go out
of it's way to drop them if there is a restart.  Basically if your
message gets paged out to disk, it will survive.

On Mon, Sep 8, 2014 at 5:25 AM, All JN jna67...@gmail.com wrote:
 Hello,



 I’m trying to use Apollo 1.7.

 I’m facing a problem with my first JMS test: I use a non-persistent
 delivery mode, the messages are persisted and survive to a restart.

 Someone can explain me?



 Thx.



-- 
Hiram Chirino
Engineering | Red Hat, Inc.
hchir...@redhat.com | fusesource.com | redhat.com
skype: hiramchirino | twitter: @hiramchirino


Re: what is the root cause and how to resolve the error i.e javax.jms.JMSException: No buffer space available (maximum connections reached?

2014-09-23 Thread Tim Bain
The fact that you create a new ActiveMQ connection for each message seems
like the probable cause for the error you saw.  If you had a surge of N
messages to process all at once, you'd have N connections open (I'm
assuming you're processing your messages asynchronously), so if N was large
enough, you could overrun the limit for the number of concurrent
connections.

The Spring page http://activemq.apache.org/spring-support.html of the
ActiveMQ documentation recommends using a pooled connection factory
(org.apache.activemq.pool.PooledConnectionFactory) when working with
Spring's JmsTemplate, and I would think you'd want to do the same.  (Maybe
you'd also want to use Spring's JmsTemplate, too?)  I haven't used ActiveMQ
without the support of another framework (Spring or Camel), so I don't have
concrete tips for exactly how to use a PooledConnectionFactory, but
hopefully the page I linked plus what you find from Googling will give you
enough to figure it out.

Tim

On Tue, Sep 23, 2014 at 12:06 AM, venkatesh venkatesh.sti...@gmail.com
wrote:

 Hi Tim,

 Please find more details related to this issue and also answers for your
 below questions

 Your Question: Was there anything unusual in the logs around the time the
 errors were seen?
 Answer: Actually No, But there is one scenario during our performance test
 where this issue occurs but it's not a valid scenario

 Your Question: Finally, your stack trace from several days ago shows that
 com.spacetimeinsight.alerts.util.MessagingUtils.sendMessage() calls
 org.apache.activemq.ActiveMQConnection.createSession().

 Answer: Please find below code snippet once.
 try {
 ConnectionFactory connectionFactory =
 (ConnectionFactory)
 JNDIUtils.getJNDIResouceSource(resourceName);
 connection = connectionFactory.createConnection();
 Session session = connection.createSession(false,
 Session.CLIENT_ACKNOWLEDGE);
 connection.start();
 MessageProducer producer =
 session.createProducer((Destination)
 JNDIUtils.getJNDIResouceSource(destinationName));
 producer.send(buildMessage(msg, msgType,
 session,props));
 } catch (Exception e) {
 //some code here
 } finally {
 if (connection != null) {
 try {
 connection.close();
 } catch (JMSException e) {
 // TODO Auto-generated catch block
 Logger.error(Exception is
 sendMessage  while close connection ,
 MessagingUtils.class, e);
 }
 }

 Question: Do you create a new AMQ session for every message you send?
 Answer: Yes

 Question: Is there any caching/pooling being done?
 Answer: No


 Thanks,
 Venkatesh



 --
 View this message in context:
 http://activemq.2283324.n4.nabble.com/what-is-the-Root-cause-and-how-to-resolve-the-error-i-e-javax-jms-JMSException-No-buffer-space-avail-tp4685440p4685778.html
 Sent from the ActiveMQ - User mailing list archive at Nabble.com.



Re: Replicated LevelDB store issues

2014-09-23 Thread Kevin Burton
Look at the cause … see below.

It’s a NoSuchMethodError…

You have the wrong version of guava sitting around… or one of the .jars
you’re using is newer and compiled for a newer version of guava :-(

I know.. not fun.  I think this is an issue regarding 17 removing this
method but 15 having it and a LOT of libraries use this version.

But if you have a newer jar using 17 you would have to regress...

 Caused by: java.lang.NoSuchMethodError:
com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
at org.iq80.leveldb.impl.MMapLogWriter.close(MMapLogWriter.java:83)
at
org.iq80.leveldb.impl.VersionSet.initializeIfNeeded(VersionSet.java:111)
at org.iq80.leveldb.impl.VersionSet.init(VersionSet.java:91)
at org.iq80.leveldb.impl.DbImpl.init(DbImpl.java:178)
at org.iq80.leveldb.impl.Iq80DBFactory.open(Iq80DBFactory.java:59)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_
init$2.apply$mcV$sp(LevelDBClient.scala:661)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_
init$2.apply(LevelDBClient.scala:657)
at
org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_
init$2.apply(LevelDBClient.scala:657)
at
org.apache.activemq.leveldb.LevelDBClient.might_fail(
LevelDBClient.scala:549)
... 11 more

On Tue, Sep 23, 2014 at 2:29 AM, davidvg77 david.visi...@gmail.com wrote:

 Hi all,


 I'm getting this exception when starting ActiveMQ with following
 persistence
 configuration.
 Currently, an instance is elected as a master, but in that moment, i get
 this exception:

 java.io.IOException:
 com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
 at

 org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:39)
 at

 org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:552)
 at

 org.apache.activemq.leveldb.LevelDBClient.replay_init(LevelDBClient.scala:657)
 at
 org.apache.activemq.leveldb.LevelDBClient.start(LevelDBClient.scala:558)
 at org.apache.activemq.leveldb.DBManager.start(DBManager.scala:648)
 at
 org.apache.activemq.leveldb.LevelDBStore.doStart(LevelDBStore.scala:235)
 at

 org.apache.activemq.leveldb.replicated.MasterLevelDBStore.doStart(MasterLevelDBStore.scala:110)
 at
 org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)
 at

 org.apache.activemq.leveldb.replicated.ElectingLevelDBStore$$anonfun$start_master$1.apply$mcV$sp(ElectingLevelDBStore.scala:226)
 at
 org.fusesource.hawtdispatch.package$$anon$4.run(hawtdispatch.scala:330)
 at

 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
 at

 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:701)
 Caused by: java.lang.NoSuchMethodError:
 com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
 at org.iq80.leveldb.impl.MMapLogWriter.close(MMapLogWriter.java:83)
 at
 org.iq80.leveldb.impl.VersionSet.initializeIfNeeded(VersionSet.java:111)
 at org.iq80.leveldb.impl.VersionSet.init(VersionSet.java:91)
 at org.iq80.leveldb.impl.DbImpl.init(DbImpl.java:178)
 at org.iq80.leveldb.impl.Iq80DBFactory.open(Iq80DBFactory.java:59)
 at

 org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply$mcV$sp(LevelDBClient.scala:661)
 at

 org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply(LevelDBClient.scala:657)
 at

 org.apache.activemq.leveldb.LevelDBClient$$anonfun$replay_init$2.apply(LevelDBClient.scala:657)
 at

 org.apache.activemq.leveldb.LevelDBClient.might_fail(LevelDBClient.scala:549)
 ... 11 more

 Persistence configuration:
 persistenceAdapter

 replicatedLevelDB
   directory=activemq-data
   replicas=3
   bind=tcp://0.0.0.0:
   zkAddress=172.0.3.25:2181
   zkPassword=
 securityToken=abcd
   zkPath=/activemq/leveldb-stores
   /

 /persistenceAdapter



 --
 View this message in context:
 http://activemq.2283324.n4.nabble.com/Replicated-LevelDB-store-issues-tp4685793.html
 Sent from the ActiveMQ - User mailing list archive at Nabble.com.




-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
https://plus.google.com/102718274791889610666/posts
http://spinn3r.com


Re: Replicated LevelDB store issues

2014-09-23 Thread Kevin Burton
… and I seem to recall that I fixed this and had to rm a jar or move it to
a specific directory.  But I’ve long forgotten which one :-( ….

So to help you resolve this here are all the .jars in my activemq 5.10
install… you can just diff your .jars and probably figure out what’s wrong.


./bin/wrapper.jar

./bin/activemq.jar

./activemq-all-5.10.0.jar

./lib/activemq-web-5.10.0.jar

./lib/activemq-kahadb-store-5.10.0.jar

./lib/slf4j-api-1.7.5.jar

./lib/activemq-openwire-legacy-5.10.0.jar

./lib/activemq-console-5.10.0.jar

./lib/jcl-over-slf4j-1.7.5.jar

./lib/hawtbuf-1.10.jar

./lib/insight-log-core-7.2.0.redhat-024.jar

./lib/geronimo-jms_1.1_spec-1.1.1.jar

./lib/activemq-protobuf-1.1.jar

./lib/extra/mqtt-client-1.10.jar

./lib/optional/jaxb2-basics-runtime-0.6.4.jar

./lib/optional/spring-jms-3.2.8.RELEASE.jar

./lib/optional/jasypt-1.9.1.jar

./lib/optional/xbean-spring-3.16.jar

./lib/optional/guava-12.0.jar

./lib/optional/commons-beanutils-1.8.3.jar

./lib/optional/activemq-shiro-5.10.0.jar

./lib/optional/activemq-log4j-appender-5.10.0.jar

./lib/optional/jackson-mapper-asl-1.9.12.jar

./lib/optional/spring-aop-3.2.8.RELEASE.jar

./lib/optional/leveldb-0.6.jar

./lib/optional/org.apache.servicemix.bundles.josql-1.5_5.jar

./lib/optional/hawtjni-runtime-1.9.jar

./lib/optional/spring-core-3.2.8.RELEASE.jar

./lib/optional/hawtdispatch-transport-1.21.jar

./lib/optional/org.linkedin.util-core-1.4.0.jar

./lib/optional/activemq-runtime-config-5.10.0.jar

./lib/optional/proton-jms-0.7.jar

./lib/optional/activeio-core-3.1.4.jar

./lib/optional/slf4j-log4j12-1.7.5.jar

./lib/optional/shiro-core-1.2.2.jar

./lib/optional/jackson-core-asl-1.9.12.jar

./lib/optional/leveldbjni-1.8.jar

./lib/optional/jmdns-3.4.1.jar

./lib/optional/hawtdispatch-1.21.jar

./lib/optional/spring-beans-3.2.8.RELEASE.jar

./lib/optional/activemq-amqp-5.10.0.jar

./lib/optional/activemq-jms-pool-5.10.0.jar

./lib/optional/zookeeper-3.4.5.jar

./lib/optional/commons-net-3.3.jar

./lib/optional/jettison-1.3.5.jar

./lib/optional/velocity-1.7.jar

./lib/optional/activemq-leveldb-store-5.10.0.jar

./lib/optional/activemq-mqtt-5.10.0.jar

./lib/optional/hawtdispatch-scala-2.11-1.21.jar

./lib/optional/commons-dbcp-1.4.jar

./lib/optional/scala-library-2.11.0.jar

./lib/optional/activemq-http-5.10.0.jar

./lib/optional/commons-pool-1.6.jar

./lib/optional/snappy-java-1.1.0.1.jar

./lib/optional/log4j-1.2.17.jar

./lib/optional/spring-expression-3.2.8.RELEASE.jar

./lib/optional/snappy-0.2.jar

./lib/optional/activemq-stomp-5.10.0.jar

./lib/optional/activemq-partition-5.10.0.jar

./lib/optional/activemq-jdbc-store-5.10.0.jar

./lib/optional/commons-collections-3.2.1.jar

./lib/optional/activemq-pool-5.10.0.jar

./lib/optional/httpclient-4.2.5.jar

./lib/optional/httpcore-4.2.4.jar

./lib/optional/xstream-1.4.7.jar

./lib/optional/geronimo-j2ee-connector_1.5_spec-2.0.0.jar

./lib/optional/org.linkedin.zookeeper-impl-1.4.0.jar

./lib/optional/hawtbuf-proto-1.10.jar

./lib/optional/proton-j-0.7.jar

./lib/optional/jasypt-spring3-1.9.1.jar

./lib/optional/spring-tx-3.2.8.RELEASE.jar

./lib/optional/shiro-spring-1.2.2.jar

./lib/optional/spring-oxm-3.2.8.RELEASE.jar

./lib/optional/commons-lang-2.6.jar

./lib/optional/leveldb-api-0.6.jar

./lib/optional/commons-codec-1.6.jar

./lib/optional/spring-context-3.2.8.RELEASE.jar

./lib/optional/xpp3-1.1.4c.jar

./lib/activemq-spring-5.10.0.jar

./lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar

./lib/activemq-broker-5.10.0.jar

./lib/activemq-client-5.10.0.jar

./lib/camel/camel-spring-2.13.1.jar

./lib/camel/camel-core-2.13.1.jar

./lib/camel/activemq-camel-5.10.0.jar

./lib/camel/camel-jms-2.13.1.jar

./lib/geronimo-jta_1.0.1B_spec-1.0.1.jar

./lib/web/spring-web-3.2.8.RELEASE.jar

./lib/web/jdom-1.0.jar

./lib/web/jsp-api-2.1-glassfish-2.1.v20100127.jar

./lib/web/jetty-all-server-7.6.9.v20130131.jar

./lib/web/jsp-2.1-glassfish-2.1.v20100127.jar

./lib/web/json-simple-1.1.jar

./lib/web/jetty-websocket-7.6.9.v20130131.jar

./lib/web/spring-webmvc-3.2.8.RELEASE.jar

./lib/web/geronimo-servlet_2.5_spec-1.2.jar

./lib/web/core-3.1.1.jar

./lib/web/jolokia-core-1.2.1.jar

./lib/web/rome-1.0.jar

./lib/insight-log4j-7.2.0.redhat-024-patched.jar

./lib/activemq-jaas-5.10.0.jar

On Tue, Sep 23, 2014 at 9:28 AM, Kevin Burton bur...@spinn3r.com wrote:

 Look at the cause … see below.

 It’s a NoSuchMethodError…

 You have the wrong version of guava sitting around… or one of the .jars
 you’re using is newer and compiled for a newer version of guava :-(

 I know.. not fun.  I think this is an issue regarding 17 removing this
 method but 15 having it and a LOT of libraries use this version.

 But if you have a newer jar using 17 you would have to regress...

  Caused by: java.lang.NoSuchMethodError:
 com.google.common.io.Closeables.closeQuietly(Ljava/io/Closeable;)V
 at org.iq80.leveldb.impl.MMapLogWriter.close(
 MMapLogWriter.java:83)
 at
 

Consumer stops sending messages to DefaultMessageListener

2014-09-23 Thread shaneg
Hi,

We've introduced a HA deployment of active mq 5.9.1 using leveldb and
zookeeper using 3 nodes.  We did a performance run and subsequently our
message consumers have stopped consuming messages but message creation is
working fine.  

We are seeing the dispatched queue count increasing so it appears that the
messages are being delivered to the consumer but are not being delivered to
the listener.  This is happening across all the clients of our queues , its
not local to a single queue.  

I've observed the following in our log files which may or may not be
connected.  The client seems to be continually connecting and reconnecting
using the failover transport (fyi activemq1 is the active node) but I'm not
sure if this is expected behaviour :

Line 25527: 2014-09-23 15:13:22,882 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.failover.FailoverTransport - urlList
connectionList:[tcp://activemq3.cert.api.hco.com:61616,
tcp://activemq2.cert.api.hco.com:61616,
tcp://activemq1.cert.api.hco.com:61616], from:
[tcp://activemq1.cert.api.hco.com:61616,
tcp://activemq2.cert.api.hco.com:61616,
tcp://activemq3.cert.api.hco.com:61616]
Line 25528: 2014-09-23 15:13:22,882 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.failover.FailoverTransport - Attempting  0th 
connect to: tcp://activemq3.cert.api.hco.com:61616
Line 25529: 2014-09-23 15:13:22,884 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.failover.FailoverTransport - Connect fail to:
tcp://activemq3.cert.api.hco.com:61616, reason: java.net.ConnectException:
Connection refused
Line 25530: 2014-09-23 15:13:22,884 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.tcp.TcpTransport - Stopping transport
tcp://activemq3.cert.api.hco.com:61616
Line 25531: 2014-09-23 15:13:22,884 [ActiveMQ Task-1] DEBUG
org.apache.activemq.thread.TaskRunnerFactory - Initialized
TaskRunnerFactory[ActiveMQ Task] using ExecutorService:
java.util.concurrent.ThreadPoolExecutor@75d2eea6[Running, pool size = 0,
active threads = 0, queued tasks = 0, completed tasks = 0]
Line 25532: 2014-09-23 15:13:22,885 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.tcp.TcpTransport - Closed socket
Socket[unconnected]
Line 25533: 2014-09-23 15:13:22,885 [ActiveMQ Task-1] DEBUG
org.apache.activemq.util.ThreadPoolUtils - Forcing shutdown of
ExecutorService: java.util.concurrent.ThreadPoolExecutor@75d2eea6[Running,
pool size = 1, active threads = 1, queued tasks = 0, completed tasks = 0]
Line 25534: 2014-09-23 15:13:22,885 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.failover.FailoverTransport - Attempting  0th 
connect to: tcp://activemq2.cert.api.hco.com:61616
Line 25535: 2014-09-23 15:13:22,886 [ActiveMQ Task-1] DEBUG
org.apache.activemq.transport.failover.FailoverTransport - Connect fail to:
tcp://activemq2.cert.api.hco.com:61616, reason: java.net.ConnectException:
Connection refused
Line 25536: 2014-09-23 15:13:22,887 [ActiveMQ Task-1] DEBUG
org.apache.activemq

This is the failover connection string:

activemq.connectionfactory.brokerurl=failover:(tcp://activemq1.cert.api.hco.com:61616,tcp://activemq2.cert.api.hco.com:61616,tcp://activemq3.cert.api.hco.com:61616)

This is our current spring config:


bean id=amqConnectionFactory
class=org.apache.activemq.ActiveMQConnectionFactory
property name=brokerURL
value=${activemq.connectionfactory.brokerurl}/
property name=userName
value=${activemq.connectionfactory.brokerUser}/
property name=password
value=${activemq.connectionfactory.brokerPassword}/


property name=redeliveryPolicy
  bean class=org.apache.activemq.RedeliveryPolicy
  property name=initialRedeliveryDelay value=1/
   property name=maximumRedeliveries value=2 /
   /bean
/property

/bean



bean id=connectionFactory
class=org.springframework.jms.connection.CachingConnectionFactory
constructor-arg ref=amqConnectionFactory/
property name=sessionCacheSize value=100/
/bean



bean id=inboundContainer
class=org.springframework.jms.listener.DefaultMessageListenerContainer
property name=connectionFactory ref=connectionFactory/
property name=destination ref=inboundQueue/
property name=messageListener ref=inboundQueueListener/
property name=sessionTransacted value=true/
/bean


I'd be interested if anyone else has seen similar behaviour after
introducing HA.  The config above has been in use for about 6 months without
any issue so my assumption thus far is that the issue is HA related but of
course it may be that its exposing an issue with our config.

Thanks 

Shane



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/Consumer-stops-sending-messages-to-DefaultMessageListener-tp4685807.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


ActiveMQ 5.10 LDAP Setup

2014-09-23 Thread nicholas.gray
Hello,I am fairly new to ActiveMQ. Ive been tasked with upgrading our old
ActiveMQ environment. I have installed ActiveMQ 5.10 on a new server. I've
been asked by our team to integrate LDAP with our current AD for our
domain.I've been trying to figure out from the Apache ActiveMQ website, how
to configuration this but I'm having some issues.I was reading this page and
it talks about Apache Directory Server (ldif) and also OpenLDAP (ldif).
http://activemq.apache.org/cached-ldap-authorization-module.htmlWould
someone be able to point me in the right direction and give a little advice
on how to set this up?Muchley appreciated.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/ActiveMQ-5-10-LDAP-Setup-tp4685808.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Replicated LevelDB store issues

2014-09-23 Thread Justin Reock
Remove the ³pax-url-aether-1.5.2.jar² from /lib to resolve this issue.

Thanks,

Justin Reock
OpenLogic
Www.openlogic.com

On 9/23/14, 12:31 PM, Kevin Burton bur...@spinn3r.com wrote:

Š and I seem to recall that I fixed this and had to rm a jar or move it to
a specific directory.  But I¹ve long forgotten which one :-( Š.

So to help you resolve this here are all the .jars in my activemq 5.10
installŠ you can just diff your .jars and probably figure out what¹s
wrong.


./bin/wrapper.jar

./bin/activemq.jar

./activemq-all-5.10.0.jar

./lib/activemq-web-5.10.0.jar

./lib/activemq-kahadb-store-5.10.0.jar

./lib/slf4j-api-1.7.5.jar

./lib/activemq-openwire-legacy-5.10.0.jar

./lib/activemq-console-5.10.0.jar

./lib/jcl-over-slf4j-1.7.5.jar

./lib/hawtbuf-1.10.jar

./lib/insight-log-core-7.2.0.redhat-024.jar

./lib/geronimo-jms_1.1_spec-1.1.1.jar

./lib/activemq-protobuf-1.1.jar

./lib/extra/mqtt-client-1.10.jar

./lib/optional/jaxb2-basics-runtime-0.6.4.jar

./lib/optional/spring-jms-3.2.8.RELEASE.jar

./lib/optional/jasypt-1.9.1.jar

./lib/optional/xbean-spring-3.16.jar

./lib/optional/guava-12.0.jar

./lib/optional/commons-beanutils-1.8.3.jar

./lib/optional/activemq-shiro-5.10.0.jar

./lib/optional/activemq-log4j-appender-5.10.0.jar

./lib/optional/jackson-mapper-asl-1.9.12.jar

./lib/optional/spring-aop-3.2.8.RELEASE.jar

./lib/optional/leveldb-0.6.jar

./lib/optional/org.apache.servicemix.bundles.josql-1.5_5.jar

./lib/optional/hawtjni-runtime-1.9.jar

./lib/optional/spring-core-3.2.8.RELEASE.jar

./lib/optional/hawtdispatch-transport-1.21.jar

./lib/optional/org.linkedin.util-core-1.4.0.jar

./lib/optional/activemq-runtime-config-5.10.0.jar

./lib/optional/proton-jms-0.7.jar

./lib/optional/activeio-core-3.1.4.jar

./lib/optional/slf4j-log4j12-1.7.5.jar

./lib/optional/shiro-core-1.2.2.jar

./lib/optional/jackson-core-asl-1.9.12.jar

./lib/optional/leveldbjni-1.8.jar

./lib/optional/jmdns-3.4.1.jar

./lib/optional/hawtdispatch-1.21.jar

./lib/optional/spring-beans-3.2.8.RELEASE.jar

./lib/optional/activemq-amqp-5.10.0.jar

./lib/optional/activemq-jms-pool-5.10.0.jar

./lib/optional/zookeeper-3.4.5.jar

./lib/optional/commons-net-3.3.jar

./lib/optional/jettison-1.3.5.jar

./lib/optional/velocity-1.7.jar

./lib/optional/activemq-leveldb-store-5.10.0.jar

./lib/optional/activemq-mqtt-5.10.0.jar

./lib/optional/hawtdispatch-scala-2.11-1.21.jar

./lib/optional/commons-dbcp-1.4.jar

./lib/optional/scala-library-2.11.0.jar

./lib/optional/activemq-http-5.10.0.jar

./lib/optional/commons-pool-1.6.jar

./lib/optional/snappy-java-1.1.0.1.jar

./lib/optional/log4j-1.2.17.jar

./lib/optional/spring-expression-3.2.8.RELEASE.jar

./lib/optional/snappy-0.2.jar

./lib/optional/activemq-stomp-5.10.0.jar

./lib/optional/activemq-partition-5.10.0.jar

./lib/optional/activemq-jdbc-store-5.10.0.jar

./lib/optional/commons-collections-3.2.1.jar

./lib/optional/activemq-pool-5.10.0.jar

./lib/optional/httpclient-4.2.5.jar

./lib/optional/httpcore-4.2.4.jar

./lib/optional/xstream-1.4.7.jar

./lib/optional/geronimo-j2ee-connector_1.5_spec-2.0.0.jar

./lib/optional/org.linkedin.zookeeper-impl-1.4.0.jar

./lib/optional/hawtbuf-proto-1.10.jar

./lib/optional/proton-j-0.7.jar

./lib/optional/jasypt-spring3-1.9.1.jar

./lib/optional/spring-tx-3.2.8.RELEASE.jar

./lib/optional/shiro-spring-1.2.2.jar

./lib/optional/spring-oxm-3.2.8.RELEASE.jar

./lib/optional/commons-lang-2.6.jar

./lib/optional/leveldb-api-0.6.jar

./lib/optional/commons-codec-1.6.jar

./lib/optional/spring-context-3.2.8.RELEASE.jar

./lib/optional/xpp3-1.1.4c.jar

./lib/activemq-spring-5.10.0.jar

./lib/geronimo-j2ee-management_1.1_spec-1.0.1.jar

./lib/activemq-broker-5.10.0.jar

./lib/activemq-client-5.10.0.jar

./lib/camel/camel-spring-2.13.1.jar

./lib/camel/camel-core-2.13.1.jar

./lib/camel/activemq-camel-5.10.0.jar

./lib/camel/camel-jms-2.13.1.jar

./lib/geronimo-jta_1.0.1B_spec-1.0.1.jar

./lib/web/spring-web-3.2.8.RELEASE.jar

./lib/web/jdom-1.0.jar

./lib/web/jsp-api-2.1-glassfish-2.1.v20100127.jar

./lib/web/jetty-all-server-7.6.9.v20130131.jar

./lib/web/jsp-2.1-glassfish-2.1.v20100127.jar

./lib/web/json-simple-1.1.jar

./lib/web/jetty-websocket-7.6.9.v20130131.jar

./lib/web/spring-webmvc-3.2.8.RELEASE.jar

./lib/web/geronimo-servlet_2.5_spec-1.2.jar

./lib/web/core-3.1.1.jar

./lib/web/jolokia-core-1.2.1.jar

./lib/web/rome-1.0.jar

./lib/insight-log4j-7.2.0.redhat-024-patched.jar

./lib/activemq-jaas-5.10.0.jar

On Tue, Sep 23, 2014 at 9:28 AM, Kevin Burton bur...@spinn3r.com wrote:

 Look at the cause Š see below.

 It¹s a NoSuchMethodErrorŠ

 You have the wrong version of guava sitting aroundŠ or one of the .jars
 you¹re using is newer and compiled for a newer version of guava :-(

 I know.. not fun.  I think this is an issue regarding 17 removing this
 method but 15 having it and a LOT of libraries use this version.

 But if you have a newer jar using 17 you would have to regress...

  Caused by: java.lang.NoSuchMethodError:
 

Permission to edit wiki - add NMS AMQP provider details

2014-09-23 Thread Chuck Rolke
Hi,

I'd like to get some wiki karma so that I may update the NMS Sub Project pages. 
The AMQP provider is available but it will not be used until it gets more 
advertising.

I am a committer at Apache http://people.apache.org/committer-index.html#C

 SVN id  : chug
 Name: Charles E. Rolke
 Confluence user : chug

Regards,
Chuck


Re: Permission to edit wiki - add NMS AMQP provider details

2014-09-23 Thread Timothy Bish

On 09/23/2014 02:58 PM, Chuck Rolke wrote:

Hi,

I'd like to get some wiki karma so that I may update the NMS Sub Project pages. 
The AMQP provider is available but it will not be used until it gets more 
advertising.

I am a committer at Apache http://people.apache.org/committer-index.html#C

  SVN id  : chug
  Name: Charles E. Rolke
  Confluence user : chug

Regards,
Chuck


Should have access now, let me know if not.  Thanks!

--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
skype: tabish121 | twitter: @tabish121
blog: http://timbish.blogspot.com/



What all problems with broker or network can be detected using Transport Listener?

2014-09-23 Thread bansalp
Hi,

What all problems with broker or network can be detected using Transport
Listener?

I am using failover uri with master/slave architecture. I want my clients to
get notify if there is any problem with connection from client to broker.
Though as soon as there will be problem with primary, failover will takeover
and vice versa, but I want my client to know that there was some problem.

I know I can implement TransportListener and set it to my connection..but
what all can be detected using TransportListener?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/What-all-problems-with-broker-or-network-can-be-detected-using-Transport-Listener-tp4685815.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.