This may be the change from Jasper1 to Jasper2 - I have upped my
?/proc/fs/fs-max? (something like that) with Jetty, which has
upgraded to this Jasper in 3.2beta.
Try taking the Jasper jars from the earlier version of TC and using
them with the newer version.
Jasper2 uses Ant to do all it's on the fly compilation.
This apparently works much better !!!
On-the-fly compilation is, IMNSHO, purely a useful development feature
and anyone using it in production is asking for trouble. For
production, you should precompile. In development, try the older
version of Jasper, or up your max-fds and grit your teeth.
Come back to the forum and let us know whether this is the problem. If
it is, someone should really raise a bug against Jasper.
If it isn't, I apologise to the Jasper team for my slanderous
allegations ! :-)
thank you for your quick reply...i will definitely try it and let you know what happens.