nickfelt bc0116f3a0 Add EPP controller logging for XML unmarshalling failures ... This will make it much easier to detect issues with bad EPP XML (e.g. the one in the loadtest action fixed in [] based on the request logs, since otherwise the only indication of what went wrong is the EPP response returned to the client, which we don't store anywhere. Now we'll get log messages that look like this: google.registry.flows.EppController handleEppCommand: EPP request XML unmarshalling failed - "Syntax error at line 2, column 7: cvc-elt.1: Cannot find the declaration of element 'epp'.": (EppController.java:59) {"clientId":"CharlestonRoad","resultCode":2001,"resultMessage":"Command syntax error","xmlBytes":"PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiIHN0YW5kYWxvbmU9InllcyI\/Pgo8ZXBwLz4K"} ======================================== <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <epp/> ======================================== google.registry.flows.EppXmlTransformer$GenericSyntaxErrorException: Syntax error at line 2, column 7: cvc-elt.1: Cannot find the declaration of element 'epp'. at google.registry.flows.EppXmlTransformer.unmarshal(EppXmlTransformer.java:89) at google.registry.flows.EppController.handleEppCommand(EppController.java:56) at google.registry.flows.EppRequestHandler.executeEpp(EppRequestHandler.java:37) at google.registry.flows.EppToolAction.run(EppToolAction.java:33) <snip> ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=137363446		2016-11-02 15:19:34 -04:00
..
registry	Add EPP controller logging for XML unmarshalling failures	2016-11-02 15:19:34 -04:00