• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Session

 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

I have an application implemented using Adobe Flex. After login into the application from multiple browser, I can see each time a new session created which is a correct behavior as for our requirement.

I am using java console to check the session information.

Once I launch my application, I verify that in TaskManger i found that javaw.exe instance gets created. But when I log out from the application javaw.exe instance remains appears there in task manger and keeps eating the system resource.

My question is :

1. Does javaw.exe instance maintaining the session information at client end?
2. programaticlly how can I kill javaw.exe instance on logout?

Thanks,

Ravish
reply
    Bookmark Topic Watch Topic
  • New Topic