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

EMERSON commented on AXIS2-6077:
--------------------------------

Hi Robert,

Unfortunatly I can't do it. My appliaction doesn't ready to run on Java 17. 
Fourthermore, the problem happens only in production environmet and with low 
frequency. Recently, we descovered that the customer network had some problems 
that were solved by our customer. After that, the problema didn't appear again. 

I think the network instability caused the problem, didn't it? Does Axis2 2.0.0 
provide more protection against network instability? 

 

> Write timeout doesn't work sometimes
> ------------------------------------
>
>                 Key: AXIS2-6077
>                 URL: https://issues.apache.org/jira/browse/AXIS2-6077
>             Project: Axis2
>          Issue Type: Bug
>          Components: kernel, TCP transport
>    Affects Versions: 1.7.9
>         Environment: OS: Linux Gentoo kernel 3.2.1
> Java: 
> openjdk version "1.8.0_181"
> OpenJDK Runtime Environment (IcedTea 3.9.0) (Gentoo icedtea-3.9.0)
> OpenJDK Server VM (build 25.181-b13, mixed mode)
>            Reporter: EMERSON
>            Priority: Major
>         Attachments: gwfiscal_axis2.log
>
>
> Sometimes the write timeout doesn't work and the write in the socket takes 
> longer than write timeout was configured. I set it up for 15 seconds, but 
> note in the log below that the WriteTo takes 4 minutes to give up and try 
> again:
>  
> 20/11 09:04:11,485 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:148] 
> contentType returned =text/xml; charset=UTF-8
> 20/11 09:04:11,547 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:51] start 
> writeTo()
> 20/11 09:04:11,548 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:52]   
> preserve=false
> 20/11 09:04:11,549 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:53]   
> isOptimized=false
> *20/11 09:04:11,550 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:54]   
> isDoingSWA=false*
> *20/11 09:08:11,746 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:81] end 
> writeTo()*
> 20/11 09:08:11,811 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:51] start 
> writeTo()
> 20/11 09:08:11,811 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:52]   
> preserve=false
> 20/11 09:08:11,812 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:53]   
> isOptimized=false
> 20/11 09:08:11,813 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:54]   
> isDoingSWA=false
> 20/11 09:08:11,879 DEBUG [pool-5-thread-1] [SOAPMessageFormatter:81] end 
> writeTo()
> 20/11 09:08:12,480 TRACE [pool-5-thread-1] [HTTPSenderImpl:300] Handling 
> response - 200
>  
> I attached the complete log file with this case described above end others, 
> it doesn't always take 4 minutes, this time may vary.
>  
> Please, let me know if there is a workaround and if it will be fixed in the 
> next Axis2 release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to