Thanks for the info. Do you think we should rewrite this using Digester
instead of Castor?
Carsten Ziegeler wrote:
Someone told me some months ago that they experienced several strange
issues with castor under load - I think he mentioned class loading and
synchronization problems. I still can't remember *who* it was :( So,
chances are that this is really caused somehow by castor. I improved the
the castor portal implementation for 2.1.8 slightly - the version in
2.1.7 parsed the mapping each time a profile is loaded. I guess that
through this operation the classes are loaded as well. In 2.1.8 the
mapping is only read once on startup.
So my suggestion is to use the CastorSourceConverter from 2.1.8 in your
2.1.7 environment and see what happens.
Carsten
