hey, thanks for the interest. Did you have any luck in getting this to work ?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-won-t-start-with-jre-1-7-tp4658849p4658974.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
see https://issues.apache.org/jira/browse/AMQ-4164
--
View this message in context:
http://activemq.2283324.n4.nabble.com/master-slave-within-a-network-of-brokers-tp4410862p4658965.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
How does rounding work for these two properties ? Since most the messages (as
per JMX stats) are queued only for 60 microseconds I need to understand if
that means that difference between properties would be shown as 0 ms or 1ms.
Whats the rounding logic ?
--
View this message in context:
http
Hai,
I am having a problem with sending heartbeats to JMS broker. I am using
JBoss hornetQ as the message broker. When I am using C# NMS stomp client to
subscribe to a topic, after some time I am seeing a message on hornetQ
console "Received Invalid stomp header 1,10,1,10..". When I googled around
big +1 to that.
the wrapper has been causing trouble for a while now.
On 7 November 2012 12:55, Christian Posta wrote:
> Apollo uses winsw http://kenai.com/projects/winsw/downloads
> wonder if it would be worth backporting to Apache 5.x?
> I'll give it a shot and see if it solves this issue with
Can you give more context about how you're trying to run it?
I tried it on my side and it looks just fine @
http://localhost:8161/adminwhich is where it gets deployed by default.
Are you trying to run it in a
different container, e.g., Tomcat?
On Tue, Nov 6, 2012 at 7:49 AM, Earle Nietzel wrote:
Apollo uses winsw http://kenai.com/projects/winsw/downloads
wonder if it would be worth backporting to Apache 5.x?
I'll give it a shot and see if it solves this issue with Java 7 / 64bit
On Tue, Nov 6, 2012 at 11:34 PM, jmls wrote:
> urgh. I changed the wrapper.conf to use a 1.6 jre, and the ser
great.
send a pull request to fusesource, so we can take your changes on
board as soon as you are happy with them.
On 7 November 2012 12:35, jsimmonsc wrote:
> Thanks for the quick response and for confirming what I was seeing. I don't
> know if it will be of help but I've temporarily forked the
-rw-r--r-- 1 root root 33555136 Nov 6 16:24 db-2.log
-rw-r--r-- 1 root root 33554663 Nov 6 16:24 db-3.log
-rw-r--r-- 1 root root 33557047 Nov 6 16:24 db-6.log
-rw-r--r-- 1 root root 33556316 Nov 6 16:25 db-7.log
-rw-r--r-- 1 root root 33556009 N
Thanks for the quick response and for confirming what I was seeing. I don't
know if it will be of help but I've temporarily forked the fusesource jms
pool and applied the fixes made for the memory leak.
https://github.com/jsimmonsc/jmspool
If there is anything else I can do to help, please let m
k, at least you have a workaround.
I had a peek at the code and I see what you saw.. this is a regression from
https://issues.apache.org/jira/browse/AMQ-4019
the xa factory has been left behind a bit with that refactor.
On 7 November 2012 12:21, jsimmonsc wrote:
> My entire context is below.
>
>
My entire context is below.
If I switch out the org.apache.activemq.pool.XaPooledConnectionFactory with
a org.fusesource.jms.pool.XaPooledConnectionFactory, everything works as
expected except for the previously mentioned memory leak fixed in AMQ-3997.
Just in case it's needed, my route:
from
can you post your xml configuration for the came context.
the enlistment is done automatically by XaPooledConnectionFactory once
it gets a handle
on the transactionmanager that has an active transaction
On 6 November 2012 21:50, jsimmonsc wrote:
> Hello,
>
please do raise a jira and attach your patch. It would be good to
capture the use case and gauge interest. In the main, the shared
nothing master/slave setup does not get a lot of attention, but that
may be b/c it works fine for most users or b/c most folks use a shared
store or independent brokers
14 matches
Mail list logo
