[
https://issues.apache.org/activemq/browse/AMQ-719?page=comments#action_36432 ]
James Stanton commented on AMQ-719:
---
This can be fixed by changing ActiveMQTextMessage "Text" getter/setter to look
like this: (tested with Java 1.4.2)
public string Text
[ https://issues.apache.org/activemq/browse/AMQ-757?page=all ]
james strachan reassigned AMQ-757:
--
Assign To: james strachan
> MapMessage to support nested Map objects to create a typesafe hierarchial
> message such as used on RV etc
>
[ https://issues.apache.org/activemq/browse/AMQ-758?page=all ]
james strachan resolved AMQ-758:
Resolution: Won't Fix
Closed for now as this bug is an effect of the design of Message Groups - they
are meant to implement single-threaded processing o
[
https://issues.apache.org/activemq/browse/AMQ-758?page=comments#action_36423 ]
james strachan commented on AMQ-758:
I don't really understand the problem. Message Groups are designed so that a
single thread processes all messages of the same group. If
we're experiencing an OOM with heavy CPU usage at startup on an
activemq 4.0final release broker. we're connecting with activemq
4.0 final release client. We're using jencks message driven pojo's and
jencks outbound message pooling. Our config looks like this:
[...]
[]
3
+1.
On 6/19/06, Fritz Oconer <[EMAIL PROTECTED]> wrote:
+1 Release ActiveMQ 4.0.1
Regards,
Fritz Oconer
- Original Message -
From: "Hiram Chirino" <[EMAIL PROTECTED]>
To:
Sent: Saturday, June 17, 2006 10:03 AM
Subject: [VOTE] Release Apache ActiveMQ 4.0.1
> Since the 4.0 release a b
