We are making a Essci40.dll
call via the SciSocketmanager#getHostByAddr method.
The first call is always quick.
Then sometime afterwards ( may take 10 more calls to it, may take 100 more
calls to it ), the method will hang up to 2-3 minutes.
We can verify that the call is somehow using the Windows host file ( we can
change the host file values and see either the FQDM get returned or just the
name, depending on what we change it to ), but we cannot debug any further
because its an IBM/Instantiations DLL.
Can someone tell me exactly what the SciSocketManager>>getHostByAddr is
doing in the DLL?
And has anyone experienced this issue, and have a resolution?
This method has never thrown a walkback or error code, it'll just hang and
eventually returns, but it is painfully slow.
We are running the application on a Windows 2008 server.
Here's an example of our debugging and logging, where it took over 3 minutes
for the DLL call to return a value:
12/23/2019 5:09:22 PM ---
TrsFileNetSOAPXmlSimpleHttpProcessor>>#processCommand START method:
12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>#processCommand
START method: 12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>host = xxx.70.118.37
12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>port = 7102
12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>Got Host Name:
12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>openAsClientToHost:
inside method START 12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- AbtXmlSimpleHttpProcessor>>openAsClientToHost:
inside method , creating new socket stream 12/23/2019 5:09:22 PM
12/23/2019 5:09:22 PM --- SciSocketmanager>>getHostByAddr START, String =
'xx.70.118.37' 12/23/2019 5:09:22 PM
12/23/2019 5:12:59 PM --- SciSocketmanager>>getHostByAddr END method
12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- SciSocketAddress>>abtFromHost = 2722526757
12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>openAsClientToHost:
inside method , set address 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>openAsClientToHost:
inside method , connect and END of method 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>#processCommand
openAsClientToHost method: 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>#processCommand
writeRequestHeaders method: 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>#processCommand
readResponseStatusFrom method: 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- AbtXmlSimpleHttpProcessor>>#processCommand END
method: 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM ---
TrsFileNetSOAPXmlSimpleHttpProcessor>>#processCommand END method:
12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- TrsFileNetInterface>>#processRequest
TrsContentExecuteSearchRequest END method: 12/23/2019 5:12:59 PM
12/23/2019 5:12:59 PM --- numberOfAttempts calling exectureSearch: 1
12/23/2019 5:12:59 PM
Thanks in advance, Garet
--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to va-smalltalk...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/va-smalltalk/2d79a28a-2cc2-4bcc-a632-9024d9340e15%40googlegroups.com.
We are making a Essci40.dll call via the SciSocketmanager#getHostByAddr method.
The first call is always quick.
Then sometime afterwards ( may take 10 more calls to it, may take 100 more calls to it ), the method will hang up to 2-3 minutes.