[
https://issues.apache.org/jira/browse/CAMEL-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13244449#comment-13244449
]
Frank Kootte commented on CAMEL-3776:
-------------------------------------
Hye Christian - appreciate the fenomenal collaboration !
Indeed would the solution induce more locking giving the current approach. This
is actually the reasoning behind my initial solution - pooling contexts,
marshallers and unmarshallers - which in hindsight is somewhat overkill for
common usecases - not everbody needs a highly scalable solution catering for
high load as we are currently dealing with. The automagically expanding and
shrinking pool would load on demand and scale to extremely high load. As we
have a lot of routes using the FallbackTypeConverter I will try to amend a
single end-to-end flow to use the JaxbDataFormat so we can compare how the
different approaches when stressed. I hope I will be able to provide you
feedback on performance tomorrow but given the work required I wont make
promises anymore I am not sure I can live up to.
With regards to the pooling solution camel provides - I briefly looked into it
before I decided to go for the Apache Commons Pool approach - I think it is
worth considering to refactor the camel pool to use the APC as I think it
contributes to familiarity and mantainability to reuse the proven solution
instead of a special camel catered crafted approach offering no directly
obvious benefits.
Hopefully I will be able to provide you with some conclusive numbers soon and
we can finalise this patch.
Cheers
> Add pooling support for JAXB data format
> ----------------------------------------
>
> Key: CAMEL-3776
> URL: https://issues.apache.org/jira/browse/CAMEL-3776
> Project: Camel
> Issue Type: New Feature
> Components: camel-jaxb
> Reporter: Claus Ibsen
> Fix For: 3.0.0
>
> Attachments: jaxb-pool.patch
>
>
> We should use the ServicePool in camel-core to pool JAXB / marshaller /
> unmarshaller.
> Of course ppl should be able to customize pool settings and if to be used.
> Also mind that for type converters with JAXB you do not configure a JAXB data
> format. And thus we should
> still be able to configure and use pooling, so the type converter can be more
> efficient.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
