I set persistence="false" on the jbi container. It was a solution to this
problem,but not a good solution for me.Because I would loose messages in
this case. And in my use-case their should no message be lost.One of one
million would be acceptable. So I now set persistence="true" and just allow
the jca-flow,this should give me the best solution to this use-case, I
think. Looking at the table at this site
http://incubator.apache.org/servicemix/transactions.html I found out that
jca-flow can just use asynchronous with persistent and not synchronous with
persistence.And in my config the jms component tries to send synchronous
while persistence is true. But if I set synchronous="false" the
jms-component does not receive any message.
bsnyder wrote:
>
> On 6/15/07, goldi <[EMAIL PROTECTED]> wrote:
>>
>> Found reason for first problem. This just occurs when I'm using
>> persistence="true". Using persistence="false" I don't get the exception.
>> A
>> little bit strange I think.
>
> Where did you set persistence=false?
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache Geronimo - http://geronimo.apache.org/
> Apache ActiveMQ - http://activemq.org/
> Apache ServiceMix - http://servicemix.org/
> Castor - http://castor.org/
>
>
--
View this message in context:
http://www.nabble.com/Unable-to-choose-a-flow%21-tf3872089s12049.html#a11163251
Sent from the ServiceMix - User mailing list archive at Nabble.com.
