axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AXIS2-2566) Log errors returned to client as Error, not Debug messages
Date Mon, 03 Mar 2008 15:02:52 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Davanum Srinivas resolved AXIS2-2566.
-------------------------------------

    Resolution: Fixed

> Log errors returned to client as Error, not Debug messages
> ----------------------------------------------------------
>
>                 Key: AXIS2-2566
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2566
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: databinding
>            Reporter: Valerie Masin
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Trivial
>
> My customer gets an error returned when they call my service. The 
> error is generated by Axis because they passed a soap message that 
> does not conform to the schema. But I don't see any errors in my logs. 
> If I turn up the logging level to show Debug messages then I see the 
> message that the customer is seeing. These are reported as Debug level messages.
> I would think that errors should be reported as Error, not Debug, or at least as Warnings.
> Here are the log messages leading up to the failure, and the stack trace. They all logged
as Debug
> Thanks
>  Found AxisOperation : getDocumentList
>  Checking post-conditions for phase "Transport"
>  Checking pre-condition for Phase "Security"
>  Invoking phase "Security"
>  Checking post-conditions for phase "Security"
>  Checking pre-condition for Phase "PreDispatch"
>  Invoking phase "PreDispatch"
>  Invoking Handler 'AddressingFinalInHandler' in Phase 'PreDispatch'
>  Starting WS-Addressing Final IN handler ...
>  No Headers present corresponding to WS-Addressing Final
>  Invoking Handler 'AddressingSubmissionInHandler' in Phase 'PreDispatch'
>  Starting WS-Addressing Submission IN handler ...
>  No Headers present corresponding to WS-Addressing Submission
>  Checking post-conditions for phase "PreDispatch"
>  Checking pre-condition for Phase "Dispatch"
>  Invoking phase "Dispatch"
>  Invoking Handler 'AddressingBasedDispatcher' in Phase 'Dispatch'
>  Invoking Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch'
>  Invoking Handler 'InstanceDispatcher' in Phase 'Dispatch'
>  Invoking Handler 'AddressingWSDLValidationHandler' in Phase 'Dispatch'
>  Checking post-conditions for phase "Dispatch"
>  isReplyRedirected: ReplyTo is null. Returning false
>  Checking pre-condition for Phase "OperationInPhase"
>  Invoking phase "OperationInPhase"
>  Checking post-conditions for phase "OperationInPhase"
>  Checking pre-condition for Phase "soapmonitorPhase"
>  Invoking phase "soapmonitorPhase"
>  Checking post-conditions for phase "soapmonitorPhase"
>  START_ELEMENT: {urn:webservices.docharbor.com}credential:credential
>  Build the OMElelment credentialBy the StaxSOAPModelBuilder
>  Exception caught, Stack Trace follows:
>  org.apache.axis2.AxisFault: java.lang.RuntimeException: Unexpected subelement vjm; nested
exception is: 
>  	java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement vjm
>  	at org.apache.axis2.AxisFault.makeFault(AxisFault.java:321)
>  	at com.docharbor.webservices.DocHarborServicesMessageReceiverInOut.invokeBusinessLogic(DocHarborServicesMessageReceiverInOut.java:463)
>  	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceiver.java:39)
>  	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
>  	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:328)
>  	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:254)
>  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:807)
>  	at javax.servlet.http.HttpServlet.service(HttpServlet.java:908)
>  	at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:771)
>  	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:322)
>  	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
>  	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
>  	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
>  	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:209)
>  	at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:509)
>  	at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:161)
>  	at com.iplanet.ias.web.WebContainer.service(WebContainer.java:580)
>  Caused by: java.lang.RuntimeException: java.lang.RuntimeException: Unexpected subelement
vjm
>  	at com.docharbor.webservices.DocHarborServicesMessageReceiverInOut.fromOM(DocHarborServicesMessageReceiverInOut.java:1369)
>  	at com.docharbor.webservices.DocHarborServicesMessageReceiverInOut.invokeBusinessLogic(DocHarborServicesMessageReceiverInOut.java:112)
>  	... 15 more
>  Caused by: java.lang.RuntimeException: Unexpected subelement vjm
>  	at com.docharbor.webservices.GetDocumentList$Factory.parse(GetDocumentList.java:427)
>  	at com.docharbor.webservices.DocHarborServicesMessageReceiverInOut.fromOM(DocHarborServicesMessageReceiverInOut.java:1216)
>  	... 16 more
>  isReplyRedirected: FaultTo is null. Returning isReplyRedirected
>  isReplyRedirected: ReplyTo is null. Returning false
>  Checking pre-condition for Phase "soapmonitorPhase"
>  Invoking phase "soapmonitorPhase"
>  Checking post-conditions for phase "soapmonitorPhase"
>  Checking pre-condition for Phase "OperationOutFaultPhase"
>  Invoking phase "OperationOutFaultPhase"
>  Checking post-conditions for phase "OperationOutFaultPhase"
>  Checking pre-condition for Phase "PolicyDetermination"
>  Invoking phase "PolicyDetermination"
>  Checking post-conditions for phase "PolicyDetermination"
>  Checking pre-condition for Phase "MessageOut"
>  Invoking phase "MessageOut"
>  Invoking Handler 'AddressingOutHandler' in Phase 'MessageOut'
>  Addressing is disabled .....
>  Checking post-conditions for phase "MessageOut"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message