You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Usman Chaudhry (JIRA)" <ji...@apache.org> on 2009/12/04 13:02:20 UTC
[jira] Commented: (AXIS2-3005) [7/12/07 9:09:32:923 CEST] 82d122f
SRTServletRes W WARNING: Cannot set header. Response already committed. is
logged when ever a Axis2 based webservice is called
[ https://issues.apache.org/jira/browse/AXIS2-3005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785896#action_12785896 ]
Usman Chaudhry commented on AXIS2-3005:
---------------------------------------
This is not resolved yet. Why is it marked fixed? Can we re-open the issue? Or should I create a new one?
> [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3005
> URL: https://issues.apache.org/jira/browse/AXIS2-3005
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: WebSphere 5.1.1.14
> HP UX operating system
> Reporter: Muhammad Hamza Hakim
> Assignee: Charitha Kankanamge
> Priority: Minor
>
> We have implemented Web Services using Axis2 and facing the below mentioned problem when ever the a request is made to Web Service:
> We now installed WebSphere 5.1.1.14
> In the logs we still see below error-messages filling our logs. So the fixpack did not solve this issue. Can you please arrange that these
> messages do not appear anymore in the logs?
>
> [7/12/07 9:09:32:923 CEST] 82d122f SRTServletRes W WARNING: Cannot set header. Response already committed.
> Our Finding:
> WebSphere logs the warning message "SRTServletRes W WARNING: Cannot set header. Response already committed." in SystemOut.log due to Axis2. Axis2 processes the incomming request sends the response and then tries to set a header property in response. Because at this point WebSphere has already committed the response so it logs a warning in the log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.