Forum Discussion
14 years ago
Really appreciate the comments in this post.
The solution recommended of shutting down the Single Sign-On manager worked for another java app which I am working on, that had an issue with diaglogue boxes not working and was also throwing a very similar exception to the one described.
My question is: what is the SSO doing which means this error is generated?
I would like to get to the bottom of the issue, rather than just stopping the SSO manager (the solution might still remain as shutting it down, but I would like to get further understanding so that I at least know why shutting it down makes it work)
Is there a shared resource which is not being released by the SSO manager (e.g. a port or somethng)?
Thanks
Adam
The solution recommended of shutting down the Single Sign-On manager worked for another java app which I am working on, that had an issue with diaglogue boxes not working and was also throwing a very similar exception to the one described.
My question is: what is the SSO doing which means this error is generated?
I would like to get to the bottom of the issue, rather than just stopping the SSO manager (the solution might still remain as shutting it down, but I would like to get further understanding so that I at least know why shutting it down makes it work)
Is there a shared resource which is not being released by the SSO manager (e.g. a port or somethng)?
Thanks
Adam
Related Content
- 14 years ago
- 4 years ago
- 9 years ago
Recent Discussions
- 15 days ago
- 22 days ago