Application.SessionCount

Answered
0
0

Hi,

Today we are going to publish our second application using WiseJ and because we want to monitor system rescources andalso monitor activity we’ve added a label on the homepage to see how many connections there are currently.

This seems to not be working because each time I start a new session, the counter goes up but not down when I close the browser. Am I using this wrong or?

 

Im using 2.5.23

 

Thanks

 

Vincent

Share
  • You must to post comments
Filter
Sort by: Recently Active
Best Answer
0
0

Hi Vincent,
There is a ping between the client and the server continuously when a Wisej application is running. The moment the ping stops, the Wisej application begins the countdown to time out the session. If you want to create an “infinite” session that gets cleared when the browser is closed you can set the sessionTimeout to 60 seconds or so and handle the Application.SessionTimeout event. Set e.Handled = true. This will prevent any timeout window from appearing and clear the session after the browser has been closed for a bit.
HTH,
Levie

  • You must to post comments
0
0

Hi Vincent,

I´m glad to hear your feedback about Wisej.

We are very eager to learn more about your projects and what you achieved so far.

Please contact us at SalesATWisej.com and we can check how to follow up on a case study.

Best regards
Frank

  • You must to post comments
0
0

The application is a incident report system which allows employees to report incidents, near incidents and other related events. As these reports can be difficult to compose it was requested there’d be no timout as users might have to search and add attachments related to the notification. I figured there’d be a kindoff ping going on between the browser and the WiseJ framework.

I’ve changed the timeout to 30 minutes which seems to be working just fine, I’ve had no complaints so far 🙂

 

This is our second WiseJ project where multiple people use it on a daily basis and so far they’re happy with the results. I’m considering publishing details of the project so you can showcase them. Both look great and both showcase the potential WiseJ has!

I have two more projects in the making, perhaps I’ll supply those too. One is technically challenging so if that one works out, I’m going to real happy and surely have it submitted as a showcase too.

 

Anyway, thanks for the support as always!

 

Vincent

  • You must to post comments
0
0

Hi Vincent,

closing the browser does not immediately clear the session.
You will see Application.SessionTimeout decrease after twice the time default for SessionTimeout is reached.
SessionTimeout can be defined in your default.json.

Best regards
Frank

  • vincent_
    I’ve turned off the timeout, would that cause performance issues if those sessions are never closed? I assumed a session would end if the browser was closed regardless of session time out
  • Frank (ITG)
    No. Closing the browser does not end the session as the closing cannot be detected reliably. You can find a lot of messages concerning this topic here in the support forum. I would not recommend turning off the timeout. Best regards, Frank
  • You must to post comments
Showing 4 results
Your Answer

Please first to submit.