[ 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 > 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]