On Thu, Aug 21, 2008 at 9:43 PM, Ryan Moquin <[EMAIL PROTECTED]> wrote:
> Hi Bruce,
>
> I tried my service with the two settings:
>
> deliveryMode="1"
> timeToLive="1000"
>
> The scenario is an external JMS client sends a message to a JMS consumer SU
> in servicemix. It forwards that to my service
Hi Bruce,
I tried my service with the two settings:
deliveryMode="1"
timeToLive="1000"
The scenario is an external JMS client sends a message to a JMS consumer SU
in servicemix. It forwards that to my service which does some processing
with the incoming message, and then creates a new message t
On 21 Aug 2008, at 13:52, Artur Siekielski wrote:
Hi.
Is it possible to change JMS queues semantics to Last In, First Out
(ie.
stack)? Would it be difficult to patch ActiveMQ sources to achieve
this?
Another solution to our problem is using priority queues. But ActiveMQ
doesn't support p
On 21 Aug 2008, at 21:35, Patrick Ruckstuhl wrote:
Hi,
as we wanted to use activeMQ for the messaging layer of Origo
(http://origo.ethz.ch), I wrote a small wrapper around activeMQ that
allows to easily connect an Eiffel application to activeMQ.
It can be found on Origo: http://ems.origo.ethz
Hi,
as we wanted to use activeMQ for the messaging layer of Origo
(http://origo.ethz.ch), I wrote a small wrapper around activeMQ that
allows to easily connect an Eiffel application to activeMQ.
It can be found on Origo: http://ems.origo.ethz.ch
About two weeks ago, Origo switched from a hand ma
Looks like there's an open JIRA for this issue:
https://issues.apache.org/activemq/browse/AMQ-1763 but that hasn't been
touched since it was created. Does anyone know what's going on here? Is
the Virtual Topic feature basically unusable in the 5.1.0 broker?
--
View this message in context:
htt
Some time back I started a discovery agent that used SLP and was optionally
backed by ApacheDS LDAP server. SLP is a nifty little protocol because it
allows you to attach attributes to the service registration and service
queries. So if a broker was configured to register with the attribute
color
Hi Joe
It's what I suspected. It's not suit me unfortunately.
I would like to have several multicast groups (and one network connector by
group) but not on a single LAN.
I would like that a local broker can request a "WAN distant directory server
(with known fixed IP)" to make a multicast choic
I haven't looked closely at the LdapNetworkConnector source, but I suspect it
will connect to all the brokers that result from the corresponding LDAP
search operation.
Joe
http://www.ttmsolutions.com
Eric-AWL wrote:
>
>
> ldap://myldap.mydomain.com:389";
>
Hello
Can somebody give me some hints about the basic steps to run the OpenWire
source code generator? I would like to support the OpenWire protocol in my
implementation of a client library for Delphi (which currently uses STOMP).
Java is no foreign language for me so I will not need much help, j
ldap://myldap.mydomain.com:389";
base="dc=brokers,dc=mydomain,dc=com"
anonymousAuthentication="true"
searchFilter="(cn=*)"
searchScope="SUBTREE_SCOPE"
2008/8/21 Eric-AWL <[EMAIL PROTECTED]>:
>
> Hi every body
>
> I'm not an LDAP expert so I expect I don't make too many mistakes in my
> explications.
>
> If we put several server references under the same RDN, does the discovery
> mechanism choose one of them with a round-robin algorithm ?
>
> What
Hi every body
I'm not an LDAP expert so I expect I don't make too many mistakes in my
explications.
If we put several server references under the same RDN, does the discovery
mechanism choose one of them with a round-robin algorithm ?
What happens if the server associated with this reference do
Hi, thanks for answer.
The first solution with selectors is too static for us - max. priority is
unknown. The second solution - using resequencer - should be tested by us
but I'm afraid of bad efficiency. How does it behave with millions of
messages in queues and hundreds of consumers/producers?
Hi Sebastian,
You can set the prefetch size on the connection URI as follows:
activemq:tcp://servername:61616?session.prefetchSize=5
As you noted, the prefetch size is set to 1000 as a default, but it can be
changed on a per-connection basis. Setting the value to 0 would effectively
disable pre
Using the default broker config I get an error message that there are too
many open files when I try to produce to 1000 topics.
I am not able to load any other configuration files.
If I give the url argument with the configType argument it seems to get
ignored:
mvn activemq-perf:broker -Durl=brok
I wrote a FAQ entry on implementing priority queues with ActiveMQ...
http://activemq.apache.org/how-can-i-support-priority-queues.html
2008/8/21 Artur Siekielski <[EMAIL PROTECTED]>:
>
> Hi.
> Is it possible to change JMS queues semantics to Last In, First Out (ie.
> stack)? Would it be difficult
What about using Camel to implement a resequencer?
http://activemq.apache.org/camel/resequencer.html
Joe
http://www.ttmsolutions.com
Artur Siekielski wrote:
>
> Hi.
> Is it possible to change JMS queues semantics to Last In, First Out (ie.
> stack)? Would it be difficult to patch ActiveMQ sou
Hi.
Is it possible to change JMS queues semantics to Last In, First Out (ie.
stack)? Would it be difficult to patch ActiveMQ sources to achieve this?
Another solution to our problem is using priority queues. But ActiveMQ
doesn't support priorities. Only Oracle's AQs support this...
A bigger pict
Hi,
if you need a with the secured broker, you must set the
appropriate ActiveMQComponent as shown in the patch for AMQ-1237
(https://issues.apache.org/activemq/browse/AMQ-1237)
Cheers
--
Dejan Bosanac
http://www.ttmsolutions.com - get a free ActiveMQ user guide
ActiveMQ in Action - http://
I found out that what i called a local store is in ActiveMQ called
prefetching. This prefetching is controlled via the variable prefetchSize
(which in NMS is set in the session.cs to a fixed value of 1000). Do I have
influence on this value in some way ? It would even better if, there would
be a
On Thu, Aug 21, 2008 at 12:33:52PM +0300, Eugeny N Dzhurinsky wrote:
> the method createBroker doesn't start the broker.
>
> Or I didn't understand what you meant with
>
> > What should help is to add a start="false" attribute to the broker xbean.
>
> Could you please advice?
sorry, I've tried
On Wed, Aug 20, 2008 at 01:35:58PM +0100, Gary Tully wrote:
> I think the issue is that the broker configured via
> "xbean:activemq.xml" is started eagerly. That is, it is started before
> your connector is added. What should help is to add a start="false"
> attribute to the broker xbean.
>
> not
In fact, I imagine splitting my architecture in "local islets" and having a
similar multicast mechanism in each "islet".
Islets are distributed over two sites and each have a sort of HA directory
server which answers to discovery requests from whatever broker, by sending
multicast request on their
24 matches
Mail list logo