axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5742) client recieves empty SOAP response message
Date Tue, 16 Feb 2016 19:32:18 GMT

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

Andreas Veithen commented on AXIS2-5742:
----------------------------------------

Couple of comments/questions:
- Why is this issue labelled/flagged with "patch"? Where is the patch?
- Logs from a 1ms time window are not useful.
- Logs from application code (obao.ssm.communication.protocol.ProtocolOutPollerV114 in this
case) are not useful unless they show the exception received from Axis2.
- Experience shows that this type of issue is often caused by misconfigured clients. You should
add the relevant code snippet.
- Bug reports are more likely to receive attention if the issue is reproducible with the latest
release (1.7.0 in this case).

> client recieves empty SOAP response message
> -------------------------------------------
>
>                 Key: AXIS2-5742
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5742
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.6.3, 1.6.4
>         Environment: jorg.apache.axis2.transport.SimpleAxis2Server
>            Reporter: Frédéric Movsessian
>              Labels: patch
>
> when used as a client of gsoap server (https), some responses from server are considered
by axis2 as empty. 
> tcpdump shoes that there is actually a response.
> This problem seems to occurs when sending lot of SOAP requests in a short amount of time.
> This problem doesn't occurs in axis2-1.3 version (so I roll back to 1.3)
> traces are as follows :
> [ad90cssm@ssmsce2 logs]$ grep "14:29:11,863" obaossm-DebugFull.log.1.1429
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "HTTP/1.1 200 OK[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "Server: gSOAP/2.7[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "Content-Type: text/xml; charset=utf-8[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "Content-Length: 2180[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "Connection: close[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] DEBUG httpclient.wire.header
 - << "[\r][\n]"
> 2016-02-04 14:29:11,863 [574fad53-1566-44ab-a664-ac7f2d3293ed] ERROR obao.ssm.communication.protocol.ProtocolOutPollerV114
 - Connection error for suppressEquipments at endpoint https://10.57.137.54:60443/  : null



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message