Presumably you’re using m_apache with the MGWSI integration service.
If you look in the MGWSI configuration manager you will find a parameter that will shut down idle connections between MGWSI and Mumps after a certain period of inactivity:
DB Server Access -> Timeout for Inactive Connections (specified in seconds)
The m_apache/MGWSI combination is now deprecated in favour of mg_web:
https://github.com/chrisemunt/mg_web
I would encourage you to look at migrating to this more up to date solution for bringing M databases to the web. If configured correctly, you should not need to make any changes to your web application in rolling out this upgrade.
Chris.
--
You received this message because you are subscribed to the Google Groups "Enterprise Web Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enterprise-web-develope...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/enterprise-web-developer-community/CAMqO6n2KgNEE8_Z2Uv4R%3D%2BVWnqT_v_9Whq0x5KS2LUbRK2Amzg%40mail.gmail.com.
To help people reading this thread, and trying to help, you need to provide some more information:
A concurrency limit of around 256 sounds suspiciously close to the Apache default Max Clients setting.
Chris.
To view this discussion on the web, visit https://groups.google.com/d/msgid/enterprise-web-developer-community/526d3055-8cf9-4963-87f1-76086bbf0c34n%40googlegroups.com.