Remoting nullPointerException for ALL Errors

[littler...@gmail.com]

Lucee is running well - I'm working on an Enterprise Flex project and didn't take long to move from ADCF.

Everything is now running as expected - the only issue I'm running into is when an error is thrown - the only error returned to the flex client is this nullPointerException.  The actual error - in this case an error I threw -  is being logged in Tomcat's stderr - then immediately after the nullPointerException is thrown by lucee - and it's this error that gets returned to the remoting client.

I've logged this error: https://bitbucket.org/lucee/lucee/issue/269/remoting-nullpointerexception-for-all

Also including the snap of the stderr and the debug dump from BlazeDS to stdout

Is there a way to stop Lucee from throwing this error?  Or a way to catch and send the original back to BlazeDS?

[littler...@gmail.com]

It seem that Railo 4.2.0.007 is unaffected by this issue - every version after this has the same issue.  Is there someone out there that can point me in the right direction?

[Moishe Groger]

This is affecting me as well. 

[Michael Offner]

best update to the latest patch available on the preview update provider, that solves the issue

Micha

--
You received this message because you are subscribed to the Google Groups "Lucee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lucee+un...@googlegroups.com.
To post to this group, send email to lu...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/lucee/44269cbb-c4aa-4acd-8bd0-f944331ae2d6%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.