Two bugs, one feature request

Bugs:

1. Dictionary "Adds" do not save
2. No response from server in 101.79 seconds on a frequent, but not regular basis.

Feature Request:

1. It really needs to save the window layout from one run to the next.

charles,

Item 1, correct, we don't save the new words.
For item 2, go into IIS, check the properties of the default app pool, turn off the recyle check box.  When the worker process recycles, it knocks us off.  You can setup a new app pool for sighmax if you desire with the proper settings, then go into the sightmaxagentinterface and sightmaxwebservices virtual directories and change those to use your new app pool.

As for the feature request, yes, we want to start saving those, especially with some of the new features we've added into the right pane.

Thanks.

Eric

Is the dictionary editable in any way?

Not really, we do have a spanish directory, but words you add to the dictionary aren't saved at this time.

Eric

Hello Eric!

This is not a cause for the problem. I already disabled the recycling
working process and still have same problem.

Version and system info please?

SightMax 3.0

Windows 2003 R2 IIS6.0 .NET 2.0 with separate pool for SightMax3 (btw created by upgrade). Dual Xeon/2Gb RAM
Dedicated SQL 2005 SP1 for the SightMax database  Dual Xeon/4Gb RAM

Clients: WinXP Pro+SightMax Opoerator and Adin 3.0. .NET 2.0 Framework.

The disconnections happen after 100.67 seconds.

Alex, if you are running .NET 2.0 and SightMax 3, it shouldn't be timing out.  Please check your IIS settings, see if there is an issue, or something in your network which might be disallowing some type of communcations between SightMax and your operators.  If the operator doesn't get anything back from the server, it will disconnect.

 

Thanks.

 

Eric

 

What communications need to be allowed between operator client and server.
What is required to the keep session permanently between the two?

We are using Cisco content switch (CSS) in our farm for load-balancing/redundancy, but for this particular service we are not enabling the load-balance and forwarding traffic to the SightMax server.
Do you have any recommendation for such layout, any known issues re: using CSS?

I don't know anything about the Cisco content switch.  Port 80 should be the port in question.

Hi!

 The solution is quite simple!
Adding the folowing directive (where arrow points) in appropriate content solves the session disconnections problem:

 content sightmax-ssl
    vip address <ip address>
    port 443
    protocol tcp
    add service sightmax_ssl
    balance srcip
==>    flow-timeout-multiplier 0
    active


Regards,

Alex.