cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-3466) HTTP client sends empty messages when FINE log level is enabled
Date Tue, 05 Jul 2011 12:30:16 GMT

    [ https://issues.apache.org/jira/browse/CXF-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059860#comment-13059860
] 

Christian Schneider commented on CXF-3466:
------------------------------------------

2.4.1 is already out


> HTTP client sends empty messages when FINE log level is enabled
> ---------------------------------------------------------------
>
>                 Key: CXF-3466
>                 URL: https://issues.apache.org/jira/browse/CXF-3466
>             Project: CXF
>          Issue Type: Bug
>          Components: Transports
>    Affects Versions: 2.4
>            Reporter: Alessio Soldano
>            Assignee: Christian Schneider
>             Fix For: 2.4.1
>
>
> I'm testing JBossWS-CXF integration with Apache CXF 2.4.0 and I'm seeing a weird behaviour
in HTTPConduit.
> Basically, when the org.apache.cxf log category is set to DEBUG (I'm using log4j logging,
that's FINE level) I see empty(1) messages being sent from client to server. Setting the log
level to INFO, remove the problem. So I looked for "isLoggable(Level.FINE" strings in the
CXF sources and tried commenting out them one by one to identify the culprit. Finally isolated
it in the following code in HTTPConduit::onFirstWrite()
> {code:title=HTTPConduit.java|borderStyle=solid}
>             if (LOG.isLoggable(Level.FINE)) {
>                 LOG.fine("Sending "
>                     + connection.getRequestMethod() 
>                     + " Message with Headers to " 
>                     + connection.getURL()
>                     + " Conduit :"
>                     + conduitName
>                     + "\nContent-Type: " + connection.getContentType() + "\n");
>             }
> {code}
> My guess is one of the calls to the connection in there compromise its state.
> (1) actually, capturing the network traffic reveals the http headers only are written,
the body is completely missing

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message