to my application
via my embedded broker.
So I am thinking of create a dynamic list of connectors to allow certain IP
address to talk to my app.
is it do able and wise to do so?
Thanks
-Dan
bsnyder wrote:
>
> On Fri, Oct 23, 2009 at 3:43 PM, Dan Tran wrote:
>>
>>
>> Act
mance/memory
issue?
My main purpose is just to control security and what host I can listen to.
Thanks
-Dan
rajdavies wrote:
>
>
> On 23 Oct 2009, at 06:32, Dan Tran wrote:
>
>>
>>
>> Hi instead of using the bellow config to allow all remote clients to
Just curious,
have you set up your JVM's -Xmx param?
-Dan
OliverLeeYn wrote:
>
> Today I install ActiveMQ in a computer , but after AMQ started, the
> console post the error:
>
> INFO BrokerService - ActiveMQ JMS Message Broker (localhost, I
> D:oliver-1374-1256219225078-1:0) started
> Ex
Hi instead of using the bellow config to allow all remote clients to connect
to my embedded broker
Is there a way to programmatically create transportConnector to allow a
limit number of remote client hosts?
Thanks
-Dan
--
View this message in context:
http://www.nabble.co
scratch that, i need jmsTemplate.setExplicitQosEnabled( true ); as well
sorry for the noise.
-D
Dan Tran wrote:
>
>
> I would like to bring discussion back where I cannot get message in my
> queue to expire.
>
> I am using JmsTemplate producer to send messages to
no
affect
Is it the right way?
-Dan
Dan Tran wrote:
>
>
> It turns out I am using topic and when my consumer is destroyed, all
> messages also destroyed, but the stats still lingering in the jconsole and
> this is were confusion starts.
>
> thanks
>
>
tion. As a workaround you could hack it to make that attribute
> a string value.
>
> 2009/10/9 Dan Tran :
>>
>>
>> Hi I am using ActiveMQ with Spring, and I seem not able to make useJmx
>> configurable
>>
>>
>> > advisorySupport="false&
Hi I am using ActiveMQ with Spring, and I seem not able to make useJmx
configurable
I have other properties work fine except that line, any suggestion? must be
the xbean's issue?
here is error message:
SEVERE: Exception sending context initialized event to listener instance of
class org
is to turn off the dedicate task runner:
> -Dorg.apache.activemq.UseDedicatedTaskRunner=false.
>
> Thanks for your help,
> -Jimmy
>
>
> Dan Tran wrote:
>>
>>
>> Default flow control can nail you. how big is your message, how fast is
>
; for messages using
>
> MessageConsumer.receive()
>
> rather than have the broker push messages to the consumer. Does the
> jms.prefetchPolicy.queuePrefetch parameter still apply? Perhaps this is
> slowing us down?
>
> -Jimmy
>
>
> Dan Tran wrote:
>>
>> Sound like you have
Sound like you have the classical slow consumer fast producer problem. Read
up on producer flow control feature, prefetchSize, etc.
-Dan
jimmymartin wrote:
>
> Hello,
>
> I'm running a 5.2.0 broker that throws the error below after about 2 days
> of running. I've seen some discussion from pr
any
flow control.
I now set prefetch size to a much smaller number ( 10 ), most of messages
are stuck in broker, this is where broker can do its job to throttle the
producer to slow down.
Nothing is better than hand on experience.
Sorry for all the noise.
-D
Mine,
Dan Tran wrote:
>
>
It turns out I am using topic and when my consumer is destroyed, all
messages also destroyed, but the stats still lingering in the jconsole and
this is were confusion starts.
thanks
-Dan
Dan Tran wrote:
>
>
> Hi Felix,
>
> Thanks for the info, both of my producer and consum
)
Any suggestion?
Thanks
-Dan
Dan Tran wrote:
>
>
> Hello, I am testing the producer flow control of activemq for both 5.2
> and 5.3-RC2. In my test bed, I have a number of producer an consumer
> topic working in pair. When I have multiple pairs running at the same
&
Hello, I am testing the producer flow control of activemq for both 5.2 and
5.3-RC2. In my test bed, I have a number of producer an consumer topic
working in pair. When I have multiple pairs running at the same time where
the producers are out pacing the consumers, the flow control feature wor
number of
> messages have not (yet) been acknowledged by the consumer.
> Can it be that the consumer received the message but couldn't ack the 13
> messages since you stopped it ?
>
>
> Cheers,
> Felix
>
>
>
>
> Dan Tran wrote:
>>
&g
Ah you are right, it does not happen on 5.3-SNAPSHOT
must be the left over of 5.2
Thanks for looking into this
-D
rajdavies wrote:
>
>
> On 28 Sep 2009, at 05:51, Dan Tran wrote:
>
>>
>>
>> My ActiveMQ configuration does not persist message, all messages in
Hi, I am testing 5.3-SNAPSHOT to pick up expired message enhancement where
the message will be automatically removed when timed out.
I have multiple topics with each has a pair of producer/consumer. All
messages are memory base, where 'memoryUsage' is used to do the producer
flow control. All
My ActiveMQ configuration does not persist message, all messages in in
memory. However activemq-data directory is created uppon startup. is this a
bug?
i tested with both 5.2. and 5.3-SNAPSHOT.
Here is my configuration
...
will fixed at activemq side?
-D
rajdavies wrote:
>
> ooh - ok - I think we need to adjust something ;)
> On 22 Jul 2009, at 16:54, Dan Tran wrote:
>
>>
>>
>>
>> is it better if it is at DEBUG level? Or it really mean we must to
>> adjust
>>
is it better if it is at DEBUG level? Or it really mean we must to adjust
the memory accordingly. otherwise the log file will be full of these
messages.
This is new in 5.3 SNAPSHOT
-D
--
View this message in context:
http://www.nabble.com/WARN--org.apache.activemq.usage.Usage%3CMemory-us
Hello
works for 5.2.0 but break in 5.3-SNAPSHOT
I have to change it to
is this the expected behavior?
Thanks
-Dan
--
View this message in context:
http://www.nabble.com/broken-5.3-SNAPSHOT-when-using-localhost-for-transport-tp24599700p24599700.html
Sent from the ActiveMQ - User m
Any one with an answer for this question? from reading activemq doc and
forum, the lockup is understandable, how it what it does not make sense is
that it is still locked up when there only one client left.
Thanks
-dan
Dan Tran wrote:
>
>
> Hello, I have an embedded AMQ with
Oops, sorry. It is 5.2 with 2 clients: sss and vm. The vm topic client is
the receiving end
-Dan
rajdavies wrote:
>
> some details on version/config may help ;)
>
> On 19 Jul 2009, at 17:01, Dan Tran wrote:
>
>>
>>
>> Hello,
>>
>>
Hello,
I am seeing the following message on stdout
Conn: 172.30.63.41.42867.090709212649 SYSSH200 qasj04
for each StreamMessage received
and 172.30.63.41 is another host that has nothign to do with my testbed.
Any suggestion on this?
Bug thanks ahead
-Dan
--
View this message in c
Hi does ActiveMQ supports this feature?
Thanks
-D
--
View this message in context:
http://www.nabble.com/Is-it-possible-to-have-multiple-queue-receivers-listening-on-the-same-queue%2C-using-message-selectors-%28typically-filtering-on-a-correlation-ID%29-to-determine-which-listener-actually-r
the fix will be in 5.3 perhaps?
-D
rajdavies wrote:
>
> Unfortunately not in the current release - though using a Queue
> browser will have the same result - in forcing expired messages to be
> removed
>
> On 15 May 2009, at 08:55, angel7 wrote:
>
>>
>> thank you for your kind
>>
>> So,
Hello, I have an embedded AMQ with 2 clients using vm:// and tcp://
respectively. The tcp://client mostly used to send lots of messages to the
vm:// client. The vm://client periodically sends control massages to tcp://
client.
The issue I am facing right now is the send operation from vm:// cl
28 matches
Mail list logo