The GM startup option will affect the number of web connections used! Is there any other way for users to queue up?

[ximen]

dbsrv17.exe "E:\\demo.db" -n 2011n -x tcpip -c 512m -gm 10 -xs http(port=80;maxrequestsize=70m;LOPT=ALL,HEADERS;LOG=D:\\WEB.LOG) -zoc clientinfo.txt -qn

Why does this parameter affect web services with limited access!（-gm） Why is the API data of other systems provided by WEP services also affected by this GM restriction? What should I use to solve this problem!

[chris_keating]

The -gm is intended to limit concurrent connections both standard and http based. Please review the MaxConnections protocol option or Reserved_Connections option if you need to limit HTTP based connections only.

[ximen]

I don't limit http. I need to limit the number of 2638 port connections. Using GM parameters will affect all of them. Can't I limit port 2638 alone?

[VolkerBarth]

I guess you can use a custom login_procedure to limit the number of regular connections.

I guess you would probably need to do some calculation over the number of current licensed connections (via rows in sa_conn_info() with number < 100000000) and properties HttpNumConnections resp. HttpsNumConnections. If the difference (aka non-web connections) is higher than desired, and the new connection is not a web connection, you would reject it. Compare the (simpler) sample in the cited doc topic.

(I have no database with web connections in use currently, so can't check that approach myself...)