Well, starting up a connection against the vm:// transport will always get
a connection because the broker will be auto-created in the JVM if it
cannot find one.
Check your connection URI. Is there a broker running at
tcp://localhost:61616 ?
On Wed, Sep 11, 2013 at 7:54 AM, travep wrote:
> A
Post your test case and instructions to re-create.
On Wed, Sep 11, 2013 at 1:38 AM, Liviu I. wrote:
> Hello again and sorry for answering so late :)
>
> I was refreshing jconsole manually and it did not show any updates until
> around 10 seconds later (this seemed to vary a little bit).
>
> In
Have you altered the prefetch size for your consumers?
http://activemq.apache.org/what-is-the-prefetch-limit-for.html
On Wed, Sep 11, 2013 at 8:15 AM, mandrake_2 wrote:
> Hi there,
> I've got a big problem with Glassfish 3.1.2 and ActiveMQ 5.6.0.
>
> My system configuration is the following:
>
Hello:
I'm using ActiveMQ 5.8.0 and my client requires to install 3 brokers
into 3 different servers
What is the best configuraration ? Each ActiveMQ server connected to
others ? A ring ?
Is possible a loop ?
Thanks
Looked briefly at your configs...
Can you try this... for the brokers that have 2+, you can use the
masterslave: discovery agent on your network connector... check out more
details here: http://activemq.apache.org/networks-of-brokers.html
For the NC that has single URI connectons, add this to the
Hi there,
I've got a big problem with Glassfish 3.1.2 and ActiveMQ 5.6.0.
My system configuration is the following:
1) a java stand-alone Producer that sends 50 msg/sec to a jms queue (Queue
type) hosted by ActiveMQ
2) a EAR deployed into Glassfish with a MDB to consume messages from that
queue
T
A quick test against an working environment works like this:
Now, trying to get this working in glassfish using jndi and the
active-rar-5.5.1 package like this:
The jndi version results in failure: JMSException: Error in allocating a
connection. Cause: Could not create connection.
Here is my
I’ve come across a problem which has similar sounding symptoms & have done a
bit more investigation (no resolution yet though).
My problem is that when a network connector failed back to the remote broker
specified by the "priorityBackup" uri, the remote broker doesn't seem to
recognise that the c
I've come across a problem with similar symptoms & have done a bit more
investigation (no resolution yet though):
See JIRA https://issues.apache.org/jira/browse/AMQ-4720
Business Computer Projects Ltd is a limited company registered in England and
Wales.
Regis
I'm using a network of brokers & am trying to get a fail-back network
connection working (using priorityBackup=true on the connector)
I'm finding that the broker does failover & failback correctly but that the
remote broker doesn't seem to recognise that the re-established connection
is a network
Hi,
take a look at
https://issues.apache.org/jira/browse/AMQ-4628
In the comment there's a procedure how to manually update database schema.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic
Hi,
at the moment there's only a plan for 5.9.0 release and it should be due in
the next month or so.
Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manni
Hello again and sorry for answering so late :)
I was refreshing jconsole manually and it did not show any updates until
around 10 seconds later (this seemed to vary a little bit).
In the tests that we have done there were no consumers for the queue that
we've tested. After activating a consumer
13 matches
Mail list logo
