As an update to this item, the latest version of NMS 1.1 has the ability to
programmatically delete destinations (queues and topics).
On Tue, Nov 25, 2008 at 2:28 PM, Jim Gomes wrote:
> You are welcome to add those missing features as enhancement requests
> in the AMQNET JIRA database so they ge
I entered a JIRA (https://issues.apache.org/activemq/browse/AMQNET-138).
Before I dig into the code, would you ensure that the config files have been
copied into the same directory as the NMS files. For every protocol, you
will need the corresponding config files. Following are the basic
configu
Sorry for the delay
STOMP should be supported, but it just appears to be broken from recent
changes. If there isn't a JIRA for this already, I'll throw one in there
and take a look at it. Hopefully, it shouldn't be too hard to fix. The
STOMP code is all still there, it's just an error in se
Not sure about that part. Could be an issue. I used Pidgeon, because it
was the only IM client I could get to work correctly. Would have been nice
if I could get GoogleTalk to work, since that is my main IM client.
On Fri, Jan 30, 2009 at 4:07 PM, Dave Cramer wrote:
>
> I'm running on OSX I w
Try setting the wireformat.maxinactivityduration=30 parameter. If you
are using the latest version of NMS 1.1, this should already default to
3, which is 30 seconds. If you shorten that amount, then ActiveMQ
should kick off dead connections faster. Barring that, you can use a GUID
in you
I'm running on OSX I wonder if that is the problem. I know the listener is
working. If I connect via telnet I get a response upon connection. But for
some reason clients can't login.
Dave
semog wrote:
>
> I have and am using Pidgeon to successfully connect to ActiveMQ XMPP
> protocol. I use th
Any updates on this issue? This seems very similar to a problem we are
experiencing with the broker halting dispatch of messages to consumers that
are ready and able to receive messages. Our problem definitely seems to be
surrounding the flagging of messages as persistent. Our current work-aroun
I think a couple of things should be clarified first. Setting the
Persistent flag is not the same thing as a Durable Consumer. A durable
consumer must be created with the CreateDurableConsumer() API. A normal
consumer will consume messages flagged as persistent as well as
non-persistent.
If you
Anybody have some experience with SSL on the .NET platform? I don't use it
(except when I do my online banking in my browser).
On Tue, Jan 6, 2009 at 6:35 AM, Gleb wrote:
>
> Hi,
> First of all, please excuse me for my english.
> I have to develop client for ActiveMQ 4.1.1-based service . I hav
I've never worked with ActiveMQ 4.1 series. I would only be able to try
this against the 5.1.0 or higher version. I tend to stay with the latest
version of ActiveMQ. This issue would need to be narrowed down to whether
it is a client or broker issue. Could you try this test against ActiveMQ
5.2
I have and am using Pidgeon to successfully connect to ActiveMQ XMPP
protocol. I use the Pidgeon IM client to get notified of our Hudson
builds. Hudson publishes via Jabber API to ActiveMQ, and then my Pidgeon
client sees the message. It wasn't too difficult. I am currently using the
5.3 snapsh
Hi,
Even I Have the same problem.
ModiPawan wrote:
>
> Hi
>
> Sorry, I forget to attached my ACtiveMQ config file. Here it is
> http://www.nabble.com/file/p17773268/activemq.xml activemq.xml
>
> do i need to configure any queue or topic in this configuration file?
>
> Please
Great! Glad I was able to help. I was once mystified by the same thing. I
think I made some changes inside NMS to handle this in a more coherent
fashion. It didn't make sense that a message flagged as non-persistent was
being sent as persistent. Like I said, I would have to go and check the
co
The best reference is the code[1] but in short, it determines whether
a pool of threads is used to do work in the broker or whether tasks
(or groups of tasks) each take their own thread.
If your JVM does a good job of thread management then having a thread
per task is sensible. If there are too man
I don't know if that was the only intended use, it was just the one I could
think of :D
Gabe
-Original Message-
From: "yesnid"
Sent: Friday, January 30, 2009 1:29pm
To: users@activemq.apache.org
Subject: RE: Why configure destinations in the broker?
Hello Gabe,
So that is the intende
Hello Gabe,
So that is the intended use case keeping entities in the system from
creating queues that you have not authorized, interesting.
Thank you for the input, I appreciate it.
Nick
Gabe Westmaas wrote:
>
> You can disable the creation of queues if you want to limit usage of your
> bro
You can disable the creation of queues if you want to limit usage of your
broker to specific, known queues.
Gabe
-Original Message-
From: "yesnid"
Sent: Friday, January 30, 2009 1:08pm
To: users@activemq.apache.org
Subject: Why configure destinations in the broker?
Hello All,
I am cu
Hello all,
I am working on trying to customize my broker's configuration to that end I
am trying to understand the various elements of the configuration. As part
of that what is the effect of: "dedicatedTaskRunner" why and when would I
want to enable or disable this?
Thank you.
--
View this m
Bill,
Yes, the xmpp connector starts. When I try connecting it just hangs. When I
try a small client app it just hangs on the send as well.
Dave
Bill Schuller wrote:
>
> Are you including the optional XMPP jar?
>
>
> On 1/30/09 5:08 AM, "Dave Cramer" wrote:
>
>>
>> I've tried Adium, spar
Hello All,
I am curious, I see where Destinations can be configured to be created by
the broker on startup instead of on demand, why would you want to do this?
What is the advantage to creating a queue or topic on startup as opposed to
on demand?
Thank you.
--
View this message in context:
htt
There is test case attached to
https://issues.apache.org/activemq/browse/AMQ-1593 that works on
trunk.
2009/1/30 jmychasiw :
>
> Greetings:
>
> The only way that I can get AMQ 5.2 to properly route an invalid message to
> the DLQ is if I use a Non XA connection and set sessionTransaction=true. We
semog wrote:
>
> Check your producer settings. The producer may override the message
> setting. Think of this as a "persistent producer" or "non-persistent
> producer".
>
Thank you, that was it.
For anyone using Spring.NET, please note that the [B]Persistent[/B] property
on the [B]NmsTemp
Greetings:
The only way that I can get AMQ 5.2 to properly route an invalid message to
the DLQ is if I use a Non XA connection and set sessionTransaction=true. We
would prefer to use XA if possible.
Is there a known issue with redelivery policy and XA?
Any help would be appreciated.
Could it be
Are you including the optional XMPP jar?
On 1/30/09 5:08 AM, "Dave Cramer" wrote:
>
> I've tried Adium, spark, iChat. None of them will connect. I even tried
> writing a simple publish/subscribe in java. Same problem.
>
> Does xmpp work ?
---
Bill Schuller, Service Foundations Engineering, I
Check your producer settings. The producer may override the message
setting. Think of this as a "persistent producer" or "non-persistent
producer". Whatever message is sent via a persistent producer, that message
will be flagged as persistent. I seem to remember coming across this a
while back,
the network will not send messages back to where they came from. This
is to stop messages bouncing over and back between brokers if there
are consumers on both brokers. The issue is that the network connector
(consumer) is quite fast so it will typically beat a regular consumer
to a message or get
Hi everybody
In 4.1.2.
I developped a queuing and multi-threaded mechanism just behind JMS listener
: each time a message comes, a thread is prepared, enqueued (Executor) and
executed only when an other one dies. I can manage the maximum number of
active threads.
When I used AUTO_ACKNOWLEDGE Se
I haven't tested out the failover code yet, but I've been told that it is
working. I would suggest taking out the failover: specifier in your
connection string to see if a normal connection works. Then work up to
using failover.
wangchao wrote:
>
> Hello everyone:
> I encountered a proble
Yes, I will put this workaround.
Thank you.
James.Strachan wrote:
>
> Looks like a concurrency bug we should work around. In the mean time -
> how about adding a synchronized block around looking up a queue in
> JNDI? You should only need to look it up once on start up and not need
> to look
Looks like a concurrency bug we should work around. In the mean time -
how about adding a synchronized block around looking up a queue in
JNDI? You should only need to look it up once on start up and not need
to look it up in each thread many times concurrently?
2009/1/30 Eric-AWL :
>
> Hi
>
> On
Hi
On 5.2.0 release.
I create 10 threads, each using the same dynamicQueues/CATE-CHARGE-charge
queue
I fail with
javax.naming.NamingException: Something already bound at CATE-CHARGE-Charge
at
org.apache.activemq.jndi.ReadOnlyContext.internalBind(ReadOnlyContext.java:150)
at
org
semog wrote:
>
> consumer" situation. If the messages are flagged as non-persistent, then
> everything works fine. We are still working on narrowing down the
> problem.
>
I'm having the same problem as the OP, so we put a workaround in our
production system.
However, I am interested in purs
Hello,
I don't know if you figure out the solution or not. So here is what my fix
for your issue:
> /**
> * @openwire:marshaller code="9"
> */
> public class Person implements Serializable
> {
> private String firstName;
>
> private String lastName;
>
> public void setFirs
The first error in the log looks descriptive...
2009-01-30 14:09:58,278 [main ] ERROR BrokerService
- Failed to start ActiveMQ JMS Message Broker. Reason:
java.lang.RuntimeException: java.io.IOException: Failed to create
directory 'activemq-data/localhost/tmp_storage'
java.lang.R
Hi Degan
There was a reference to jetty in the WEB-INF/activemq.xml file, however i
have now done a fresh deployment of the web console, as I had previously
made amendments to some of the config files to try and get it to work so i
might have adding something that wasn't required. So now all the
Do you have tag left in your WEB-INF/activemq.xml file?
Cheers
--
Dejan Bosanac
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Jan 29, 2009 at 3:25 PM, Richie84 wrote:
>
> Hi
>
> Thanks for that, I
I've tried Adium, spark, iChat. None of them will connect. I even tried
writing a simple publish/subscribe in java. Same problem.
Does xmpp work ?
--
View this message in context:
http://www.nabble.com/xmpp-broken---tp21745261p21745261.html
Sent from the ActiveMQ - User mailing list archive at
Hi Bill,
this is a known issue and something we are working on, with a bit of
luck you will get the behavior you require with a 5.3-SNAPSHOT build
next week. Follow the status of
https://issues.apache.org/activemq/browse/AMQ-1730 for details. Short
term, prefetch=0 is the workaround.
Regards,
Gary
I'm not sure, if this is all related to the Memoryleak I found in AMQ 5.2
see
http://www.nabble.com/OutOfMemoryError-after-9505925-persistent-messages-to21722796.html
I just made a new test run last night and my PS Old Gen is about to explode.
GC has no effect any more.
Cybexion wrote:
>
>
39 matches
Mail list logo
