Linux DPS to windows DS yuck
I am having a strange connection issue between my directory proxy server and backend directory server with user data. I am upgrading my servers to newer versions and have a JES 2005Q4 DPS with linux dps 4.1 patch running on RHEL 4u3 linux going against a DS Sun-ONE-Directory/5.2 B2003.143.0014 on Windows 2000 SP4.
One of our programs runs a search against the DPS and retrieves approximately 30,000 results, and we are getting a "cant connect to ldap" error before it finsihes returning all the results. The search opens one connection and does a multiple search. The DPS closes the connection before the DS is finished. This is a non-ssl connection between the DPS and DS. I have tried some tcp and file tuning on the linux DPS but it doesnt make a difference. Maybe there is a tweak I missed.
[809 byte] By [
Xoth] at [2007-11-26 9:46:37]
# 2
Thanks Stefan. On the DS the timeout is unlimited, and for the DPS network group that handles this app there is no timeout to permit persistent connections. The DPS has no timeout settings for the backend connection to the DS. Whats odd is this works when 2 windows boxes are talking to each other, but when I put the latest version of DPS on linux then it has an issue.
Xoth at 2007-7-7 0:51:51 >
# 3
Any Directory Proxy Server gurus out there :)
There are two DPS settings which may help with this issue. For the server itself there is a connection backlog setting with a default of 128. Then the config for each backend directory server has a keep alive property with a default of 180 seconds. Would adjusting one or both of these help with the dps dropping a connection to the backend directory server before the search results were returned?
Xoth at 2007-7-7 0:51:51 >
