struts2 parameters invalid chunk ignored -


I am working on a project in struts 2, hibernate. I am using jqgrid (json data) I upgraded my struts version 2.3.16 (the first 2.1.8) and jquery grid and jquery version to 3.7.0, which caused my previous problems (due to version mismatch) Has solved.

But right now, I am getting an error and my Junkyard data is not showing

  mysql-connector-java-5.1.13-bin.jar, struts2 -fullhibernatecore-plugin-2.2.2-GA.jar, Commons Collection, 3.2.jar, Commons-Bannutils- 1.8.0.jar, Commons-DBCP-1.2.1.jar, Commons-Logging-API-1.1.Jar, Stropes 2-Core-2.3.16.jar, Xvercover-Core-2.3.16.jpg, OGN-3.0. 6, Jawashish-3.11.0. GAGR, Freemar-2.3.19.jar, Commons-file uploads -1.3.jar, Commons-IO-2.2.jar, Commons-Lang3-3.1, Commons-Logging- 1.1.3.jar, asm-3.3 Jar, asm-commons-3.3.jar, struts2-jquery-grid-plugin-3.7.0.jar, struts2-jquery-plugin-3.7.0.jar, struts2-json-plugin-2.3.16.jar  

I am using Tomcat 6.0.35.

I upgraded my struts version to 2.3.16 (the first 2.1.8) and has the Jquery grid and jquery version 3.7.0, which resolves my previous problems (due to version mismatch) .

But right now, I am getting an error and my Junkbird data is not showing.

Log: Here is the log

  org.apache.tomcat.util.http.Paramet Ence ProcessPameters Information: Byte [0 ], With the cost of the invalid segment and [null] starting from [i]  

I updated the Jason Plugin on 2.3.16, but that did not help < / P>

My library structure -

  mysql-connector-java-5.1.13-bin.jar, struts2-fullurbernatecore-plugin-2.2.2-GA.jar, Commons - Collections-3.2.jar, Commons-Beanut ils-1.8.0.jar, Commons-DBCP-1.2.1.jar, Commons-Logging-API-1.1.j, str P2-Core-2.3.16.j, Axwerk-Core -2.3.16.Jere, OGN-3.0.6.Jar, JavaSTistic-3.11.0.Gajr, Freemar-2.3.19.jar, Commons-File Upload- 1.3.jar, Commons-O-2.2.jar, Commons-lang3-3.1.jar, Commons-Logging.1.1.3. Jar, ash-3.3.jar, asm-commons-3.3.jpg, strokes2-jquery-grid -plugin-3.7.0.jar, Straits-2 -Jazzery-Plugin -3.7.0.jar, Struts-2-Jason-Plugin-2.3.16.jar  

I have a tinker 6.0 I'm using .35.

This is a minor bug that was introduced in Apache 6.0.35 and Apache 6.0.36 Was decided. See this link for more information


Comments