axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5537) tcp transport problem: multithread blocking sending doesn't work
Date Fri, 03 Jul 2015 23:40:04 GMT


Hiranya Jayathilaka commented on AXIS2-5537:

TCP transport went through an overhaul after this issue was raised. This scenario works correctly

> tcp transport problem: multithread blocking sending doesn't work
> ----------------------------------------------------------------
>                 Key: AXIS2-5537
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: TCP transport
>         Environment: jdk1.5, axis2 1.2, tomcat 6.0
>            Reporter: Yattie Yang
> I create a webservices to send datas, and http,jms transport works fine with multithread
sending, but not for tcp.
> TCP uses ws-addressing in both client and server sides, and it works fine in single thread.
In the case of multithread,
> e.g., 
> 1. a thread T1 created to send data D1, use a ServiceClient object in blocking way(sendReceive())
> 2. meanwhile, another thread T2 created to send data D2
> 3. T1 sent the data and has not received the reply;(need more time)
> 4. T2 sent the data and received the reply;(T2 works OK)
> 5. T1 throws a Exception: Socket output is already shutdown
> I use the seperator listener by options.setUseSeparateListener(true) and similarlly "socket
shutdown" exception
> My question is:
> when using two seperate ServiceClient, there should be two socket connection. It works
fine for http and jms, but why not work for
> tcp? Is there something I missed when engaged ws-addressing or some bugs there?

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message