Setting ajp_max_data_packet_size causes SIGSEGV
clownshoes19 opened this issue · comments
I'm using Nginx 1.8.0 with this module to proxy requests to JBoss-AS over AJP. When I upload a file I get this error in the Nginx logs, "upstream sent unexpected AJP type: 6 while reading upstream" and this error in the JBoss-AS log, "JBWEB002011: Socket read failed". I thought it was related to ajp_max_data_packet_size based on testing files above and under 8K. I tried changing the setting and even defining it to 8k, but it seems to crash the Nginx worker. Also, if I look at a packet capture, the data is truncated at the 8k boundary. E-mail me at arthurramsey19@gmail.com to obtain the packet capture.
Shouldn't the module split a body larger than ajp_max_data_packet_size into multiple packets?