DWR

"Failed to Read Input" popup appearing too frequently on the jsp page

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: DWRP
  • Documentation Required:
    No
  • Description:
    Hide
    There is a popup that shows up from the environment overview page. This is caused by an unfulfilled ajax request. In versions prior to 3.4.x, this would olnly show up when the server was bounced and the page was still open in a browser. Now, this popup shows up periodically when the server is running, and a lot more than it should. We need to determine the cause of this and see if we can reduce the frequency of these popups occurring.

    Applied following scenarios for this issue, but still we are getting same error.

    1. Tried with following approach:
    Replacing:
    in = new BufferedReader (new InputStreamReader (req.getInputStream ()));
    with:
    in = req.getReader ();
    With reference:
    http://www.codeweblog.com/solve-dwr-framework-failed-to-read-input-problems/

    2. Changed dwr's internal timeout period from 10sec. to 1min. in following file.
    dwr\java\org\directwebremoting\engine.js

    One more thing we observed is, this error we are not getting on all machines but on some.
    Show
    There is a popup that shows up from the environment overview page. This is caused by an unfulfilled ajax request. In versions prior to 3.4.x, this would olnly show up when the server was bounced and the page was still open in a browser. Now, this popup shows up periodically when the server is running, and a lot more than it should. We need to determine the cause of this and see if we can reduce the frequency of these popups occurring. Applied following scenarios for this issue, but still we are getting same error. 1. Tried with following approach: Replacing: in = new BufferedReader (new InputStreamReader (req.getInputStream ())); with: in = req.getReader (); With reference: http://www.codeweblog.com/solve-dwr-framework-failed-to-read-input-problems/ 2. Changed dwr's internal timeout period from 10sec. to 1min. in following file. dwr\java\org\directwebremoting\engine.js One more thing we observed is, this error we are not getting on all machines but on some.
  1. dwr1.log
    (6 kB)
    nilesh subhash mantri
    22/Feb/12 3:52 AM

Activity

Hide
David Marginian added a comment - 22/Feb/12 5:21 AM

We have very clear instructions for creating JIRA issues on the JIRA login page and on our support page - http://directwebremoting.org/dwr/support/index.html. You have not followed those instructions therefore this issue is being closed. Our support page also has a link to a troubleshooting page which it appears you have not taken the time to read.

There is no 3.4.x version of DWR and ParseUtil does not even exist in the latest 3.x versions of DWR.

Show
David Marginian added a comment - 22/Feb/12 5:21 AM We have very clear instructions for creating JIRA issues on the JIRA login page and on our support page - http://directwebremoting.org/dwr/support/index.html. You have not followed those instructions therefore this issue is being closed. Our support page also has a link to a troubleshooting page which it appears you have not taken the time to read. There is no 3.4.x version of DWR and ParseUtil does not even exist in the latest 3.x versions of DWR.
Hide
David Marginian added a comment - 22/Feb/12 5:32 AM

Also this is likely due to a network issue, problem with a proxy (apache in front of DWR?), etc. and not a bug in DWR. You need to do a lot more investigative work.

Show
David Marginian added a comment - 22/Feb/12 5:32 AM Also this is likely due to a network issue, problem with a proxy (apache in front of DWR?), etc. and not a bug in DWR. You need to do a lot more investigative work.
Hide
nilesh subhash mantri added a comment - 22/Feb/12 8:03 PM

Sorry David, The version I had given is incorrect, i am using DWR 2.0.10.
and Thanks for the reply.

I want to know Is there any configuration setting for socket timeout in DWR jar?

Show
nilesh subhash mantri added a comment - 22/Feb/12 8:03 PM Sorry David, The version I had given is incorrect, i am using DWR 2.0.10. and Thanks for the reply. I want to know Is there any configuration setting for socket timeout in DWR jar?
Hide
David Marginian added a comment - 22/Feb/12 8:36 PM

The stack trace in the log file you attached has a line that is a comment in the 2.0.10 codebase. So the log you posted is not accurate with version 2.0.10.

Regardless, a quick search of the mailing list revealed:

http://dwr.2114559.n2.nabble.com/IOException-happens-frequently-tc5397409.html#a5397410

Which revealed this:
http://markmail.org/message/ee6or5eec7odj3zn

It appears this is may be a bug in Tomcat, what version are you using?

Show
David Marginian added a comment - 22/Feb/12 8:36 PM The stack trace in the log file you attached has a line that is a comment in the 2.0.10 codebase. So the log you posted is not accurate with version 2.0.10. Regardless, a quick search of the mailing list revealed: http://dwr.2114559.n2.nabble.com/IOException-happens-frequently-tc5397409.html#a5397410 Which revealed this: http://markmail.org/message/ee6or5eec7odj3zn It appears this is may be a bug in Tomcat, what version are you using?
Hide
nilesh subhash mantri added a comment - 22/Feb/12 9:42 PM

I am using tomcat 6.0.32

Sorry David, I forgot to tell you that, for tracing exact error I changed dwr.jar and put logger in ParseUtil.java file. And I got attached logs.

I found the SocketTimeoutException on line: "String line = in.readLine();"

And with reference to link you had mentioned i.e.

BufferedReader in = new BufferedReader(new InputStreamReader( req.getInputStream()));
Replacing this line by
BufferedReader in = req.getReader();

but still I got same exception, so is there any other resolution for this?

Thanks in advance.

Show
nilesh subhash mantri added a comment - 22/Feb/12 9:42 PM I am using tomcat 6.0.32 Sorry David, I forgot to tell you that, for tracing exact error I changed dwr.jar and put logger in ParseUtil.java file. And I got attached logs. I found the SocketTimeoutException on line: "String line = in.readLine();" And with reference to link you had mentioned i.e. BufferedReader in = new BufferedReader(new InputStreamReader( req.getInputStream())); Replacing this line by BufferedReader in = req.getReader(); but still I got same exception, so is there any other resolution for this? Thanks in advance.
Hide
David Marginian added a comment - 23/Feb/12 4:31 AM

Nilesh, you already created DWR-563 which I closed because you failed to follow the support instructions that I keep telling you to follow - http://directwebremoting.org/dwr/support/index.html. This issue is no different and I don't understand why you refuse to follow the directions.

The directions exist for a good reason. This is not a place for discussion, this is a place for reporting bugs in DWR. You will have a much wider audience if you follow the directions and contact the users mailing list. Before you do so you need to look at our troubleshooting page and provide a lot more information - http://directwebremoting.org/dwr/support/common_problems.html. I strongly recommend that you use a HTTP Debugging proxy and take a look at the request size and send along that and a lot more information in you message to the list.

Show
David Marginian added a comment - 23/Feb/12 4:31 AM Nilesh, you already created DWR-563 which I closed because you failed to follow the support instructions that I keep telling you to follow - http://directwebremoting.org/dwr/support/index.html. This issue is no different and I don't understand why you refuse to follow the directions. The directions exist for a good reason. This is not a place for discussion, this is a place for reporting bugs in DWR. You will have a much wider audience if you follow the directions and contact the users mailing list. Before you do so you need to look at our troubleshooting page and provide a lot more information - http://directwebremoting.org/dwr/support/common_problems.html. I strongly recommend that you use a HTTP Debugging proxy and take a look at the request size and send along that and a lot more information in you message to the list.
Hide
David Marginian added a comment - 23/Feb/12 4:38 AM

Also, I would like to add that I don't really see how this is a DWR issue. It seems either to be a network issue or an issue with a proxy (you haven't even told us your configuration). Tomcat has a "connectionTimeout" attribute on the connector you are using. You should check that setting and perhaps modify it.

Show
David Marginian added a comment - 23/Feb/12 4:38 AM Also, I would like to add that I don't really see how this is a DWR issue. It seems either to be a network issue or an issue with a proxy (you haven't even told us your configuration). Tomcat has a "connectionTimeout" attribute on the connector you are using. You should check that setting and perhaps modify it.
Hide
nilesh subhash mantri added a comment - 23/Feb/12 11:17 AM

Hi David, I searched in bug tracking system for an issue, but I don't get any directions on this issue.

I verify server.xml file of tomcat for connection_timeout setting and modified respectively, but I don't get any resolution

I also mentioned that 'Failed to read input' popup is not getting on all machines but on some machines IE browser.

Configuration of machines are also the same, IE Version that we are using is 8.0.6001

Show
nilesh subhash mantri added a comment - 23/Feb/12 11:17 AM Hi David, I searched in bug tracking system for an issue, but I don't get any directions on this issue. I verify server.xml file of tomcat for connection_timeout setting and modified respectively, but I don't get any resolution I also mentioned that 'Failed to read input' popup is not getting on all machines but on some machines IE browser. Configuration of machines are also the same, IE Version that we are using is 8.0.6001
Hide
David Marginian added a comment - 23/Feb/12 11:29 AM

Nilesh,
This issue is closed. Follow the instructions you have been provided with several times now.

Show
David Marginian added a comment - 23/Feb/12 11:29 AM Nilesh, This issue is closed. Follow the instructions you have been provided with several times now.

People

Dates

  • Created:
    22/Feb/12 3:52 AM
    Updated:
    23/Feb/12 11:29 AM
    Resolved:
    22/Feb/12 5:21 AM