On Thu, Oct 25, 2012 at 10:44 PM, Christian Posta
wrote:
> You don't have the activemq-camel jar on the classpath properly.
>
> Add it to the camel/WEB-INF/lib folder
>
There may be other JARs as well, such as scalete, scala et all.
You can download the WAR from maven central, and then extract i
Thanks, i'm working on it.
On Oct 26, 2012, at 4:12 AM, ceposta [via ActiveMQ]
wrote:
> Charles,
> wireFormat.maxInactivityDuration won't work for MQTT
> Can you try on the latest snapshots using the KeepAlive setting in the
> client?
>
> On Mon, Oct 22, 2012 at 1:20 AM, Charles Wang <[hid
There is 1GB durable topic messages left in KahaDB files ,with 1 mb size per
message.Then start 5 durable subscribers simultaneously to receive the
stored messages,the Broker run out of memory immediately. There's one way to
prevent this from happening,that is configure the size of parameter
durabl
What version of activemq are you using?
On Fri, Oct 12, 2012 at 12:44 PM, ajCohen wrote:
> Hi All,
>
> For some reason I cannot get my message consumer to consume an
> 'ActiveMQ.Advisory.MasterBroker' advisory message. When the master is
> killed, the slave takes over and I can see in the slave
Actually, I just tried it with trunk and 5.7.0.
It works fine. Make sure you go back to the /admin path (after going into
slave, it will be at /admin/slave.jsp... can't just refresh that page...
gotta manually go back to admin)
Let me know if that works. We can still open a jira to make it a littl
It should come back from slave mode to be in master mode.
Can you open a JIRA for that?
On Mon, Oct 22, 2012 at 1:57 AM, orackbahama wrote:
> Hi,
> when operating 2 ActiveMQ instances in master/slave mode, the webconsole of
> the master is working as expected and displays all relevant values. Th
You don't have the activemq-camel jar on the classpath properly.
Add it to the camel/WEB-INF/lib folder
and add this to your WebAppContext declaration:
**
Can you post the config for your brokers?
For the messages to transfer from a broker to another broker, there has to
be demand, ie, a consumer for the destination on the other broker.
On Mon, Oct 22, 2012 at 2:03 PM, newUser06 wrote:
> Hi,
> I am new to activeMQ and i am trying to setup 2 instan
enable debug logging of
org.apache.activemq.store.kahadb.MessageDatabase and you will get a
full stack trace to the source of the :java.io.EOFException
That will give us a hint as to where the problem is.
On 25 October 2012 17:31, James Green wrote:
> Each time we start this broker we're gettin
i'm using the 5.8.0-snapshot, my setting:
And i got:
2012-10-22 16:10:45,674 | DEBUG | SampleJavaV3_subscribe MQTT Connection
using heart beat of 60 secs |
org.apache.activemq.transport.mqtt.MQTTProtocolConverter | ActiveMQ
Transport: tcp:///124.127.108.134:7442@1883
2012-10-22 16:10:45,699 |
Hi,
when operating 2 ActiveMQ instances in master/slave mode, the webconsole of
the master is working as expected and displays all relevant values. The
webconsole of the slave now (in 5.7.0) displays "Slave mode" - correct at
this time.
But when the master goes off or is broken, the slave webconsol
Hi,
I am new to activeMQ and i am trying to setup 2 instances of activeMQ in the
same VM using network of brokers using discovery. I am using spring to
configure the brokers and they are 2 webapps on the same tomcat
The following logs mentions that connection has been established. But the
message
Hi all,
I tried to manually add the camel web console to activemq 5.7. For that I
was doing the following steps:
- *I extracted the camel-web.war inside of the
camel-web-standalone-2.10.1.jar into webapps/camel*
- *in the conf/jett.xml I added the webapp:*
Thanks.
These postings hits the Mark Richard's article right on the bull's eye.
On Thu, Oct 25, 2012 at 6:01 AM, Christian Posta
wrote:
> Sean K,
> Looks like you already got a response from James :)
> But here's at least one discussion that took place a while ago about this
> very subject:
>
>
Hello,
We are facing a behavior where subscribers' Pending Queue Size
increases, it seems that no ACKs are dispatched and flow ratio decreases
almost to zero.
Our topology is somehow peculiar:
We have several places, each one containing multiple machines.
Each machine has a local broker with a
>
> One more question, the web-console should display a queue or a topic only
> after there is a client connected to it, or always after it's declared as a
> Resource in tomee.xml?
Yep, that sounds correct.
On Thu, Oct 25, 2012 at 12:42 AM, cristisor wrote:
> Good morning,
>
> All my issues ge
Sean K,
Looks like you already got a response from James :)
But here's at least one discussion that took place a while ago about this
very subject:
http://www.jroller.com/RickHigh/entry/amqp_versus_jms
On Wed, Oct 24, 2012 at 3:37 PM, Sean K wrote:
> Has anyone responded to this article writt
Afraid not, the store usage manager is a broker singelton, so is is
shared by all of the instances of kahadb. The code that checks usage
is unaware of the multiple stores atm.
On 25 October 2012 09:10, Gilles Harloux wrote:
> Using mKahaDB, is there a way to set usage limits per individual
> kaha
Thanks for the validation. Will this be the case from now on? For example,
if one was 5.6 and the other 5.7 would that still be a problem or is it just
a problem between mixing 5.5.1 and earlier versions with 5.6 or later? The
reason we use a network of brokers is to allow communications between
http://www.wmrichards.com/amqp.pdf
On Wed, Oct 24, 2012 at 11:58 PM, Claus Ibsen wrote:
> Hi
>
> Do you have a link to the article?
>
>
> On Thu, Oct 25, 2012 at 12:37 AM, Sean K wrote:
>> Has anyone responded to this article written by Mark Richards about
>> AMQP and JMS (includes ActiveMQ)?
Good morning,
All my issues get solved after adding "DataSource =". This is my new
JMSAdapter, with the broker configuration:
BrokerXmlConfig =
broker:(tcp://localhost:61616)?persistent=false&useJmx=true
ServerUrl = tcp://localhost:61616
Dat
On 24 October 2012 23:37, Sean K wrote:
> Has anyone responded to this article written by Mark Richards about
> AMQP and JMS (includes ActiveMQ)?
>
> Specifically:
>
>
> "This means that message clients using AMQP are completely agnostic as
> to which AMQP clients API or
> AMQP message broker you
22 matches
Mail list logo
