I have what I thought was a simple need: destroy a session once a user logs out of my application either via a logout button or by closing the browser.
I have implemented the body ... onunload="disconnectAll()" .. method which I found numerous examples of on the net and have my logout button call the same disconnectAll() upon click.
All this is good and my FlexSessionListener sessionDestroyed() gets called. However, I can see from my logs that a sessionCreated() also gets called straight after the call to sessionDestroyed!
Has anybody seen this or have any idea why this is happening?
Are there threads running or feeds from clients that are keeping my session alive through recreating another one?
Any help would be greatly appreciated!
Europe, Middle East and Africa