java - Request Entity Too Large (JasperServer / Apache / Tomcat) -


i following error when try access jasperreports server pages:

request entity large requested resource /jasperserver/olap/viewolap.html not allow request data requests, or amount of data provided in request exceeds capacity limit.

i checked apache log files , got following error in mod_jk.log

[thu nov 10 10:25:00 2016][8964:3876] [error] ajp_marshal_into_msgb::jk_ajp_common.c (517): failed appending query string of length 7417

i tried many different ways solve it.

i added maxhttpheadersize , max_packet_size attributes ajp connect of tomcat (server.xml):

<connector port="8010" protocol="ajp/1.3" connectiontimeout="20000" redirectport="8443" maxhttpheadersize="65536" max_packet_size="65536" />

also added limitrequestline, limitrequestbody, limitrequestfieldsize , limitrequestfields apache httpd.conf file (added end of file without virtualhost):

limitrequestline 65536 limitrequestbody 0 limitrequestfieldsize 65536 limitrequestfields 10000

i still getting error above.

i found suggestions add max_packet_size workers.properties of apache. if add attribute http 400 error , white page. that's why commented property in workers.properties:

#worker.jasper.max_packet_size=65536

i restarted services after changing configurations.

when access same pages via http-connector of tomcat (http://hostname:8081/jasperserver/..) works fine. when access via ajp-connector of apache (http://hostname/jasperserver/..) error. think there should problem ajp-connector.

apache: 2.4.12 jasperreports server: 6.2.1 apache tomcat version 8.0.14:

does have suggestion have solve issue?

i figured out problem.

the attribute in server.xml tomcat has packetsize , not max_packet_size

see documentation ajp connector

after renaming it, works fine.

here configurations:

tomcat server.xml:

connector port="8010" protocol="ajp/1.3" redirectport="8443" packetsize="65536"

apache workers.properties:

worker.jasper.max_packet_size=65536

if afterwards error:

request-uri long

the requested url's length exceeds capacity limit server.

you have set following attributes in apache httpd.conf file:

limitrequestline 65536 limitrequestbody 0 limitrequestfieldsize 65536 limitrequestfields 10000

i hope answer helps others too.


Comments

Post a Comment

Popular posts from this blog

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

i getting "__type": "com.amazon.coral.service#serializationexception" as reply in postman & in test console in api gateway trying post record directly dynamodb using api proxy services.. referring aws article - https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/ here's mapping { "tablename": "tablenamegoeshere", "item": { "id" : "$context.requestid" "eventname" : "$input.path('$.eventname')", "timestamp" : $input.path('$.timestamp'), "answers": "$util.parsejson($input.path('$.answers'))" } } update: did asked ... , worked if try add array of json objects gives me above same error - here's trying now. please - couldnt find on google well #set($inputroot = $input.path('$')) { "tablename": "answer", "item": {
Read more

asp.net - Problems sending emails from forum -

i have been redesigning site has message board, has been written guy looked after site. it has few problems , written in .asp , uses .mdb files database. you can see whole thing here . feel free post if helps, test thing have set using original files , new database. the basic problem when posts message, supposed email sent them, have posted it. when replies, originator supposed message, replier has been posted. i’d have thought @ point in process there should script/file in postmessage.asp? the postmessage.asp page below. <% option explicit %> <!-- #include virtual="common/adovbs.inc" --> <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="microsoft frontpage 4.0"> <meta name="progid" content="frontpage.editor.document"> <title>new page 2</title> <base target="_self"
Read more