Hi Chago/James,
you are right. I had same problem and because of this i am not able to
use latest tech. provided by Activemq and jetty(Continuation). I am facing
only one issue that is whenever client do polling that time i am not getting
any consumer for that client so even if we have data
Please set the inactivity flag on your broker as
wireFormat.maxInactivityDuration=-1
http://activemq.apache.org/configuring-wire-formats.html
-Original Message-
From: tmccauley [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 25, 2007 9:33 AM
To: users@activemq.apache.
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I'm experiencing the same or a very similar problem, although it is on
version 4.1.1, oddly enough.
In my case the broker sends messages to a durable topic with two consumers.
They both receive the message just fine.
If I then re-start the broker while leaving the clients running, the second
cli
I am getting
[09:15:54.910] Async exception with no exception listener:
org.apache.activemq.transport.InactivityIOException: Channel was inactive
for too long.
[09:15:54.910] org.apache.activemq.transport.InactivityIOException: Channel
was inactive for too long.
on a Listener running under Li
Hi all
I'm using network of brokers config with 2 brokers
After some time one of the queues on one broker stopped dispatching messages
to its 2 consumers, log files contained no errors and any kind of strange
behavior, 3 other queues on the same broker were just fine
my config file for brokers is
Hi, James - thanks for the quick reply.
I had not started it in persistent mode and I was not statically defining
the consumer queue. However, upon doing that the same results apply.
I *should* be able to start this broker, send messages to the topic, bring
down the broker, bring up the broker,
No i am not using Spring and YES, I have also tried it without "failover".
The result is the same.
TOPPER_HARLEY wrote:
>
> Hi,
> Are you using Spring? Can you use an
> org.apache.activemq.xbean.BrokerFactoryBean?
>
> This will create and start the broker and just leave it there in the VM.
>
I know others that have had this problem running with the 4.1.x series. Is
that the case for you?
-- jim
JigarP wrote:
>
> Hi ,
>
>I am using ActiveMQ/AJAX for my web based application. I have
> integrated ajax successfully in my application but getting below issue
> sometime.
>
> 1) I s
http://www.plope.com/software/supervisor2/
Roger Hoover <[EMAIL PROTECTED]> wrote: We're planning to use ActiveMQ as an
asynchronous messaging layer between
daemon processes written in various languages (connecting to ActiveMQ via
STOMP). We need a convenient way to launch, shutdown, or restart
Can you upgrade to 5.0? I have tried to help others with the same problem,
but it worked for them when they upgraded to latest code.
-- jim
bbuffone wrote:
>
> I have started using Active MQ to build an Ajax application and currently
> running into problems. When I publish messages from the
Can you provide more detail regarding the problem. I assume you are using the
amq.js file? If you are, the browser is constantly polling the server for
data. If there is a connection problem, the browser is the first to know
about it. In these cases, reconnect logic will have to exist in the brows
Hi all!
I want to connect some Java apps and a nearby MSMQ instance. In the
past we put in place a solution using the Level-8 'Geneva Message Queue
Connector', which provided a (slightly hairy) Java client.
I'd like to put something in place using the amq.net stuff to provide
interoperability wi
On 24/09/2007, dantelope <[EMAIL PROTECTED]> wrote:
>
> The following test produces unexpected results:
>
> 1) Start a broker with a statically defined destination topic called
> VirtualTopic.FOO
> 2) Start a consumer listening to Consumer.A.VirtualTopic.FOO
> 3) Start a sender and send N messages
On 25/09/2007, mythz <[EMAIL PROTECTED]> wrote:
>
> Is it possible to have a DLQ for each Queue/Topic? rather than all messages
> going to ActiveMQ.DLQ?
> i.e. getting poison messages for Test.Queue go to DLQ.Test.Queue?
Absolutely. Its just a case of specifying the strategy to use...
http://acti
Is it possible to have a DLQ for each Queue/Topic? rather than all messages
going to ActiveMQ.DLQ?
i.e. getting poison messages for Test.Queue go to DLQ.Test.Queue?
--
View this message in context:
http://www.nabble.com/Is-it-possible-to-have-a-DLQ-for-each-Queue-Topic--tf4514966s2354.html#a1287
On 23/09/2007, mythz <[EMAIL PROTECTED]> wrote:
>
> How can I check that the broker I'm listening on is still running?
>
> I have a master slave setup where if master broker goes down one of the
> slaves takes over. The problem is that the listener does not reconnect to
> the new master broker.
>
>
Have you tried using the Java Service Wrapper tool in the binary
distro. e.g. go into activemq/bin/linux and see the wrapper scripts;
it lets you setup daemons and use unix signals to
monitor/start/stop/restart etc
On 24/09/2007, Roger Hoover <[EMAIL PROTECTED]> wrote:
> We're planning to use Acti
mythz wrote:
>
> How can I check that the broker I'm listening on is still running?
>
> I have a master slave setup where if master broker goes down one of the
> slaves takes over. The problem is that the listener does not reconnect to
> the new master broker.
>
> So how can the listener check
Hi,
Roger Hoover wrote:
>
> We need a convenient way to launch, shutdown, or restart the
> daemons and supervise them (restart them if they die). We also want to
> start multiple copies of daemon process, all listening to the same queue.
>
> Can anyone recommend any free/open-source tools for
22 matches
Mail list logo