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 "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2010/12/19 12:37:04 UTC
[jira] Updated: (AXIS2-4582) AXIS2-3005 - WARNING: Cannot set
header. Response already committed. is logged when ever a Axis2 based
webservice is called
[ https://issues.apache.org/jira/browse/AXIS2-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samisa Abeysinghe updated AXIS2-4582:
-------------------------------------
Fix Version/s: (was: 1.3)
1.6
> AXIS2-3005 - WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-4582
> URL: https://issues.apache.org/jira/browse/AXIS2-4582
> Project: Axis2
> Issue Type: Bug
> Affects Versions: 1.4.1, 1.4, 1.3, 1.2
> Environment: WebSphere 5.1.1.19
> HP UX operating system
> Reporter: Usman Chaudhry
> Priority: Minor
> Fix For: 1.6
>
>
> This has already been reported in JIRA as a bug. Please see below for reference.
> https://issues.apache.org/jira/browse/AXIS2-3005
> It says, it has been fixed in v1.3 but that is not the case. Issue still exist in 1.4 as well.
> ----------------------------------------
> 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.19
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org