Regarding this discussion from a few days ago: I am having the same problem, using Xalan 2.2.D11 from within Cocoon to generate PDFs. Several other Cocoon users are reporting the same problem, and none of them have any idea what it means or why it is happening.
The problem does NOT occur with 2.2.D8. If there isn't an easy fix, and it looks like there isn't, may I suggest changing the exception message to be more informative? Outside of Xalan developers, no one has any idea what a DTM ID is, and the API docs don't explain it either. Since the problem is not consistently reproducible, and often responds to seemingly irrelevant changes in the environment (see Cocoon user list for examples), people could spend a lot of time in vain trying to stop this. A message like "Xalan cannot cope with files of this size. Please break up your files/use a different processor" could save a lot of people a lot of pain. Ryan
