Yes, internally, the JBI components we developed have implementation of
marshalers for our requirements. These were developed and configured in the
servicemix.xml was doing the processing of xml - viz validation, total
validation ,converting to flat file sequentially.
When we introduced threading in our code , the components / marshallers did
a way better job.
Thanks for the feedback
Mat
bsnyder wrote:
>
> On Dec 19, 2007 9:53 AM, MatSM <[EMAIL PROTECTED]> wrote:
>>
>> I did try playing with the thread pool size in the config file for
>> smix..
>> However, st flow doesn't scale better than SEDA.
>
> The ST flow is not going to be affected by adjusting the thread pool
> size. That will only affect the SEDA flow.
>
>> Our next option is to go with clustering of SMix with seda and JMS flow.
>>
>> We had to use threading within our application to increase the rate at
>> which
>> Smix does all the JBI components processing on our input files, which we
>> have developed.
>>
>> The difference, with threading in our application process , image+xml
>> file
>> to extend of 1000 rec /minute
>>
>> With out threading in our application , the process did close to 50 recs
>> /
>> minute.
>
> So how did you add this functionality? Did you create a marshaler for
> one of the ServiceMix components?
>
> Bruce
> --
> perl -e 'print
> unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
> Apache Geronimo - http://geronimo.apache.org/
>
> Blog: http://bruceblog.org/
>
>
--
View this message in context:
http://www.nabble.com/Seda-Flow-and-ST-flow-tp14339781s12049p14421810.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
