Integration Technologies - JDE1 (MOSC)

MOSC Banner

BSSV and Call Object Kernel recycling. How to set up so that transactions not not lost?

edited Nov 15, 2012 6:30AM in Integration Technologies - JDE1 (MOSC) 1 commentAnswered ✓
All published BSSV methods have been re-coded to use IConnection.AUTO but still getting callObject errors and losing transactions.
Kernel recycling is set to run every hour and in the past month 11 transactions were lost when the callObject error occurred.  

The COK error occurs under both solutions.  Able to resubmit the transaction and it is successful.

1) Kernel recycling >= 15 mins
2) Automatic resubmit (IConnection.AUTO) 

Here is a sample of errors from the BSSV log

01 Nov 2012 10:58:01,135 [SEVERE]  - [JDBJ]            CallObject.executeRequest(): trying appDS.inflateUnable to inflate data-struture for BSFN. | Business Function Name: GetNextUniqueKeyID, DLL: , Module Name: X00022, BSFN data structure: com.jdedwards.system.connector.dynamic.callmethod.ExecutionParameterSet@2a4a7a5, Host: PEAPI001, User: JDE, Environment: JPD910 java.io.EOFException

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center