axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Usman Chaudhry (JIRA)" <j...@apache.org>
Subject [jira] Created: (AXIS2-4582) AXIS2-3005 - WARNING: Cannot set header. Response already committed. is logged when ever a Axis2 based webservice is called
Date Fri, 11 Dec 2009 05:43:18 GMT
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: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.2, 1.3, 1.4, 1.4.1
         Environment: WebSphere 5.1.1.19
HP UX operating system 
            Reporter: Usman Chaudhry
            Priority: Minor
             Fix For: 1.3


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.


Mime
View raw message