B
bfvo
Guest
Some extra info: I've seen the original error on 3 different machines (2 laptops, 1 VM). It happened with both 11.3.1 & 11.3.2. If I may suggest: I think some more time needs to be spent on exception handling. This error, but also when for example when the AppServer is not running, could be handled with clear & descriptive messages in the log file, insetad of not so obvious stack traces / nested exceptions. This would make the life of both developer and techsupport easier. Anyway, case closed. Thanks for thinking along with me.
Continue reading...
Continue reading...