On 3-4-2008 7:47, Joel Poloney wrote:
1. I have a consumer in a while(1) { //consume } fashion. That would
basically run forever. As I understand it, this is the way most web servers
work (at the core, core level). In this model, I would have to make sure
that the consumer was always running
On Wed, Apr 2, 2008 at 11:39 PM, Arjen van der Meijden
[EMAIL PROTECTED] wrote:
I would go with 1. But you may want to add some control-code to ensure you
can easily and cleanly kill your scripts. In my code, I added a few signal
handlers, so the consumer first finishes its most recent job
On 3-4-2008 8:50, Joel Poloney wrote:
Is your kill-message on every call? Or is that only when you manually
interrupt it? I'm wondering if you changed the Stomp-implementation such
that if you've consumed all of the messages (and it's waiting for a new
message to come through), it automatically
On Thu, Apr 3, 2008 at 12:19 AM, Arjen van der Meijden
[EMAIL PROTECTED] wrote:
My consumer just consumes a message, processes it and then goes on waiting
for another one. So if that message happens to be a 'kill'-message, it dies
(if the message was sent after the consumer started).
When I
Dear All,
To correlate between client users and actual connections we need to pass
info to the connection.
General Setup:
1. Server is listening on topic.subject1 advisory topic to get
connection/disconnect information.
2. Client user2 connects to broker [server] to consume topic.subject1
Dear All,
Bug description:
1. Server listen to advisory messages
2. Client connect == advisory messages are sent correctly.
3. Client connection.stop === no advisory message :-(
Solution:
3update. Client connection.close connection.stop
== advisory messages are sent correctly.
Hi,
I have started broker in one machine try to connect it from listener in
another machine, I am getting following error
In machine where broker is running
[java] 13:52:11 ERROR Could not accept connection : Connection reset by
peer: socket write error
Hi everybody,
I´ve been testing activeMQ and it´s pretty nice but I have a doubt: Is the
publish´s performance different using ajax of directly on java?
I made a send and a receive messages application test. When I opened one
receive application in all browsers I have (FF, IE7, Safari 3, IE6) and
Hi all,
Here is the setup and the statistics from a test run.
Tools:-
Spring2.5.2,ApacheActiveMQ4.1.1
Spring config same on both producer and consumers:
bean id=connectionFactory
class=org.apache.activemq.pool.PooledConnectionFactory
destroy-method=stop
property
Does it work when you omit the connectionTimeout property in the transport
URL?
--
View this message in context:
http://www.nabble.com/Unable-to-connect-to-remote-broker-tp16467328s2354p16467541.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi
I have tried both with and without connectionTimeout property in the
transport URL
but it does not work, I think there is some firewall issue in the network
Iam using (just a thought)
Thanks
Akhil
tmi wrote:
Does it work when you omit the connectionTimeout property in the transport
URL?
Thanks for your response Oleg.
Actually I wanted to get notified on the client side (C#) if the connection
with ActiveMQ is lost because of any reason like the ActiveMQ server is down
or network not available.
I found that if we attach an event handler for ExceptionListener to the
connection
I don't think that the retroactive consumer feature guarantees delivery of
all messages sent while the consumer was inactive. The way this feature is
described, it is more of a best-attempt effort to deliver the messages.
http://activemq.apache.org/retroactive-consumer.html
Have you considered
Hey gdaswani,
Thanks! That is very helpful information, and saved me hours. I've
since heard the same things about 5.0 from other sources. It's too
bad the ActiveMQ downloads page doesn't recommend a stable release
that is... stable.
Thanks again!
Krishna
On Apr 2, 2008, at 10:00 AM,
Any updates on this issue?
navnetkachroo wrote:
The users.properties, login.config, and groups.properties files are in
$ACTIVEMQ_HOME/conf/org/apache/activemq/security ... I give this path as
an argument while (java.security.auth.login.config) starting ActiveMQ.
I tried commenting the
I don't think he needs to acknowledge. It appears he's using an asynchronous
receiver w/in an AUTO_ACKNOWLEDGE session. In this scenario, the
acknowledgment occurs automatically when the onMessage method returns.
Joe
Goto www.ttmsolutions.com for a free ActiveMQ user guide
liushk wrote:
I am currently taking a look at this. Part of the solution is to set
a timeout for your transport using a URI parameter like so:
activemq:tcp://amqsrv:61616?transport.requesttimeout=1
Where requesttimeout is in milliseconds. However, there is a bug with
the timeout, because it will
I am getting JMSExceptions caused by EOFExceptions as shown by the stack
trace below. I don't really know why it is occurring, can't can't reliably
produce the exception, but it does occur frequently. Can anyone point me to
where in my code I should look to correct this problem? Or if it is a
18 matches
Mail list logo
