Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

CWP php stops working after10 minutes

Featured Replies

We have a two machine deployment on Windows Server 2008 R2 with IIS running FMS 12 v4 and our php apps quit after about 10 minutes. After restarting the worker system it works for 10 minutes and then again quits. The error message displayed in the log viewer after restarting for Web Publishing Core is "webuser PHP 401 565 when querying the database. This continues for about 10 minutes and then the browser displays a 500 internal server error and all 3 of the php apps stop working. Any suggestions appreciated.

 

  • Author

Just wanted to update you on our Issue. We completed a reinstall of Filemaker 12 and changed some of the settings:

 

1) Reduced Files to host from default to 40

2) Set Filemaker Clients down from 250 to 50

3) Set database cache to max 3071

4) CWP sessions are 100

 

Our environment  again is a 2 machine deployment with quad-core CPUs and 6G memory running Windows Server 2008 R2

 

Clients using filemaker can access the databases without any issues.

Web clients using CWP stop working after connected clients reach 40 ( of type fmapp(5) fmphp(35), then we get 500-internal server error.

 

How is filemaker determining number of users for fmphp clients?

 

This was not an issue before we upgrade from Filemaker 11.

 

So as far as we can tell, when connected clients of both types (fmapp&fmphp) exceed 40, clients of fmphp get an 500 internal error.

Sounds like it's not dropping the web clients after a connection - each php client should be there for less than a second (depending on the complexity of the call), and then drop the connection once it has received the requested data.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.