[
http://issues.apache.org/jira/browse/AXIS2-1113?page=comments#action_12442226 ]
Hari H Krishna commented on AXIS2-1113:
---------------------------------------
[[ Old comment, sent by email on Fri, 15 Sep 2006 17:04:34 +0530 ]]
Hello Deepal,
Thanks for your update. I am sending over this note due to a serious
customer problem that we are facing today.
I have a question for you.
You said this is not a problem with 1.x and not with 2.x, does this mean
that this problem has been fixed in 2.x. In particular I am talking about
the function "void org.apache.axis.client.Call.invokeOneWay(Object[] arg0)"
Actually, the internal implementation of invokeOneWay creates a runnable
object and is spawning a new thread, now our component is inturn
multi-threaded that spawns multiple invokeOneWayRequests. After certain
limit all the ports are occupied and we are encountering a port not
found(infact a socket connect) exception.
Would it be possible to overcome this problem in Apache 2x?
Any help on this is HIGHLY appreciated
Regards,
Hari H Krishna,
Tech Lead-LTA Adapters, Autonomic Computing,
India Software Labs, IBM Software Group,
Embassy Golf Links Business Park, Bangalore.
Phone: 91-80-41055476/Cell: (+91)94413-58865
"Deepal
Jayasinghe
(JIRA)" To
<[EMAIL PROTECTED]> Hari H Krishna/India/[EMAIL PROTECTED]
cc
08/09/2006 12:15
Subject
[jira] Resolved: (AXIS2-1113) If
callObjec.invokeOneWay() is being
used for a huge data transfer,
client side system is encountering
Socket create exception
[ http://issues.apache.org/jira/browse/AXIS2-1113?page=all ]
Deepal Jayasinghe resolved AXIS2-1113.
--------------------------------------
Resolution: Fixed
I think this is an Axis 1.x bug , so I am closing the isssue. please
re-open , if this is an Axis2 bug
client side system is encountering Socket create exception
------------------------------------------------------------------------------------------------------------------------------
spawns a new thread for each call to invokeOne way.
invokeOneWay() function internally to send events/data to WS-Notification
resource. This functionality is working fine when small number of events
are sent, but when large number of events are sent, too many ports are
being opened and at certain point the ws-notification is left with no port
and is throwing Socket create exception.
that are being created inside invokeOneWay().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
> If callObjec.invokeOneWay() is being used for a huge data transfer, client
> side system is encountering Socket create exception
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2-1113
> URL: http://issues.apache.org/jira/browse/AXIS2-1113
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: transports
> Environment: ALL
> Reporter: Hari H Krishna
>
> Basic problem is, invokeOneway() function of call object internally spawns a
> new thread for each call to invokeOne way.
> One of our sub-component that is a part of Generic Log Adapter uses
> invokeOneWay() function internally to send events/data to WS-Notification
> resource. This functionality is working fine when small number of events are
> sent, but when large number of events are sent, too many ports are being
> opened and at certain point the ws-notification is left with no port and is
> throwing Socket create exception.
> The requirement is, there shoud be a way to control the number of threads
> that are being created inside invokeOneWay().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
