All,
I have a simple bridge between ActiveMQ and TibcoEMS.
There are 2 routes.
1st (Camel) Route moves messages into ActiveMQ Queue. (thisroute reads
messages from Disk and publishes to ActiveMQ).
2nd (Camel) Route consumes messages from ActiveMQ and publish to a Topic in
TibcoEMS.
For both the
Hi,
Can some clarify the query I had raised in this post. This is becoming a
show stopper for us.
Would appreciate if some one can share their experience.
regards,
D
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-encrypt-password-in-broker-config-xml-and-ra-xml-
Hi,
Does any one have suggestions for my above query?
regards
D
--
View this message in context:
http://activemq.2283324.n4.nabble.com/How-to-encrypt-password-in-broker-config-xml-and-ra-xml-tp4681449p4681497.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
If I look more closely at the ra.xml
- the following section handles the password credentials
BasicPassword
javax.resource.spi.security.PasswordCredential
As per the connection_1_6.xsd (used by ra.xml)
The credential-interfaceTyp
Hi,
I am now able to use encrypt password as per:
http://activemq.apache.org/encrypted-passwords.html
As described earlier I run ActiveMQ integrated with Jboss.
My ejbs pick up the ActiveMQ connection from ra.xml - where the password is
specified under a config-property
The
Hi,
Thanks - I am already using security-domain for encrypting my database
connection password (in Jboss datasource).
This datasource is referred in broker-config.xml as a JNDI - so activeMQ
uses this encrypted password when it connects to the database.
My concern is the cleartext password I am
Hi,
Thanks for the link.
I am using ActiveMQ+Jboss (Active MQ integrated with Jboss 5.1.0)
I don't even find activemq-security.xml.
Am I missing something or should I store the algorithm & password in a
different file?
regards
D
--
View this message in context:
http://activemq.2283324.n4.nab
Hi,
I am using simpleAuthenticationPlugin in my broker-config.xml as shown
I also set password in ra.xml as shown below
The default password that will be used to log the
default user into the ActiveMQ server.
Password
Hi,I am using simpleAuthenticationPlugin in my broker-config.xml as shown
I also set password in ra.xml as shown belowThe default
password that will be used to log the default user into the ActiveMQ server.
Password
Would appreciate if you can clarify what changeAutoCommitAllowed="false"
means?
The API has an explanation but its unclear.
Does this parameter ensure - SQL Server's default Autocommit is overwritten
- and the actual commit is done by ActiveMQ's datasource?
regards
D
--
View this message in c
Hi,
I upgraded to ActiveMQ 5.8.0.
Added changeAutoCommitAllowed="false" to broker-config.xml - as shown below
Now I don't see the exceptions stated above.
However on Jboss start up - I see the following
2013-12-11 16:08:40,865 INFO
[org.apache.activemq.store.kahadb.plist.
https://issues.apache.org/jira/browse/AMQ-711
The issue I am facing is same as mentioned above
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Auto-commit-issue-with-SQL-Server-ActiveMQ-tp4675355p4675391.html
Sent from the ActiveMQ - User mailing list archive at Nabble.c
One thing to add - I am trying to send messages to activeMQ within an XA
transaction.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Auto-commit-issue-with-SQL-Server-ActiveMQ-tp4675355p4675356.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
All,
I am using ActiveMQ 5.6.0 SQL Server 2008 is used in backend. With SQL
Server -
I get the following exception
2013-12-11 09:17:15,085 WARN
[org.apache.activemq.store.jdbc.JDBCPersistenceAdapter] (ActiveMQ Transport:
tcp:///127.0.0.1:62351) Commit failed: commit() should not be called whil
All,I am using ActiveMQ 5.6.0SQL Server 2008 is used in backend.With SQL
Server - I get the following exception2013-12-11 09:17:15,085 WARN
[org.apache.activemq.store.jdbc.JDBCPersistenceAdapter] (ActiveMQ Transport:
tcp:///127.0.0.1:62351) Commit failed: commit() should not be called while
in aut
All,
I am running ActiveMQ (5.6.0) integrated in JBoss. I am also using Apache
Camel.
ActiveMQ runs in a master/slave fashion.
To ensure failover of Apache Camel routes, I have implemented strategy as
shown below
http://www.liquid-reality.de/display/liquid/2011/11/11/Hot+Standby+failover+for+Apac
Hi,
I am running activeMQ+Jboss in an integrated mode.
Issue I am having is ActiveMQ.rar gets deployed before by JNDI-datasource
gets deployed.
My broker-config.xml looks like this
.
.
The data source
Hi,I am running activeMQ+Jboss in an integrated mode.issue I am having is
ActiveMQ.rar gets deployed before by JNDI-datasource gets deployed.My
broker-config.xml looks like this.
.The data source is in a seperate xml fi
Just re-read your earlier message
"you won't be able to listen to that on the slave, cause you won't be able
to connect! "
That's not true, since my application does connect because it has a
fail-over, what i does not know is the IP address at run-time to connect to
JMX.
The topic itself should b
Hi,
Thanks.
Another idea I am thinking is
"broadcast" a message to a MDB, with its IPAddress as soon as it acquires a
lock is acquired on the Database.
I am following a strategy as shown below
http://www.liquid-reality.de/display/liquid/2011/11/11/Hot+Standby+failover+for+Apache+Camel+routes
for
Hi,
May be I am not explaining properly.
My app connects to the Master or Slave based on the HostName/IP-Address.
Prior to clustering my app always connected to localhost/default-JMX-port
DEFAULT_MESSAGE_BUS_JMX_HOST = "localhost";
DEFAULT_MESSAGE_BUS_JMX_PORT = 1;
Now with clustering my sl
Thanks,
As per
http://activemq.apache.org/advisory-message.html
I see that
ActiveMQ.Advisory.MasterBroker
is set to True (enabled by default).
I have also added the following in my broker-config.xml
But I don't even see the Queue ActiveMQ.Advisory.MasterBroker in my JMX
con
Hi,
My architecture uses Jboss+ActiveMQ (in integrated mode)
We have achieved HA (high availability) & HS (High Scalablity).
A high level design looks like the below
http://activemq.2283324.n4.nabble.com/ActiveMQ-Clustered-JBoss-and-JDBC-Master-Slave-td2348023.html#a2348028
Query is - when the p
All,I am have a jdbc-master-slave set up as shown in the below
link.http://activemq.apache.org/jdbc-master-slave.htmlEverything works fine
as expected, the node that starts first grabs an exclusive lock on the
database and it becomes the master.At this point the slave node attempts to
connect every
Thanks, much clear now.
For the benefit to other users who may be attempting to do the same.
Following files will need to be amended
\server\default\deploy\reform-jms-ds.xml
\server\default\deploy\activemq-ra.rar\broker-config.xml
\server\default\deploy\activemq-ra.rar\META-INF\ra.xml
http://rab
Thanks!
I can confirm that my brokers are able to Discover each other.
But from your earlier statements
'you'll won't be able to share databases'
'they would all have their own persistence stores'
I see no reason why this won't work - so is this something not-recommended
by activeMQ? becuase of
I so see the artefact static in the following location:
activemq-ra.rar\activemq-core-5.6.0.jar\*META-INF\services\org\apache\activemq\transport\/discoveryagent/\*
which is different from what I see in the exception
Caused by: java.io.IOException: Could not find factory class for resource:
META-
Thanks,
I am getting the following exception when I start Jboss (in node 1)
2013-06-20 15:23:21,775 ERROR [org.apache.activemq.broker.BrokerService]
(Starting ActiveMQ Broker) Failed to start ActiveMQ JMS Message Broker
(jboss-activemq-broker1, null). Reason: java.io.IOException: Transport
Connec
Thanks for the reply.
I am reading the explanation under link(s)
http://activemq.apache.org/clustering.html
and
http://activemq.apache.org/static-transport-reference.html
Am I right in understanding that static-transport-reference is to be set at
the Broker level? to enable one broker understand
As per this link
http://activemq.apache.org/can-two-brokers-share-the-same-database.html
It appears the recommendation is not to share database.
This link recommends another strategy
http://activemq.apache.org/jdbc-master-slave.html
But this will work if I were to follow "Clustered Singleton Ser
All,
I have JBoss+activeMQ running in an integrated mode.
Originally the plan was to have a single instance of JBoss running.
now we plan to run this in a clustered environment.
As per
http://docs.jboss.org/jbossclustering/cluster_guide/5.1/html-single/#deployment.chapt
I am going ahead with the
Hi Christian,
Correction to what I stated earlier.
In this route with "producerWindowSize" set in broker-config.xml
MICS
There were messages Queued in DLQ and (memory limit has been exceeded or
very close to exceeding)
The above rout
Not sure why consumers are blocked. Are they acking?
---
No, they are not acking at all, they seem to be blocked.
I ran 2 sets of tests.
For both tests following is the route set up
MICS
Test1 :
In this test,
Hi,
In our system, Camel produces JMS messages from integrated endpoints, which
are consumed by EJB MDBs.
The EJB application in-turn produces new JMS messages, which are consumed by
Camel to send to other integrated endpoints (eg. WebSphere MQ).
We use transacted routes, and Atomikos as XA
Thanks Christian,
On
'Maybe just write a camel route to put those messages into a database for
future analysis? '
- Will definitely consider that.
Does this also mean - I am fundamentally 'not' using DLQ in Message-Broker
for what they are actually meant for?
i.e. is it always a bad idea to leav
Hi Christian,
Prior to introducing the 'producer window' both the producer and consumer
were blocked
(If I don't consume from my DLQ) - which was expected.
The temporary work-around I have is to simply increase the memoryUsage to a
higher value
and also ensure messages are not queued up in active
All,
For a Topic with multiple consumers, if one of the client is slow, it slows
down other subscribers.
The recommended approach is given here
http://activemq.apache.org/slow-consumer-handling.html
-> approach recommended is "discarding old messages"
But I don't want to discard old messages ei
Also, - we are using JDBC store to persist messages. Does this mean messages
that are persisted will also be held up in memory/cache? i.e. will that also
be occupying the broker memory?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Query-around-ActiveMQ-DLQ-tp4666277p4
Hi,
Also what was noticed in my test is that - when the CursorMemoryUsage
reached/exceeded the limit (64MB), the producer was blocked (which is
understandable) - but it was surprising to note that consumer was also
blocked (i.e. the camel route that pulled messages from the Queue also
froze) - is
Hi,
I see the max memory size as 64MB in the JMX console, each queue has the
size set to 64MB (shown in bytes)
So I must ensure that DeQueue is also purged at regular intervals?
If yes, is there any default purge strategy recommended?
I also notice that messages are in the Queue and also in the
All,
I am facing the following incident -
Architecture setup: ActiveMQ running in JBoss; Camel used as MessageBus
1. High volume of messages are published to a Queue
2. My application consumes them and if they fail validation they are
DeQueued (goes to ActiveMQ.DLQ)
3. I can also see the message
Hi,
I am running activeMQ broker + JBoss in an integrated environment.
I notice that I do not see Object name filer: org.apache.activemq
from JBoss jmx-console
Can some one point out if there is any config change needed to enable this?
Note: I do see object name: activemq.queue and this lists ou
Thanks,
in addition, when there is an exception in my system, I store the message in
a DLQ and also persist the message in Database.
What I noticed is -
* for every exception caught we were pushing the message to DeQueue
* the DeQueue also had a limit of 64MB
* if that limit got crossed , camel
Hi,
In our system, the activeMQ Queue's MemoryLimit is 64MB (default).
We use the default message cursor (Store based).
We noticed that if the consumer were to publish multiple messages whose size
exceed 100+MB, we motice that the consumer freezes indefintely.
(I keep seeing this log) - the
Hi,
In our system, the activeMQ Queue's MemoryLimit is 64MB (default).
We use the default message cursor (Store based).
We noticed that if the consumer were to publish multiple messages whose size
exceed 100+MB, we motice that the consumer freezes indefintely.
(I keep seeing this log) - the bloc
All,
In the architecture I am working in, messages come into a ActiveMQ Queue
from IBM MQ.
An application/consumer polls the messages from this active MQ Queue.
Messages from IBM MQ have a priority field set.
By default ActiveMQ ignores the priority, so I have added the
prioritization-destinatio
46 matches
Mail list logo
