hello,
There is a problem with the table "wwsession" when we have two instance of the same server.
The second server does not read the data modified by the First Prev.

We are file based messaging on a single server.

The problem exists on the production server (Windows Server 2008 R2 WWEB) and the development station (Seven).

Thanks in advance for your advice

Michel

Michel

Hi Michel,

Make sure you set up your paths so that the files are either shared or not. If you have two applications sharing the same session make sure you add SET PATH from the second app to the first app's base path (at the end of the path chain), then make sure that the local folder does not contain a wwSession file. That way the second app will find the first apps wwSession file.

However, I think this is a really bad idea. The whole point of separate applications is that they are separate. If you need to share functionality/behavior it's usually better to just add another process class to an existing application.

+++ Rick ---

Hello Rick,
Thank you for your reply.
The configuration of the paths is correct.
Our application is used for schools, some processing time take 2 to 3 seconds and we have many queries at certain times of the day.
As stated in your documentation we run 2 or 3 instances.
We are in file operation mode.
We do not plan run under com operation

Everything works fine except reading session variables.
It takes some time for data to be updated from one instance to another.

In development mode, the browse tells me that the data is outdated. it is enough that I am moving in to browse the data is updated.

Thanks in advance for your advice

Michel

Hi Michel,

The wwSession table just runs under VFP sharing mechanisms, wConnect has nothing to do with this.

The issue is probably network-related (SMB2 ?)

-- thn (FoxInCloud)

Hi Thierry,

Thanks for your reply

I think like you or a problem with the cache disk or Fox.

I have the same problem on W7 development machines.

There make it a tip for dealing with the problem?

Michel

Hello

I resolved my problem.

The session object is saved if it destroys or with the Save method.

In our case we do not destroy the session object after our process or make a save.

Thanks for your help.

Michel