In my experience, the "weird errors" you see in virtualized production environments where JVM is unrestricted (unlike Google App Engine or RedHat OpenShift) are almost never caused by the environment itself but some small, fairly simple differences between your dev/test and production environments. "Unable to locate class" is almost certainly caused by Plastic not being able to instantiate your custom exception report page. Could be a small missing dependency or anything else but errors that happen in the exception handling chain are not always clearly reported, and this case "not able to locate" is probably a bit misleading when that class likely threw an exception while being instantiated.
For the actual error at JobHistoryManager.java:429, why would you even post this without sharing the code with us? I guarantee it's not just because its "somehow not liking the virtualized server" but without seeing the code, all we can do is guess. Kalle On Mon, Jan 18, 2016 at 4:49 PM, George Ludwig <georgelud...@gmail.com> wrote: > Andreas, yes, I am 100% certain that the specific directories are readable > and writable by Tomcat. In fact, prior to this exception being thrown, a > different file is successfully read and written. > > Still scratching my head. > > On Mon, Jan 18, 2016 at 12:04 PM, Andreas Fink <fink.a...@googlemail.com> > wrote: > > > Hi George. > > > > Are you sure the specific directory and its content is readable by > Tomcat? > > Maybe some File-specific exceptions get silently catched on the way and > > substituted with 'null' instead of empty array. > > > > Just my 2c. > > > > Cheers, > > Andi. > > > > On 18 Jan 2016, at 2:06 , George Ludwig <georgelud...@gmail.com> wrote: > > > > > At that > > > time it's trying to convert a Set of files to a List of files, and I > can > > > see that the directory that is being listed clearly has files, so the > NPE > > > should never have been thrown. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > >
