Problem:

I set up sending to a web-tracker. I'm pretty sure that entered settings are correct (e.g. "Test" button in EurekaLog project settings dialog may work, or sending from real application may work). However, sending (either from "Test" button or from real application) may fail sometimes (or most of the times). The failure is either entire bug report is not sent, or bug report is sent, but bug report file is not attached.

Reason:

Your web-server or web-tracker may have size limitation for requests, replies, or file uploads. Sending will fail if current report is greater than this size limit. Sending will succeed if current report is less than this size limit. If API requires two steps (to create bug report and attach file) - then bug report itself may be created successfully (as small text), but file attaching will fail (as file is large).

Solution:

1. Diagnose that problem is indeed some sort of a size limit:
   1. Use run-time debug mode to add a logging to your application;
   2. Use Fiddler or WireShark to monitor network traffic between your application and web-tracker;
   3. There should be some sort of error messages/code indicating failure due to size limitation.
2. Increase size limit or remove it.

See also:

• file uploads, upload_max_filesize, max_file_uploads, post_max_size, memory_limit settings in PHP
• JIRA Character Limits on Comments and Description
• Mantis file upload limits
• FogBugz attachment limits
• maxattachmentsize setting in BugZilla
• (Mantis) All file attaches has size of 0 bytes