Problems with Message

[Norman Maurer <no...@apache.org>]

Hi all,

I'm currently try to write a Proof of Concept for using ActiveMQ for
spooling (queue) in JAMES (james.apache.org).
One of my teammates investigated into this some time ago an had some
exchange with James Strachan:
http://markmail.org/message/vzzmwm3kdv66r3ce#query:+page:1+mid:mp2pafe77efwczbb+state:results

Unfortunally we never did the move until now..

We using Camel for doing the whole Matcher/Mailet processing and us it
to read abd write from our current spool implementation.

I use camel to just send the Mail object (which holds the MimeMessage
and some other stuff) via
producerTemplate.sendBody("activemq:myqueue?jmsMessageType=Object",mail).
After that I see that the camel routes take in place and cosume the
mail object and start the routing. This works without problems, except
one "little" thing. If I try to access the MimeMessage (which is
stored in the Mail object)  I always just get "null".

So my question is, is there any "limitating" which would cut of the
MimeMessage while storing the mail object into the queue ?

I know storing the whole mail in a JMSMessage is not a good thing for
performance, but I want to get it work before start to optimize it.

Thx,
Norman

Re: Problems with Message

[Norman Maurer <no...@apache.org>]

Hi all,

I found the cause of getMessage() to return null. MimeMessage itself
is not Serializable :/ So I worked arount this problem by put the
whole MimeMessage into a byte[] array and now it work.
Anyway thats quite inefficent, so I'm currently investigating into
using a StreamMessage to store the MimeMessage. Does this sound good ?
I know BlobMessage would prolly be preferable in terms of performance,
but I don't want to depend on an "external" storage.

Bye,
Norman


2010/2/24 Norman Maurer <no...@apache.org>:
> Hi all,
>
> I'm currently try to write a Proof of Concept for using ActiveMQ for
> spooling (queue) in JAMES (james.apache.org).
> One of my teammates investigated into this some time ago an had some
> exchange with James Strachan:
> http://markmail.org/message/vzzmwm3kdv66r3ce#query:+page:1+mid:mp2pafe77efwczbb+state:results
>
> Unfortunally we never did the move until now..
>
> We using Camel for doing the whole Matcher/Mailet processing and us it
> to read abd write from our current spool implementation.
>
> I use camel to just send the Mail object (which holds the MimeMessage
> and some other stuff) via
> producerTemplate.sendBody("activemq:myqueue?jmsMessageType=Object",mail).
> After that I see that the camel routes take in place and cosume the
> mail object and start the routing. This works without problems, except
> one "little" thing. If I try to access the MimeMessage (which is
> stored in the Mail object)  I always just get "null".
>
> So my question is, is there any "limitating" which would cut of the
> MimeMessage while storing the mail object into the queue ?
>
> I know storing the whole mail in a JMSMessage is not a good thing for
> performance, but I want to get it work before start to optimize it.
>
> Thx,
> Norman
>