I am experiencing some problems with message selectors and was wondering
whether there is known issue in activemq and queue message selectors.
Prior to publishing a message on a queue i set the propA property
message.setIntProperty("propA ", zone.getZoneNumber());
On the consumer side i do
Hi,
I am configuring an outgoing JMS bridge between ActiveMQ and IBM MQSeries.
Messages that are bridged over to MQSeries need to have an extra JMS
property added on to the message header (the "JMS_IBM_Format" header).
Looking through the JMS Bridge documentation, it seems that message
converte
On 5/23/07, rjj <[EMAIL PROTECTED]> wrote:
Hi,
Can you delay consuming messages on a queue by the date time?
I would like to place a message on a queue but not have it consumed until a
certain time in the system is reached in the future. Say for example 5 mins
into the future.
I do not want to
For those of you who've not yet spotted the Camel project...
http://activemq.apache.org/camel/
its a powerful and lightweight router and implementation of the
Enterprise Integration Patterns
http://activemq.apache.org/camel/enterprise-integration-patterns.html
We've now got Camel integration in
Adrian, thanks. I add several optional jars in the lib\optional\ directory.
It works well now.
Howdy...mind sharing the list?
--
View this message in context:
http://www.nabble.com/How-to-use-http-connector-tf3826648s2354.html#a11417944
Sent from the ActiveMQ - User mailing list archive at
Oops, forgot the stack trace
2007-07-03 10:37:10,513 ERROR [STDERR] Caused by: java.io.IOException:
Unknown data type: 73
2007-07-03 10:37:10,514 ERROR [STDERR] at
org.apache.activemq.openwire.OpenWireFormat.doUnmarshal(OpenWireFormat.java:342)
2007-07-03 10:37:10,514 ERROR [STDERR] at
org.apac
James.Strachan wrote:
>
> Sounds like you are communicating with an old broker; or using the
> incorrect port (e.g. talking to the stomp port or something). Maybe
> turn off the multicast discovery and double check your client jars
> match your broker jars
>
>
Hi,
I switched to the apache-act
James.Strachan wrote:
>
> Sounds like you are communicating with an old broker; or using the
> incorrect port (e.g. talking to the stomp port or something). Maybe
> turn off the multicast discovery and double check your client jars
> match your broker jars
>
> On 7/3/07, nkiesel <[EMAIL PROTECT
I have a bunch of ActiveMQ tests that are exhibiting weird behavior. That
is, sometimes they pass and sometimes they fail. I can run a suite and see
seven failures. Then run those tests individually and watch them all pass.
This suggests to me that I'm not properly initializing the queue in setUp
On 7/3/07, yunusbayraktar <[EMAIL PROTECTED]> wrote:
Thanks for your quick reply. We still need the messages for the consumers
that are not available at the moment. The consumers are display devices and
they can go off momentarily and when they come back the messages that were
sent for them needs
Hi everybody,
has this problem already been fixed? I also getting OOME with kaha
persistence adapter.
Greets Goldi
Rainer Klute (Rainer Klute IT-Consulting) wrote:
>
> Rob Davies schrieb:
>> I'm fixing these at the moment - though I'd expect it will be closer
>> to the end of the week when I'v
Thanks for your quick reply. We still need the messages for the consumers
that are not available at the moment. The consumers are display devices and
they can go off momentarily and when they come back the messages that were
sent for them needs to be displayed.
We currently are using apache-activ
On 7/3/07, yunusbayraktar <[EMAIL PROTECTED]> wrote:
Hi James,
We have a list of clients and for each client we create a separate
queue(some of them are persistent, some of them are not) dynamically. The
number of clients can be up to 750. We preferred this way because we assumed
that this may
Hi James,
We have a list of clients and for each client we create a separate
queue(some of them are persistent, some of them are not) dynamically. The
number of clients can be up to 750. We preferred this way because we assumed
that this may be faster than a single queue with Message Selector pat
Sounds like you are communicating with an old broker; or using the
incorrect port (e.g. talking to the stomp port or something). Maybe
turn off the multicast discovery and double check your client jars
match your broker jars
On 7/3/07, nkiesel <[EMAIL PROTECTED]> wrote:
Hi,
I'm getting the fol
15 matches
Mail list logo
