D
dbeavon
Guest
Another thing I've noticed about this "sessions" console in OEE is that, even though the link to it is available within the context of an ABL Application, the sessions that are listed in the screen aren't exclusive to any particular ABL Application. The same list of sessions seems to be displayed within the "sessions" screen for EVERY ABL application. So the "sessions" seem to be top-level session-manager entities. They do not seem to be associated with any particular ABL application. In the very least, this appears to be a bad user interface design. These sessions aren't attributed to a particular ABL application and they probably shouldn't be listed in a way that implies something different. Also, if the information is overly technical/internal (as it appears to be), then it should be hidden or summarized, and expanded only when absolutely necessary. Today it is presented very prominently in the very first link that is shown within an ABL application. Here is another new link to a KB about the "sessions" console. I suspect another PASOE customer was confused about the details in the "sessions" console as well: knowledgebase.progress.com/.../sessionmanager-reports-session-state-as-reserved I may need to open a support case because the list of these unexplained "sessions" continues to grow. The only way I know to reset them is to bounce the whole PASOE instance.
Continue reading...
Continue reading...