Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat is the procedure for debugging a production-only error?
    primarykey
    data
    text
    <p>Let me say upfront that I'm so ignorant on this topic that I don't even know whether this question has objective answers or not. If it ends up being "not," I'll delete or vote to close the post.</p> <p>Here's the scenario: I just wrote a little web service. It works on my machine. It works on my team lead's machine. It works, as far as I can tell, on every machine except for the production server. The exception that the production server spits out upon failure originates from a third-party JAR file, and is skimpy on information. I search the web for hours, but don't come up with anything useful.</p> <p>So what's the procedure for tracking down an issue that occurs only on production machines? Is there a standard methodology, or perhaps a category/family of tools, for this?</p> <p>The error that inspired this question has already been fixed, but that was due more to good fortune than a solid approach to debugging. I'm asking this question for future reference.</p> <p>EDIT:<br> The answer to this so far seems to be summed up by one word: <strong>logging</strong>. The one issue with logging is that it requires forethought. What if a situation comes up in an existing system with poor logging, or the client is worried about sensitive data and does not want extensive logging systems in the system in the first place?</p> <blockquote> <p>Some related questions:<br> <a href="https://stackoverflow.com/questions/121306/test-accounts-and-products-in-a-production-system">Test accounts and products in a production system</a><br> <a href="https://stackoverflow.com/questions/1129279/running-test-on-production-code-server">Running test on Production Code/Server</a></p> </blockquote>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload