[ https://issues.apache.org/jira/browse/AXIS2-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903692#comment-17903692 ]
Robert Lazarski edited comment on AXIS2-6077 at 12/6/24 3:40 PM: ----------------------------------------------------------------- I looked at the logs and those timeouts could be lots of things, however what you can do is change this: 20/11 09:39:41,375 TRACE [pool-5-thread-1] [HTTPSenderImpl:816] Making new ConnectionManager 20/11 09:39:41,376 TRACE [pool-5-thread-1] [HTTPSenderImpl:190] Thread[pool-5-thread-1,5,main] PostMethod org.apache.commons.httpclient.methods.PostMethod@1249585 / org.apache.commons.httpclient.HttpClient@d7f6b4 That log statement clearly indicates the buggy history of httpclient 3.x. Axis2 1.7.9 allows you to optionally change that to httpclient4 in your axis2.xml. See below for the http example - same thing for https: <transportSender name="http" class="org.apache.axis2.transport.http.impl.httpclient4.HTTPClient4TransportSender"> Axis 2.0.0 will be using httpclient5. No guarantee that solves your problem as your problem could be on the network or the server your client is trying to connect to. Still, httpclient 3.x is a red flag. was (Author: robertlazarski): I looked at the logs and those timeouts could be lots of things, however what you can do is change this: 20/11 09:39:41,375 TRACE [pool-5-thread-1] [HTTPSenderImpl:816] Making new ConnectionManager 20/11 09:39:41,376 TRACE [pool-5-thread-1] [HTTPSenderImpl:190] Thread[pool-5-thread-1,5,main] PostMethod org.apache.commons.httpclient.methods.PostMethod@1249585 / org.apache.commons.httpclient.HttpClient@d7f6b4 That log statement clearly indicates the buggy history of httpclient 3.x. Axis2 1.7.9 allows you to optionally change that to httpclient4 in your axis2.xml. See below for the http example - same thing for https: <transportSender name="http" class="org.apache.axis2.transport.http.impl.httpclient4.HTTPClient4TransportSender"> Axis 2.0.0 will be using httpclient5. No guarantee that solves your problem as your problem could be on the network or the server your client is trying to connect to. Still, httpclient 3.x is a red flag. i > 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