Connected Users Section
The Connected Users section provides data for any users associated with the kernel process.
The following three attributes are the existing attributes of user session for both CallObject kernel and Security kernel:
Field |
Description |
|---|---|
User Name |
The name of the EnterpriseOne user who is signed on to the kernel process. |
Originating Machine |
The machine name from where the user signed in. For web client user, this will be the JAS server name. |
SignOn Time |
The time EnterpriseOne user signed on to this process. |
The connected user section has been modified to have eight new attributes only for CallObject kernel process:
Field |
Description |
|---|---|
Environment |
This reports environment of the logged in User in the CallObject kernel. This information will be useful to debug an issue which is specific to a path code or is specific to an environment. |
Last Active Time |
Last time the user performed any work on the CallObject kernel process. This will determine the staleness of user session and is a good metric when an EnterpriseOne user is logged for day probably from a third party integration system using EnterpriseOne Java connector, COM connector. |
JDE Caches |
This reports the number of JDE Caches opened by the specific user. If this number is high for this user compared to other users, then you should collect the memory diagnostics and review the JDE Caches opened by this user. The application developer should fix the business function code to free the JDECache leaks. |
JDE Cache Records** |
This is the total number of JDE Cache Records in the EnterpriseOne server process for the specific user which is created by calling the jdeCacheAdd API, for example. These cache records are generally created by EnterpriseOne Business Functions. They are necessary for Business Functions to do their work. But an increase in this value over time could indicate a leak that needs to be analyzed. The application developer should call the jdeCacheDelete (to delete cache records) or jdeCacheTerminate (to remove the entire cache) API in business function code to fix the JDE Cache Record leak. |
Total Open JDB Transactions |
This reports the total number of open JDB Transactions for the specific user. If this number is high for this user compared to other users, then you should collect the memory diagnostics and review the JDB Transactionsopened by this user. The application developer should fix the business function code to free the JDB Transaction leaks. |
Manual Open JDB Transactions |
This reports the total number of open Manual-Commit JDB Transactions for the specific user. If this number is high for this user compared to other users, then you should collect the memory diagnostics and review the JDB Transactions opened by this user. The application developer should fix the business function code to free the JDB Transaction leaks. |
Data Pointers |
This reports the number of Data Pointers used by the specific user. If this number is high for this user compared to other users, then you should collect the memory diagnostics and review the Data Pointers opened by this user. The application developer should fix the business function code to free the Data Pointer leaks. |
Tables/Views |
This reports the number of JDB Tables or JDB Views opened by the specific user. If this number is high for this user compared to other users, then you should collect the memory diagnostics and review the JDB Tables or JDB Views opened by this user. The application developer should fix the business function code to free the JDB Tables or JDB Views leaks. |
In Tools Release 9.2.6.0 and above, the CallObject kernel process will have an additional column showing which Applications package the EnterpriseOne user is using:
