D
dbeavon
Guest
After a lot of troubleshooting, I restarted the entire client machine (a windows machine) that was responsible for making up the majority of connections to the broker. This seems to have fixed the problem since I'm not seeing any more of these NullPointerExceptions in the broker logs. And on the client side I'm not getting any more of the generic connection failures ("NoAvailableSessionsException"). My theory is that a temporary port in the *client* port range (ie. an ephemeral port on the client-side in windows) was conflicting with another windows application in some way. I always thought that it was the OS'es responsibility to provide unused port numbers; but perhaps something was going wrong. By restarting the entire machine, it must have resolved all port conflicts. I had already restarted the individual client applications numerous time without any success. In case anyone ever sees that callstack in their broker log again, here is what Progress had told me about it. "The NullPointerException is about SocketInfo being NULL which is an indication of connection error." Hopefully this makes sense. The client tried to connect, was given a new client-side port number for communication but that port was immediately and forcefully closed on the client-side because of conflicts. It would be nice to have a dedicated range of ports for OpenEdge to use on the client side (just as there are on the server). But according to the KB, there is no way to set aside a port range on the client side, so as to avoid conflicts. In general it is the operating system's responsibility to protect against conflicts. See... knowledgebase.progress.com/.../P117124
Continue reading...
Continue reading...