well done mate!
Where is the code atm? Can I take a look at it?
Cheers
2008/9/10 Eugene79 <[EMAIL PROTECTED]>:
>
> Got reply from Andrew Kuklewicz. He said he will incorporate the changes.
>
> Eugene
>
>
>
> bsnyder wrote:
>>
>> On Tue, Sep 9, 2008 at 12:55 PM, Eugene79 <[EMAIL PROTECTED]> wrote:
rajdavies wrote:
>
> Hi Piotr,
>
> you could have run into this a problem processing lots of expired
> messages to the Dead Letter Queue.
> The around is to configure your broker not to process expired messages
> - for details on how to do that see
> http://issues.apache.org/activemq/brows
I swithed to the amqPersistenceAdapter: Kaha with journal... semms to be ok!
Thanks!
Gary Tully wrote:
>
> see http://activemq.apache.org/jdbc-support.html for some detail on
> overriding the default statement set. It should be possible to
> override the lock statement that is used by default.
It may be worth while creating a jira for this so that it can be
investigated a little further. This behavior will have an adverse
effect on a network of any size. It should (I hope,) be possible to
reduce the chattiness to some degree.
2008/9/5 Martin_Cornelius <[EMAIL PROTECTED]>:
>
> Hi all,
>
Gary Tully wrote:
>
> It may be worth while creating a jira for this so that it can be
> investigated a little further. This behavior will have an adverse
> effect on a network of any size. It should (I hope,) be possible to
> reduce the chattiness to some degree.
>
OK, JIRA entry is https://
Hello,
I have an applet which is a client to ActiveMQ 5.1. Currently it works in
Java 1.5. For external reasons (other applets in web application) I have to
use Jinitiator v.1.3.1.22 Virtual Machine.
Is it possible to run JMS client in 1.3 VM? I found out that Active MQ
server v.4 requires minimu
2008/9/10 piotr_rezmer <[EMAIL PROTECTED]>:
>
> Hello,
> I have an applet which is a client to ActiveMQ 5.1. Currently it works in
> Java 1.5. For external reasons (other applets in web application) I have to
> use Jinitiator v.1.3.1.22 Virtual Machine.
> Is it possible to run JMS client in 1.3 VM?
there may well be an ordering problem here but also consider
BrokerService broker = ...
broker.getManagementContext().setCreateConnector(false);
to see the call in context, check out a unit test that configures
multiple brokers, eg:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/t
Hi,
today i was testing a client application with ActiveMQ broker
using STOMP transport, and after some tests i saw 27 different
consumers connected to that queue by looking at the web console.
This is impossible because the broker is on my machine and i was
the only one accessing it.
By looking a
Hi!
I use AMQ 5.1.0 and I have following situation:
JMS consumer can reveice JMS-messages and processes it for some time
(for example, more than 1 sec).
For testing I send few messages in a short time (5 messages per 1 second).
I see in AMQ console (http://localhost:8161/admin/queues.jsp):
Hi,
I am starting two brokers (tcp://localhost:61616 and tcp://localhost:61626)
with shared FS. One is locked out because journal is locked by the master as
it should be. Then I start my Spring base web app with a TransportListener
added to ActiveMQConnectionFactory. When spring is done with init
Cool! I've updated updated my local NMS library and am currently running a
test. I'll let you know in a few hours how it turns out.
Thanks,
Bryan
On Wed, Sep 10, 2008 at 12:48 AM, Jim Gomes <[EMAIL PROTECTED]> wrote:
> FYI, the NMS trunk now has the keep alive support implemented. You can
> tu
I am looking through the examples, and they all package a jar, then run 'mvn
camel:run' which, I assume is an embedded camel/amq server. Correct?
If not, please tell me.
If so, where can I find a tutorial on production deployments to my AMQ /
Tomcat ?
I really do not want to use embedded first, I
Here is the patch.
Index: lib/stomp.rb
===
--- lib/stomp.rb(revision 87)
+++ lib/stomp.rb(working copy)
@@ -23,16 +23,17 @@
# synchronous receives
class Connection
-def Connection.open(login = "", passcode
here is test code for subscriber
--
require 'rubygems'
require 'stomp'
# activemq uses client-id: and activemq.subscriptionName: headers to
uniquely
# identify a subscription. This is required for durable subscribers
@conn = Stomp::Connection.open nil, nil, "lo
On Wed, Sep 10, 2008 at 10:38 AM, ivan <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I use AMQ 5.1.0 and I have following situation:
>
> JMS consumer can reveice JMS-messages and processes it for some time (for
> example, more than 1 sec).
>
> For testing I send few messages in a short time (5 messages per
On Wed, Sep 10, 2008 at 10:10 AM, Yari Marchetti
<[EMAIL PROTECTED]> wrote:
> Hi,
> today i was testing a client application with ActiveMQ broker
> using STOMP transport, and after some tests i saw 27 different
> consumers connected to that queue by looking at the web console.
> This is impossible
Below is the output from a unit test I wrote to demonstrate the problem.
here is the summary from what is highlighted:
14:34:28 - send "Hello, World!"
14:34:29 - receive "Hello, World!"
14:34:34 - remind myself to shutdown master broker, i.e. localhost:61626
14:34:40 - amq detects transport fail
2.5 hours of inactivity. I just sent a message through and the service is
still responding. That's a good sign, but I'll let it run overnight to be
sure. I'm still not convinced it will survive more drastic network outages,
but this appears to be a significant step in the right direction!! :)
Br
Hi everyone,
The ActiveMQ-CPP 2.2.1 release is now official! You can download the
source distribution here:
http://activemq.apache.org/cms/activemq-cpp-221-release.html
This release offers several bug fixes found since the 2.2 release, see
the download page for the complete list.
Regards,
Tim
Great to hear! I hope the test goes well. Thanks for verifying this.
Yeah, it won't handle network outages. That's where failover comes in
(scheduled for 1.1). However, this should keep any firewalls or routers
from aggressively disconnecting the sockets.
On Wed, Sep 10, 2008 at 3:15 PM, Bryan
Bruce Snyder пишет:
On Wed, Sep 10, 2008 at 10:38 AM, ivan <[EMAIL PROTECTED]> wrote:
Hi!
I use AMQ 5.1.0 and I have following situation:
JMS consumer can reveice JMS-messages and processes it for some time (for
example, more than 1 sec).
For testing I send few messages in a short time (5 me
22 matches
Mail list logo
