Briggs Softworks

Upgrade page:

http://www.briggsoft.com/patches.htm

Changes:

Poker Mavens will now track its own thread count so you don't have to open the Windows Task Manager or Process Explorer to see that number. The main cause of site crashes is when too many threads are running. Every file port and packet port connection makes a thread until disconnected. That includes API calls, which connect to the file port. Every running table also creates a thread. You can see the current thread count on the status bar at the bottom of the server console. It updates every 10 seconds when you are online. It will also get written in the Event Log if you have "Traffic Interval" enabled in the Log Settings group. And you can fetch it with the SystemStats command in the API.

Added "Max connection whitelist" setting to Server Settings group. This will exempt the listed IP addresses from all of the Max FP/PP Connection limits. Typically you would use this so that API calls and Remote Admin access could still connect at maximum capacity.

Increased ring table "Rathole minutes" cap to 999999. Changed from 120 by request.

Added "Table closed" lines to server-side hand history files. This includes a timestamp so you can see when tables were put offline. It also adds a blank line to fix a problem where a forced shutdown could cause the next hand to merge with the last one played in the file.

Added Currency line to tournament results file. It will now show Currency=Primary or Currency=Secondary in the file.

Added error trapping for WSServer.Execute/TimerThread.Execute exceptions. The WSServer errors should be now be replaced with more detailed error messages, indicating which command was being executed when the error happened. The TimerThread errors should disappear altogether.

Fixed "raises to 0" bug caused by invalid/duplicate bet packets. Saw a few of these that were apparently caused by disconnected players that did not react in time. They should now just indicate a Fold command.

One warning about the new "Maximum connection whitelist" setting if you are using a reverse proxy service like Cloudflare and are using the "Proxy IP header" to get the player's actual IP address. All of the "Max FP/PP Connections" and "Max FP/PP Connections per IP" checks are made before any of the connection headers are read. This means those checks only know about Cloudflare's IP addresses because the player's actual IP gets passed in via a header. So the Max connection whitelist is going to be comparing against a Cloudflare IP (which is semi-random) when you make a connection through your domain name (controlled by Cloudflare) and thus your "Maximum connection whitelist" will be of no use. The workaround is to have your API calls and Remote Access connections bypass Cloudflare and connect directly to the poker server's IP address. Then the limit checks will be made against your actual IP and thus can be put in the whitelist.

Ignore all of the above if you are not using Cloudflare or are not using any of the max connection limit settings or have no plans to use the new maximum connection whitelist setting.