().setTimeOutinMillis()
for
every call made to another webservice. Do i need to
cleanup
transport
after every call or does the AXIS2-2883 fix cleans up
after
every
request. Is these issue also fixed
().getOptions().setTimeOutinMillis()
for
every call made to another webservice. Do i need to cleanup
transport
after every call or does the AXIS2-2883 fix cleans up after
every
request. Is these issue also fixed for https
webservice. Do i need to
cleanup
transport
after every call or does the AXIS2-2883 fix cleans up
after
every
request. Is these issue also fixed for https ??
Regards,
Nirav
,
Can you advice??
I am using Axis 2.1.5.1... I do a
soapBinding._getServiceClient().getOptions().setTimeOutinMillis() for
every call made to another webservice. Do i need to cleanup transport
after every call or does the AXIS2-2883 fix cleans up after every
request. Is these issue also
2.1.5.1... I do a
soapBinding._getServiceClient().getOptions().setTimeOutinMillis()
for
every call made to another webservice. Do i need to cleanup
transport
after every call or does the AXIS2-2883 fix cleans up after
every
Hi Thilina/Glen,
Can you advice??
I am using Axis 2.1.5.1... I do a
soapBinding._getServiceClient().getOptions().setTimeOutinMillis() for every
call made to another webservice. Do i need to cleanup transport after every
call or does the AXIS2-2883 fix cleans up after every request
every call or does the AXIS2-2883 fix cleans up after every
request. Is these issue also fixed for https ??
Regards,
Nirav
On Mon, Jan 25, 2010 at 8:01 AM, Nirav Shah snirav.s...@gmail.com
mailto:snirav.s...@gmail.com wrote:
Anyone??Would appreciate valuable suggestions
i need to cleanup transport
after every call or does the AXIS2-2883 fix cleans up after every
request. Is these issue also fixed for https ??
Regards,
Nirav
On Mon, Jan 25, 2010 at 8:01 AM, Nirav Shah snirav.s...@gmail.com
mailto:snirav.s...@gmail.com wrote:
Anyone
Anyone??Would appreciate valuable suggestions..
On Sat, Jan 23, 2010 at 12:35 PM, Nirav Shah snirav.s...@gmail.com wrote:
Hi,
I have been reading some different sides of this defect. Based on the
Release Email sent out, it said the Connections are released automatically
and should not
Hi,
I have been reading some different sides of this defect. Based on the
Release Email sent out, it said the Connections are released automatically
and should not need either AUTO_RELEASE_CONNECTION or *the
*MultithreadedHttpConnectionManager.
But the defect had a comment saying either the
10 matches
Mail list logo