Oh... and this is now being tested against the 5.7.0 snapshot for the broker.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Not-seeing-enabled-advisories-ActiveMQ-WebConsole-tp4653952p4654009.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hello.
I tried with all of the following destinations.
ActiveMQ.Advisory.FULL.>
ActiveMQ.Advisory.FULL
ActiveMQ.Advisory.Full.>
ActiveMQ.Advisory.Full
ActiveMQ.Advisory.>
ActiveMQ.Advisory.FastProducer.>
The only consumer that ever received anything was ActiveMQ.Advisory.> and
that was getting n
Hi Christian, thank you for the link!
From what I understand, Apollo uses the idea of consumer "credit window" to
decide how many messages to send down to the client that haven't been ACKed.
use the "credit" header in your stomp frame to set the credit window:
http://activemq.apache.org/apollo
Are you using a composite destination?
In the little unit test the advisory destinations are:
topic://ActiveMQ.Advisory.FastProducer.TempQueue.ID:gtmbp.local-55628-1342199123635-3:1:1
topic://ActiveMQ.Advisory.FULL.TempQueue.ID:gtmbp.local-55628-1342199123635-3:1:1
So you need the exact match or a
SADNESS!
I changed my steps so that I created a consumer for the topics:
ActiveMQ.Advisory.FULL
ActiveMQ.Advisory.Full
ActiveMQ.Advisory.FastProducer.Queue
I changed to the snapshot for 5.7.0.
I see the advisory topics in the web console. However no advisories are ever
sent to them f
aha, seems it's already on the radar. failover uri masks out ssl uri.
Workaround is to force it to use the keystore and truststore via Java OPTS.
http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-3785-ActiveMQSslConnectionFactory-does-not-detect-ssl-request-in-failover-URIs-whens-td4501530.h
the problem is with failover ssl. Using ssl://localhost:61617 works fine with
ActiveMQSslConnectionFactory and client auth.
failover:(ssl://localhost:61617) or failover:ssl://localhost:61617 breaks
ActiveMQSslConnectionFactory in that the keystore and truststore set in it are
ignored and you ha
think the key bit is to create the advisory topic consumers up front.
There no persistence on a topic unless there are durable subscribers,
so you need to be listening to the topic to get the advisory.
On 13 July 2012 16:03, JRR wrote:
> Hello Gary,
>
> How would I run the test you referenced? I
What JDK/JVM version and vendor are you using?
On Fri, Jul 13, 2012 at 4:16 PM, guerra wrote:
> Hi,
>
> I was just doing some tests on ActiveMQ 5.6.0 and I got an exception reading
> the camel.xml file. Which is puzzling me is that it happens in random way
> and maybe after 3 or 4 attempts it wo
thanks, that would be much appreciated :-)
submit a jira with the doc attached and tick the grant check box and
we can add it for you.
On 13 July 2012 15:47, reza_rahman wrote:
> Perhaps I should write updated material for GlassFish deployments :-).
>
> --
> View this message in context:
> http:
Hello Gary,
How would I run the test you referenced? I use the CPP client not Java.
(Actually I don't use Java at all... I start the broker using the
bin/activemq script or the script our Java team gives the server team for
starting the broker).
I looked through the code and I see that one of the
Perhaps I should write updated material for GlassFish deployments :-).
--
View this message in context:
http://activemq.2283324.n4.nabble.com/rar-configuration-tp2344227p4653986.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Indeed, that's what I found. You can override all the values in the shipped
ra.xml after you deploy it via GlassFish resource adapter configuration (I
used the console). As a result, you can point to a AMQ configuration file
other than the default.
That's far better than mucking with the RAR file
Hi,
I was just doing some tests on ActiveMQ 5.6.0 and I got an exception reading
the camel.xml file. Which is puzzling me is that it happens in random way
and maybe after 3 or 4 attempts it works!. I am not sure whether somebody
else have come across something like this and give me and clue to fix
>From what I understand, Apollo uses the idea of consumer "credit window" to
decide how many messages to send down to the client that haven't been ACKed.
use the "credit" header in your stomp frame to set the credit window:
http://activemq.apache.org/apollo/documentation/user-manual.html#Subscript
Not sure about this one but it's weird. If I use this code in a unit test
against an embedded SslBrokerService with client authentication enabled:
connectionFactory.setKeyStore(keystorePath);
connectionFactory.setKeyStorePassword(keystorePassword);
connectionFactory.setTrustStore(truststorePath);
I would expect that properties in the embedded ra.xml can be
overridden in the container deployment descriptor.
On 11 July 2012 20:07, reza_rahman wrote:
> I have the same issue (albeit with GlassFish rather than JBoss). I need to
> add transports, customize clustering, start an embedded broker a
the jms template uses a generic producer, so it is not associated with
a particular destination.
the code uses producer.send(message, destination, ) so the
destination is specified for each send.
In jmx, the producer should appear based on its clientId and producer
id, but won't be connected
have a peek at this test case:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/java/org/apache/activemq/bugs/AMQ3903Test.java?view=markup
tweak it to validate your exact scenario but to me, it confirms the fix
On 12 July 2012 23:23, JRR wrote:
> I've created a consumer and I c
This is https://issues.apache.org/jira/browse/AMQ-3451
can you validate that the problem is the same with a current
5.7-SNAPSHOT and that you are calling the static shutdown methods as
outlined in that jira.
If I want to quickly reproduce, what steps should I follow?
On 13 July 2012 09:09, liny
Hi,
It's old issue, but I still can't or find any solution so far.
After stop my web application, Tomcat told me some memory leak.
I use VisualVM to check, and yes, below caused memory leak.
Does anyone find any solutions?
Can ActiveMQ team try to solve it?
Thank you for any advice.
--
View this
21 matches
Mail list logo
