Mailing-List: contact java-dev-help@axis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@axis.apache.org
Date: Fri, 3 Jul 2015 23:40:04 +0000 (UTC)
From: "Hiranya Jayathilaka (JIRA)" <jira@apache.org>
To: java-dev@axis.apache.org
Message-ID: <JIRA.12377136.1188436978000.96081.1435966804852@Atlassian.JIRA>
In-Reply-To: <JIRA.12377136.1188436978000@Atlassian.JIRA>
References: <JIRA.12377136.1188436978000@Atlassian.JIRA>
 <JIRA.12377136.1188436978369@arcas>
Subject: [jira] [Commented] (AXIS2-5537) tcp transport problem: multithread
 blocking sending doesn't work
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hiranya Jayathilaka commented on AXIS2-5537:
--------------------------------------------

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

> tcp transport problem: multithread blocking sending doesn't work
> ----------------------------------------------------------------
>
>                 Key: AXIS2-5537
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5537
>             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
(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