Beware that the commandAgent, which is now commented out in the default
activemq.xml, will also initiate a connection.
Joe
bsnyder wrote:
>
> On Thu, May 15, 2008 at 8:49 PM, Aaron Mulder
> <[EMAIL PROTECTED]> wrote:
>> This may not be as bad as the subject sounds, but...
>>
>> I enabled secu
On Thu, May 15, 2008 at 8:49 PM, Aaron Mulder
<[EMAIL PROTECTED]> wrote:
> This may not be as bad as the subject sounds, but...
>
> I enabled security by dumping all 3 of the default files from
> http://activemq.apache.org/security.html in activemq-5.1.0/conf and
> then putting this in the broker c
This may not be as bad as the subject sounds, but...
I enabled security by dumping all 3 of the default files from
http://activemq.apache.org/security.html in activemq-5.1.0/conf and
then putting this in the broker config:
I am trying to analyze a sub ID and identify the consumer process associated
with it ...
For example,
ID_-57617-1210810061660-1_0
>From IdGenerator.java, 57617 seems to come from
new ServerSocket(0).getLocalPort()
However, I can't find this port doing 'netstat -anp | grep 57617'. Does th
Hi Hiram,
We were having similar issue and confirmed the following
(-Dorg.apache.activemq.UseDedicatedTaskRunner=false) works for us.
What are the implications of doing this ?
Thanks
- Sridhar
Hiram Chirino wrote:
>
> Could you try updating your activemq startup script so that instead of:
The stop command needs remote jmx access to the broker. Make sure you
set the SUNJMX variable to the following in the activemq shell script:
SUNJMX="-Dcom.sun.management.jmxremote.port=1616
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false"
On Thu, May 1
I'm getting this:
[EMAIL PROTECTED]:~/apache-activemq-5.1.0/bin> ./activemq-admin stop
ACTIVEMQ_HOME: /home/andrew/apache-activemq-5.1.0
ACTIVEMQ_BASE: /home/andrew/apache-activemq-5.1.0
ERROR: java.lang.RuntimeException: Failed to execute stop task. Reason:
java.io.IOException: Failed to
OK.. perhaps the best way is if you join the our IRC channel at:
irc://irc.codehaus.org/activemq
that way I can give you better real time help on getting started at
tacking this issue.
Regards,
Hiram
On Thu, May 15, 2008 at 2:44 PM, j0llyr0g3r
<[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> regarding:
>
Hi,
regarding:
If you interested in helping let me know and I'll get
you started in the right direction.
Since we have an urgent need for this functionality: Yes, please get me
started, and i will (hopefully) be able to supply a patch
--
View this message in context:
http://www.nabble.c
this might not be related to the pool, but the fact that statements and
resultsets are not closed.
the error comes directly from Oracle,
Filip
Hiram Chirino wrote:
could you try using the C3P0 [1] connection pooling instead of the
default commons logging pooling. Some folks have reported bet
Thanks Hiram for the reply. I commented out camel configuration. I am using
jetty for the web console. Is there some way to configure jetty not to
connect to the default port?
Hiram Chirino wrote:
>
> Your broker is starting up and listening on 2506.. this is evident
> from the message:
> 008-
Hi Hiram
We are a financial institution using Active MQ to supply market data to
clients. Whenever one or more consumer(s) is slow, it affects the publisher
from publishing data. We are currently facing the slow consumer issue. I
heard 5.2 will be sending advisory alerts when a particular destina
Hi,
On Wed, May 7, 2008 at 5:04 PM, Badri
<[EMAIL PROTECTED]> wrote:
>
> Hi
>
> We are running the ./query command against Active MQ 4.0.1 version to detect
> slow consumers.
>
> Question 1:
>
> Currently we are setting log level to DEBUG for Active MQ. Is there any
> statement logged to the log f
The matching entries are alphabetically sorted and the last entry is
the one used to apply the policy to the destination.
On Thu, May 8, 2008 at 1:47 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> hi,
> I have two questions about policy entries and wild card matching,
>
> can I configure
No pans are set in stone. If there is community demand for it we will
work on getting it out soon. What feature/bug fix are you looking to
get released?
On Fri, May 9, 2008 at 1:35 PM, Badri
<[EMAIL PROTECTED]> wrote:
>
> Hi
>
> When is the expected release date of 5.2?
>
> Thanks
> Badri
> --
>
Your broker is starting up and listening on 2506.. this is evident
from the message:
008-05-09 14:41:27,794 INFO TransportServerThreadSupport -
Listening for connections at: tcp://dcmpdevapp05:2506
The it looks like a failover client in the broker is trying to connect
to tcp://localhost:61616 a
will look into it!
cheers,
Rob
http://open.iona.com/products/enterprise-activemq
http://rajdavies.blogspot.com/
On 15 May 2008, at 13:04, Steven Van Loon wrote:
Thanks for the reply Rob.
The DLQ seems to be the queue to look for indeed, but it seems that
the
expired messages are not send
I guess you want an entry for all topics or all queues right (since
the actually names are dynamic)?
One way to do it might be to use topic='>' since that would match all
topics (temp topics are still topics). But I guess we should have
something a little bette than that.
On Fri, May 9, 2008 at
The Spring NamespaceHandler for element 'amq:broker' is located inside
the activemq-core jar. Is that in your classpath?
On Sun, May 11, 2008 at 3:56 AM, Yohan Liyanage <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I tried to create an embedded broker in a Spring Bean Configuration, as
> shown in Activ
Could you submit a test case - I've tried to reproduce from your description
- but with no success
cheers,
Rob
--
View this message in context:
http://www.nabble.com/java.lang.OutOfMemoryError%3A-unable-to-create-new-native-thread-on-AMQ-5.0-tp17005441s2354p17257710.html
Sent from the ActiveM
could you try using the C3P0 [1] connection pooling instead of the
default commons logging pooling. Some folks have reported better luck
using it.
Just add the c3p0 jar to the lib dir and add spring bean similar to
the following (this a mysql example)
I meant between 4.1.1 and 5.1.0...
As you can see, we've changed 2 versions at the same time... (ActiveMQ and
Mule)... never a good idea...
Benoit
Benoitx wrote:
>
> Hi Hiram,
>
> It seems that between 1.4.3 and 1.4.4 the exclude queues is not very
> strict...
>
> See this post:
>
> http:/
On Sun, May 11, 2008 at 11:12 AM, jaya_srini <[EMAIL PROTECTED]> wrote:
>
> Hi Filip
>
> I have 4 producers (who are also consumers) on different connections i.e I
> create a diffrent connection for each producer. But If multiple threads are
> using the same producer then I can see that they might
Stat tracking is disabled by default now. (Lowers cpu overhead).
call ActiveMQConnectionFactory.setStatsEnabled(true) or add the
"&jms.statsEnabled=true" option to the connection URI to enable them.
Regards,
Hiram
On Sun, May 11, 2008 at 2:47 PM, jhcha <[EMAIL PROTECTED]> wrote:
>
> I tested the
What version? I'd suggest you test against ActiveMQ 5.1.0 using the
default persitence configuration. It's the fastest option available.
On Mon, May 12, 2008 at 4:35 AM, Subrata1208 <[EMAIL PROTECTED]> wrote:
>
> Hi ,
> I am doing some performance testing for our project requirement.
>
> we wil
Could you simulate your error condition in a junit test and post it
for us to review? I agree the broker should be more isolated.
On Mon, May 12, 2008 at 4:33 PM, jgunz <[EMAIL PROTECTED]> wrote:
>
> We identified what was causing the problem. One of our consumers had an
> uncaught exception that
Hi Hiram,
It seems that between 1.4.3 and 1.4.4 the exclude queues is not very
strict...
See this post:
http://www.nabble.com/5.1.0-Network-Brokers%3A-changes-since-4.1.1--to17206477s2354.html#a17206477
Thanks for your reply
Benoit.
Hiram Chirino wrote:
>
> are all the brokers the same ver
can you make your test a junit and post it? That way we can easily
reproduce your issue.
On Mon, May 12, 2008 at 4:53 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> Filip Hanik - Dev Lists wrote:
>>
>> Rob Davies wrote:
>>>
>>> On 1 May 2008, at 00:02, Filip Hanik - Dev Lists wrote:
>>>
Yeah.. the http/s transport does not get as much use as most other
connectors so it might not be up to snuff. It would be awesome if
interested folks to start contributing test cases and patches to get
it more robust. If you interested in helping let me know and I'll get
you started in the right d
are all the brokers the same version or are you mixing them?
On Tue, May 13, 2008 at 6:45 AM, Benoitx <[EMAIL PROTECTED]> wrote:
>
> Has anyone found a solution to this?
>
> I've just upgraded from ActiveMQ 4.1.1 to 5.1.0 and suddenly all my network
> of brokers keep the messages in the local queu
Could you try updating your activemq startup script so that instead of:
ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=true"
it reads as:
ACTIVEMQ_OPTS="-Xmx512M -Dorg.apache.activemq.UseDedicatedTaskRunner=false"
I think that should help with your thread usage issues.
On T
Hi,
using the ssl-conncetor for ssl works fine but this is not what i need.
Because of a http-proxy in the middle i need to use the https-connector.
As described here:
http://www.nabble.com/http-ok%2C-ssl-ok%2C-HTTPS--%3E-NOT-ok--td17131092s2354.html
- ssl works
- http work (even over proxies
duplex option does not exist in that version.
On Tue, May 13, 2008 at 12:02 PM, /U <[EMAIL PROTECTED]> wrote:
>
> I have an identical problem with 4.1.2. Is the duplex
> keyword implicitly set to true in 4.1.2 network connectors?
> Documentation seems to suggest this keyword was
> introduced in 5.
Looks like you have multiple threads concurrently sending messages
using only 1 session. The JMS spec explicitly states that this is not
allowed. Sessions should only be used by 1 thread at a time.
On Tue, May 13, 2008 at 1:45 PM, jaya_srini <[EMAIL PROTECTED]> wrote:
>
> thanks for the response
You should be able to use the ssl: transports between brokers just
fine. All you have to configure is the key and trust stores + the JVM
properties for them.
Regards,
Hiram
On Wed, May 14, 2008 at 8:14 AM, j0llyr0g3r
<[EMAIL PROTECTED]> wrote:
>
> Hey folks,
>
> i have a major problem with AMQ h
Looks like the SUNJMX env variable is set to
-Dcom.sun.management.jmxremote.port=1099
make sure it's not for the activemq-admin script.
On Wed, May 14, 2008 at 8:24 AM, andrewh <[EMAIL PROTECTED]> wrote:
>
> Hi, thanks for the reply.
>
>
> j0llyr0g3r wrote:
>>
>> kill the activemq-process and look
The activemq-admin stop command also supports passing in the JMX url
for the broker.. So you just need to pass in the JMX url (which would
just change the 1199 port)
On Wed, May 14, 2008 at 2:53 PM, Mike Miljour <[EMAIL PROTECTED]> wrote:
>
> I should have added this to my boker config above:
>
I like that idea...
On Wed, May 14, 2008 at 3:33 PM, sudip shrestha <[EMAIL PROTECTED]> wrote:
> I was wondering maybe extending the
> org.apache.activemq.ActiveMQSslConnectionFactory class and providing hooks
> to set KeyManagers and TrustManagers will do the trick
>
> On Wed, May 14, 2008 at
I think what is happening is that you haven't given everyone all access
rights to the advisory topics. I get a similar stack trace when I don't do
that. Add an ACL with the following "ActiveMQ.Advisory.>" and that should do
the trick.
If you're interested, check out this AMQ security plugin.
h
Look in
$AMQ_HOME/example
--
View this message in context:
http://www.nabble.com/Newbie-questions-tp17238878s2354p17252361.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Thanks for the reply Rob.
The DLQ seems to be the queue to look for indeed, but it seems that the
expired messages are not send to this queue the moment they actually
expire.
I have created the following test scenario:
- I create a receiver for queue://ActiveMQ.DLQ and start it up
- I create a r
I found that the TransportThreadSupport hase the posibillity to start the
Thread as Demon. Is there a way to configure that? I hav not found any Way
to set the Variable to true at runtime.
--
View this message in context:
http://www.nabble.com/Transports-as-Demon-Thread-tp17251049s2354p17251049.
42 matches
Mail list logo
