Forums

Hi Guys,

I've come across a small problem as usual

When we have a certain amount of users using the Thin Client, it tends to quick a person off. So for example, imagine that User A and User B log on to the Thin Client to do something, if and when User C logs on, it will kick one of the users off the system. Both, my collegue and I have checked the amount of licenses and maximum users and they are both more than sufficient. Furthermore, I don't believe we have had an issue from any clients, it could be just internal. Any ideas?

Regards,

Omash

None off hand - Just the usual.

When it happens grab the thin/fat client log and the database server jommsg log at the time and look through it find
any odd messaging at the time the client app dropped.
We have had issues with node drops in Jade 7.0.51

What jade verison are you running?

What happens when they get kicked off - is there a message?

Maybe some code you inherited only allows each user a single signon, and a second signon kicks off the first one?

Hi Guys,

@suzuki1100: We're running on JADE 6.3.12 (we only just upgraded from 6.2 a couple of weeks ago and we had the problem on there as well but not as frequently).

@ghosttie: According to my collegues, it does notify them that the session is about to close and there is an option of Yes or No but either way, it shouldn't be appearing with this dialog box; there should be enough licenses/users/space to run them all. One of the collegues also said that when he went back on, it stated whether he wants to start the session again, which would involve clearing what another user has done or is doing.

@JohnP: Looking at the logs, it shows that the node (as suzuki1100 mentioned) is being dropped but I can't see why.

I hope this helps. Thanks for the quick response guys.

Omash

@ghosttie: According to my collegues, it does notify them that the session is about to close and there is an option of Yes or No but either way, it shouldn't be appearing with this dialog box; there should be enough licenses/users/space to run them all. One of the collegues also said that when he went back on, it stated whether he wants to start the session again, which would involve clearing what another user has done or is doing.

Can you post a screenshot of the message?

Hi Guys,

Looking at the jommsg log, it states that the 'Thin Client forced off by monitor request...' followed by the user it has kicked off. Furthermore, I noticed this in the same log file: 'JADESQL: [Microsoft][ODBC SQL Server Driver]String data, right truncation'. Does this mean anything or is this just referring to the MS SQL that JADE Uses?

I have attached an image of what messages appear. In addition to this, it doesn't matter if 'Yes' or 'No' is clicked; a collegue is still kicked off.

Thanks,

Omash

That looks like user code rather than something built into JADE - I'd say you have code somewhere enforcing a concurrent user limit.

Could you put debugging in the finalise method of the application in an effort to see why the process is ending?

Did you search all schemas for "Connection limit exceeded"?