That's not a a memory leak you're seeing - that's the wacky
Retroactive Consumer functionality - see http://activemq.apache.org/retroactive-consumer.html
The default policy is FixedSizeSubscrptionRecoveryPolicy - and the
default cache size for each topic in 5.1 is about 6mb. I'd suggest
conf
hi all,
I'm using activemq 5.1.0 with jdbc persistence (postgresql).
when I send a message a new row is created in activemq_msgs , but id
increments by 3 . (4 7 10...)
why is it so?
thanks.
--
View this message in context:
http://www.nabble.com/id-sequence-tp19912788p19912788.html
Sent from t
I have run across a memory leak that I have been able to reproduce. I
am profiling the sample application in NetBeans and I believe that I
have traced the problem to
org.apache.activemq.openwire.v3.BaseDataStreamMarshaller.tightUnmarshalByteSequence(DataInput,
BooleanStream)
The sample program is
Hi, we got a problem when using journal configured with JDBC, here are some
details:
We configured the journal with an Oracle datasource, but it is *extremely*
slow when sending messages to ActiveMQ, about 1.5 minutes per message...,
and our config file looks like below:
...
On Thu, Oct 9, 2008 at 3:55 PM, Eddie Yee <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to configure some very simple authentication to the web console on
> 5.1, and noticed an error in the documentation:
> http://activemq.apache.org/web-console.html#WebConsole-ExampleconfigurationusingJetty6
>
Hi,
I'm trying to configure some very simple authentication to the web console on
5.1, and noticed an error in the documentation:
http://activemq.apache.org/web-console.html#WebConsole-ExampleconfigurationusingJetty6
In the Step 1 example xml snip, it appears to be malformed near the end of th
Hello, I am running apache-activemq-5.1.0 under Centos 5.2 and having the
exact same issue - I was under the assumption (from the posts in this tread)
that this was fixedjust reportingThank you!
Exception in thread "ActiveMQ Transport: tcp://localhost/127.0.0.1:61616"
java.lang.ClassCastE
Apologies for responding to myself, but I wanted to mention that I did try
the 1.1 NMS client with the "wireFormat.MaxInactivityDuration="
connection option, and it did resolve the issues we had with zombie/orphan
connections on the broker.
--
View this message in context:
http://www.nab
Jim,
Thanks for responding. I did try the same test under AMQ 5.2 and 5.3, but
the result was the same each time. I will try the 1.1 release with the
parameter you suggest and report back.
One follow up question: I thought the MaxInactivityDuration was already
defaulted to 30 seconds:
http://
I just added a link to the vote thread in the release page warning.
2008/10/9 James Strachan <[EMAIL PROTECTED]>:
> 2008/10/9 Eddie Yee <[EMAIL PROTECTED]>:
>> Does anybody know the actual release date/time for AMQ 5.2? I keep seeing
>> the "please come back in a few days". If it's not going to
2008/10/9 Eddie Yee <[EMAIL PROTECTED]>:
> Does anybody know the actual release date/time for AMQ 5.2? I keep seeing
> the "please come back in a few days". If it's not going to be released in a
> few days, the page should be removed or updated.
If you want to know the exact progress of the re
Does anybody know the actual release date/time for AMQ 5.2? I keep seeing the
"please come back in a few days". If it's not going to be released in a few
days, the page should be removed or updated.
Thanks
Eddie
> Date: Mon, 22 Sep 2008 12:04:18 -0700> From: [EMAIL PROTECTED]> To:
> use
Hi,
We had a similar problem as well. We called them "zombie connections". I
think we solved this by moving to ActiveMQ 5.2. If that doesn't work, you
can turn on the timeout inactivity option by setting the
"wireFormat.MaxInactivityDuration="
connection option. This option is in the NMS 1.1
BTW the default in ActiveMQ from 5.2 onwards is now to use the
failover transport - so unless you disable it or change the failover
protocol, it will silently reconnect and recover for you without
Spring having to do anything
http://activemq.apache.org/failover-transport-reference.html
2008/10/9
Hi,
I have a problem with configuring amq:connectionFactory in my srping config
file.
Ive searched google, and found some people who had the same problem, but
their solution dont work for me for some reason.
Same issue as me http://issues.apache.org/activemq/browse/AMQ-1638
http://issues.apache.
when using consumer.receive() to receive messages from a selected broker,
if i shutdown the selected broker . the consumer.receive() didn't throw
any Exception . Nevertheless ExceptionListener or TransferListener can
catch the disconnected exception , but i thought that the client cons
16 matches
Mail list logo