B4 - Server failed to flush BER data back to client

Question

Hi folks,
I'm running Java Directory Server version 7.0 64bit on Redhat Linux 5.4.
I'm noticing these errors in my logs when an application using Windows 7 attempts an SSL ldap query:
[16/Jun/2011:07:40:00 -0400] conn=1212 op=-1 msgId=-1 - fd=37 slot=37 LDAPS connection from 10.224.47.130:63199 to 10.251.0.246
[16/Jun/2011:07:40:24 -0400] conn=1212 op=0 msgId=-1 - closing from 10.224.47.130:63199 - B4 - Server failed to flush BER data back to client -
[16/Jun/2011:07:40:24 -0400] conn=1212 op=-1 msgId=-1 - closed.
The Windows 7 application is unable to get the expected ldap response and fails the operation, preventing the application from running correctly. Any ideas as to what this error is and what I might be able to do to address it?
Thanks

Answer 1

Makes sense.
Here's what I discovered today - and this only occurs with applications installed on Windows 7. The same app installed on Windows XP does not have this issue. The application is configured to connect to a DNS FQDN of (sisd-mahp.xxx.xxx). That FQDN translates to an IP that is configured on a Cisco load balancer device. There are two ldap servers behind it that are round-robin'd (sisd-mahp1.xxx.xxx and sisd-mahp2.xxx.xxx). In the SSL certificate of each of those two servers I have defined X509v3 Subject Alternative Names including the load balancer IP and the individual Linux hostnames. When the Windows 7 client uses the FQDN of the load balancer virtual IP it fails, when it uses one of the sisd-mahp1 or sisd-mahp2 it works.
That leads me to believe that there is some inherent problem with the Windows 7 client libs and the load balancer or the Subject Alternative Names. When the client attempted the SSL BIND it got an unexpected result from the server SSL certificate and aborted the connection, which resulted in the failed flush BER data messages on the server.
Thanks for the response!