[ https://issues.apache.org/jira/browse/AXIS2-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903428#comment-17903428 ]
Robert Lazarski commented on AXIS2-6077: ---------------------------------------- Can you retry with the latest code in Github and Tomcat 11 or Wildfly 32 with JDK 17? The latest code exclusively uses httpclient5 and we are about to release Axis 2.0.0. To compile Axis2 from source, you need to first compile ws-axiom from source. https://github.com/apache/ws-axiom https://github.com/apache/axis-axis2-java-core Note that you need to update your axis2.xml file transport for http and https to org.apache.axis2.transport.http.impl.httpclient5.HTTPClient5TransportSender and the messageFormatter sections to org.apache.axis2.kernel.http i.e org.apache.axis2.kernel.http.XFormURLEncodedFormatter. We are so close to the Axis 2.0.0 release that realistically I need testing done with the latest code since nearly every file has changed since 1.7.9 to support the transition to jakarta. > 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