Http status 500 - Argument is null exception shown on screen [message #803323] |
Tue, 21 February 2012 07:32 |
Avrajit Chatterjee Messages: 68 Registered: September 2011 |
Member |
|
|
Hi,
Sometimes we get this unusual error when we do random clicks on our RAP application.
"java.lang.IllegalArgumentException:Argument cannot be null". This cannot be always reproduced. The most annoying part is that it shows a HTTP Status 500 with the full stack trace on the browser screen.I see in the Table code , it does SWT.error call. I have updated the ErrorHandler.js file processJavaScriptErrorInResponse and processJavaScriptError methods to suppress errors being displayed on the screen and I know these wont help as its a server error. I have a few questions -
1. Is this a known error as I am unable to find an issue with the code.
Any hints/pointers to what I may be doing wrong is welcome.
2. How can I prevent this error from breaking the application and being displayed on the screen? I feel that I can show an error page on this occasion using the general Servlet-Error page mechanism. But I dont want to that. I want the error to be logged in my server logs and application to run smoothly.
3. Does SWT.error logs shows on the screen? If so, I think there will be a way to suppress them.
I am using RAP 1.5m4.
Any help is appreciated.
[Updated on: Tue, 21 February 2012 07:34] Report message to a moderator
|
|
|
Re: Http status 500 - Argument is null exception shown on screen [message #803374 is a reply to message #803323] |
Tue, 21 February 2012 08:55 |
Ivan Furnadjiev Messages: 2426 Registered: July 2009 Location: Sofia, Bulgaria |
Senior Member |
|
|
Hi,
if this is a bug in RAP, but not in your code, a full stack trace of the
IAE will help us to trace it down. A simple self running snippet to
reproduce the issue will be welcomed too. Please file a bugzilla with
your findings. Normally, if uncatched server-side exception occurs,
there is no guarantee that your application is still operational. That's
why we show the error on the screen and break the client as well.
Solution will be to avoid the server-side exception (recommended) or to
catch it in your code.
Best,
Ivan
On 2/21/2012 9:32 AM, Avrajit Chatterjee wrote:
> Hi,
>
> Sometimes we get this unusual error when we do random clicks on our
> RAP application.
> "java.lang.IllegalArgumentException:Argument cannot be null". This
> cannot be always reproduced. The most annoying part is that it shows a
> HTTP Status 500 with the full stack trace on the browser screen.I see
> in the Table code , it does SWT.error call. I have updated the
> ErrorHandler.js file processJavaScriptErrorInResponse and
> processJavaScriptError methods to suppress errors being displayed on
> the screen and I know these wont help as its a server error. I have a
> few questions -
>
> 1. Is this a known error as I am unable to find an issue with the code.
> Any hints/pointers to what I may be doing wrong is welcome.
>
> 2. How can I prevent this error from breaking the application and
> being displayed on the screen? I feel that I can show an error page on
> this occasion using the general Servlet-Error page mechanism. But I
> dont want to that. I want the error to be logged in my server logs and
> application to run smoothly.
>
> 3. Does SWT.error logs shows on the screen? If so, I think there will
> be a way to suppress them.
>
> I am using RAP 1.5m4.
>
> Any help is appreciated.
--
Ivan Furnadjiev
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03930 seconds