I don't really get this. If you extend the prefetchSize to more than what it
was configured to be by the maxMessages parameter in the
Connection.createConnectionConsumer() call, you are violating the JMS spec.
The maxMessages parameter is defined as "the maximum number of messages that
can be as
add a trailing slash to the ftp upload url, think that is what the strategy
is looking for to determine a working directory in the ftp server.
jndiParameters.put(Context.PROVIDER_URL,
"tcp://localhost:61616?jms.blobTransferPolicy.uploadUrl=ftp://user:p...@myhost
/");
On 16 March 2010 08:00, joe
You can achieve this but it's not as easy as a setting in a config file.
You could implement your own BrokerPlugin/Filter that overrides
BrokerFilter.addConsumer(), and implement that so that it rejects
consumers on your specific destination.
Mats
On 19 March 2010 05:31, BenXS wrote:
>
> For
The prefetch extension in the transacted case is necessary for the case
where a transacted consumer wants to consumer more than prefetch messages in
a single transaction. Without the extension, the broker would see a full
prefetch and not dispatch any more and a receive could block.
On 15 March 20
Yea, it is a simple in memory hash map configured from the environment.
I was thinking of a new property, xa=true|false that could trigger the
creation of an XA variant of the connection factory.
I think doing XA by default may upset clients what check for an XA
connection factory, transaction wrap
Aha!!! This finally makes it clear...
I had durable subscription working a week or two ago. But I had never tested
the "persistence" piece of that, i.e. taking the broker down with unconsumed
messages on a topic which has a registered durable subscriber. I just did
that test and see that it works
Gary Tully wrote:
>
> you need to change
> the
> org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(Hashtable)
> method to optionally create an ActiveMQXAConnectionFactory
> I think it would be a sensible default but having a property that can
> ensure
> that a partic
On Thu, Mar 18, 2010 at 12:15 PM, jumbro wrote:
>
> I just tested persistence using a QUEUE and... it works!
>
> So my question is: do topics offer this same functionality? If not, then
> why?
>
> If topics do support persistence, then I'm still missing something..
Topics support durability which
I just tested persistence using a QUEUE and... it works!
So my question is: do topics offer this same functionality? If not, then
why?
If topics do support persistence, then I'm still missing something..
jumbro wrote:
>
> I traced the message send within Spring.net. Setting
> NmsTemplate.Per
I have questions surrounding message groups and their behaviour under
failover:
My configuration:
* 2 brokers (A & B) connected to each other using a network connector. Both
brokers define a queue called TEST_Q.
* BrokerA and BrokerB have their own slave broker (SlaveBrokerA and
SlaveBrokerB).
I traced the message send within Spring.net. Setting NmsTemplate.Persistent =
true propagates that property to the MessageProducer. I also set
NmsTemplate.ExplicitQosEnabled = true which leads to:
producer.Send(message, persistent, priority, timeToLive);
where producer is an Apache.NMS.ActiveMQ.
On Thu, 2010-03-18 at 08:55 -0700, jumbro wrote:
> Thanks for your reply.
>
> I tested your suggestion and it works. I see now that it's the producer that
> determines the persistence.
>
> Do you know off hand how to configure this same behavior using Spring? I'm
> using the NmsTemplate and allow
On Thu, Mar 18, 2010 at 10:31 AM, BenXS wrote:
>
> For a certain Queue (e.g. myqueue123) I would like to allow producers to
> store new JMS messages
> but not for Consumers to retrieve them.
>
> How can I achieve this? In other words: Which parameter do I have to set in
> which confg file?
There'
odd, that stack trace does not match with the 5.3.0 source. I missing
subscription should be ignored during recovery. Can you verify that it is
5.3.0 and that this installation has no duplicate jars or anything odd like
that.
So the root cause seems to be connections not shutting down which forces
On Thu, Mar 18, 2010 at 9:55 AM, jumbro wrote:
>
> Thanks for your reply.
>
> I tested your suggestion and it works. I see now that it's the producer that
> determines the persistence.
>
> Do you know off hand how to configure this same behavior using Spring? I'm
> using the NmsTemplate and allowi
I am trying to use the internals of activemq to produce the following result:
Topic A
Topic B > Virtual Topic Z
Topic C
I want to publish different messages to topics A, B, and C and receive them
all via a single consumer listening to Virtual Topic Z.
I attempted to use a composite topic,
For a certain Queue (e.g. myqueue123) I would like to allow producers to
store new JMS messages
but not for Consumers to retrieve them.
How can I achieve this? In other words: Which parameter do I have to set in
which confg file?
Ben
--
View this message in context:
http://old.nabble.com/Can-
Thanks for your reply.
I tested your suggestion and it works. I see now that it's the producer that
determines the persistence.
Do you know off hand how to configure this same behavior using Spring? I'm
using the NmsTemplate and allowing Spring to manage the underlying messaging
context. I'm set
Hi all
I have a job's queue, from which a worker receives messages to work on.
Each time the worker decides to take a job (it can handle more than on the
same time) it calls createQueueSession with transacted=true, creates a
consumer, receives a message, and keep these 3 objects until the job's
ha
Gary Tully schrieb:
> what version are you using? this looks like
> http://issues.apache.org/activemq/browse/AMQ-1712 but that is not consistent
> with your reference to KahaDB.
>
Sorry. The broker is 5.3.0. We had no problems with our stores on 5.2.0
but there we had problems with hanging conne
can you raise an issue for this, with the url you pass to
addNetworkConnector. I see some of the networkConnectors override the
getName method to make it unique but not all do.
On 16 March 2010 15:41, Ryan Moquin wrote:
> I was experimenting with adding network connectors to ActiveMQ through JMX
What you describe is as expected. Topics are a little different w.r.t to
expiry as the messages are only persisted on a per consumer basis.
If there are no consumers, the messages are discarded so they don't get a
chance to expire.
If there are durable subscribers the pendingMessageLimitStrategy ki
what version are you using? this looks like
http://issues.apache.org/activemq/browse/AMQ-1712 but that is not consistent
with your reference to KahaDB.
On 17 March 2010 12:43, Roland Thomas Lichti wrote:
> Hi,
>
> after a broker shutdown I get IOExceptions when starting again. The
> broker tries
you need to change
the
org.apache.activemq.jndi.ActiveMQInitialContextFactory.createConnectionFactory(Hashtable)
method to optionally create an ActiveMQXAConnectionFactory
I think it would be a sensible default but having a property that can ensure
that a particular factory is xa would be a nice a
can you post your consumer code?
On 18 March 2010 10:29, sand...@i2it wrote:
>
> Hello All,
> In my application i have two types of user A & B. Now what i want to
> alert the user B whenever A performs some action through mail. So for 100%
> delivery of messages i am using JMS ActiveMQ. My Re
uu... you are right
i forgot that i also copied activemq.rar to the common glassfish modules
directory some weeks ago. i removed that directory and now everything is
fine again!
thanks for your help!!!
Gary Tully wrote:
>
> That smells of a classloading issue, like the activemq jars
That smells of a classloading issue, like the activemq jars are available to
two different classloaders, or two different versions of the acrtivemq-core
jar are available.
Both of the referenced classes are from the same activemq-core jar and
should only be resolved from the RAR. The jars should no
Looking for a way to make ActiveMQ use PooledConnectionFactory through JNDI I
came across your post
and http://www.mail-archive.com/us...@tomcat.apache.org/msg66249.html that
one which may not help solve your issue but possibly delivers an
explanation.
Michael
stevegula wrote:
>
> I have spe
I deployed the activemq-ra-5.3.rar to glassfish v3. My MDB can now consume
jms messages from my
activemq broker. everything is fine, BUT when i restart my glassfish domain,
I get the folowing stacktrace:
after restarting the activemq resource adapter and my application ear
everything is fine aga
Hello All,
In my application i have two types of user A & B. Now what i want to
alert the user B whenever A performs some action through mail. So for 100%
delivery of messages i am using JMS ActiveMQ. My Requirement is before
directly sending request to mail server first i want to check whethe
Environment:
Win32
Environment
Websphere 6.1.0.13
ActiveMQ 5.3.0 [Win32, same machine as WAS]
ActiveMQ configured with accompanying Resource Adapter on Websphere.
Spring 2.5.6.
Hibernate 3.3.2
LS,
In preparation for our Websphere - Websphere MQ connection and absense of
the latter on o
Thank you for answers.
Don't hesitate if you have any other suggestions.
I will invistigate on WCF and ServiceMix.
Thierry M.
--
View this message in context:
http://old.nabble.com/ActiveMQ-with-SOAP-tp27933776p27942877.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
32 matches
Mail list logo
