ERROR* CallObject@32722022: COSE#1000 Request timeout: timeout after 90000ms host MYHQJDE001:6010(1360) SocID:1361 PID:5720 BSFN:F4114EndDocument user:NSS0666 Env:JNSB7334
Explaination :
COSE#1000 = timeout error at user id : NSS0666 Env:JNSB7334
Table below is to indicate what kind of error is resulted.
note: In getting above error turn on JDEDEBUG.LOG (Call Object kernel log) per process and analyze it as issue is coming from logic server not JAS machine.
Explaination :
COSE#1000 = timeout error at user id : NSS0666 Env:JNSB7334
Table below is to indicate what kind of error is resulted.
note: In getting above error turn on JDEDEBUG.LOG (Call Object kernel log) per process and analyze it as issue is coming from logic server not JAS machine.
Which errors will cause Call Object Kernel to return an error immediately (without retrying)?
LOADLIB_FAILED - When it fails to Load Parent Library which called BSFN belongs to.
GETPROCADDRESS_FAILED - Library is loaded but it is not able to find the address (compilation issue).
TM_TRAN_CANCELLED - Transaction itself is canceled most probably because Row Security is preventing
a user from updating/adding data from/into a certain table(s).
What are some examples of common error messages?
In general, the errors below will come when a certain Business Function is
called with 'Transaction Processing' ON (MANUAL Commit) and it was called
Asynchronously across E1 Distribution Module.
TIMEOUT - Unless issue is specific to transaction volume timeout error will come when a called BSFN (xxxEndDoc or its sub-routine) falls into zombie(caused by memory error) or locking(including deadlock) so analyze jdedebug.log (call object kernel log)
TM_TRAN_CANCELLED - This error will come when Transaction Processing is on and when it fails to commit cache to Table(s). Usually jde.log in logic server will contain Primary Key Constraint or Row Security Violation message. So check jdedebug.log for further detail
RETRY_NEEDED - Most of call object kernel error will call this error message. Consider this rather informational as most of case (unless error is specific to a certain data set) error may be repeated
ASSOC_KERNEL_NOT_FOUND - Common cause of this error is when a certain call object kernel falls into zombie before it reaches return(); so it failed to return to called routine(event rule)
TIMEOUT - Unless issue is specific to transaction volume timeout error will come when a called BSFN (xxxEndDoc or its sub-routine) falls into zombie(caused by memory error) or locking(including deadlock) so analyze jdedebug.log (call object kernel log)
TM_TRAN_CANCELLED - This error will come when Transaction Processing is on and when it fails to commit cache to Table(s). Usually jde.log in logic server will contain Primary Key Constraint or Row Security Violation message. So check jdedebug.log for further detail
RETRY_NEEDED - Most of call object kernel error will call this error message. Consider this rather informational as most of case (unless error is specific to a certain data set) error may be repeated
ASSOC_KERNEL_NOT_FOUND - Common cause of this error is when a certain call object kernel falls into zombie before it reaches return(); so it failed to return to called routine(event rule)
No comments:
Post a Comment