> I've tried setting connectorHost in the managementContext to both the FQDN
> and the internal 10.* IP, and I've also tried different ports, but no
> matter what I try I always see this exception a few seconds after I start
> up ActiveMQ. Any ideas on this one?
Yup in that case it's simple, you
Thanks, Timothy. I've been using the public IP like that but it hasn't
helped. I actually just noticed the following exception that I missed
initially:
Failed to start JMX connector Cannot bind to URL
[rmi://localhost:1199/jmxrmi]: javax.naming.NoPermissionException [Root
exception is java.rmi.
> I'm trying to enable JMX access to ActiveMQ over an SSL connection to a
> server located in Amazon's cloud but I'm not having any luck. We have
> existing Tomcat applications that I've successfully set up with JMX & SSL
> by specifying all the following on the java command line:
Hi Bruce,
I'm
Hi all,
I'm trying to enable JMX access to ActiveMQ over an SSL connection to a
server located in Amazon's cloud but I'm not having any luck. We have
existing Tomcat applications that I've successfully set up with JMX & SSL
by specifying all the following on the java command line:
-Dcom.sun.mana
> Clients connect to tls-connector connector on port 51619 and point to the
> first broker.
>
> After few seconds they switch misteriously to the nio connector.
This makes sense to me.
I think if you look at the updateClusterClients behaviour you will see that the
broker will announce other net
On 11/19/2013 10:52 AM, Jose María Zaragoza wrote:
Hello:
I'm using AMQ 5.8 and I've got some questions about PooledConnectionFactory:
This is my testing configuration , running in JVM 6
// ConnectionFactory
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("failover
Hello:
I'm using AMQ 5.8 and I've got some questions about PooledConnectionFactory:
This is my testing configuration , running in JVM 6
// ConnectionFactory
ActiveMQConnectionFactory connectionFactory = new
ActiveMQConnectionFactory("failover:(tcp://broker1:61616?connectionTimeout=3000,tcp://br
Yep that helps a little. So that seems like an error on the slave.
Where there any errors on the master?
On Mon, Nov 18, 2013 at 5:37 PM, kal123 wrote:
>
> Today after the exception occurred, I updated the activemq start script to
> redirect output to file instead of null and at the start i see
On 11/18/2013 06:30 PM, xbhanu wrote:
Am I correct to assume that Apache Qpid is 100% AMQP compliant but ActiveMQ
is still in the process of adapting AMQP?
I wouldn't put it in those terms.
Qpid is really an umbrella project for several different components (as
is ActiveMQ) many/most of which
On 11/19/2013 05:18 AM, xbhanu wrote:
Using the qpid implemented client with JNDI and creating a connection factory
with something like
connectionfactory.qpidConnectionfactory =
amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672' (as
provided in qpid client examples) still doesnt w
Hi
I am trying this code
log.debug(this+" : Creating Connection for "+op.name());
ConnectionFactory connectionFactory =
this.baseService.getConnectionFactory();
connection = connectionFactory.createConnection();
connection.start();
log.
I just updated https://issues.apache.org/jira/browse/AMQ-4485 with a
fix which may be relevant, it is relevant. If you are experiencing
that issue then using a policyEntry useCache="false" will avoid it.
You will need to wait a bit to get a 5.10 SNAPSHOT with that fix in it
- the build is pending:
12 matches
Mail list logo
