Error while executing BSFN using Enterprise One adapter

We are currently on 6.2 E1 adapter.
Error:
com.wm.pkg.art.error.DetailedServiceException: [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service EAIE1mOrderPublish.adapterServices:callN550043C. [ADA.7180.1018] SystemException: Fatal exception thrown when executing BSFN Method. Fail to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException: Server problem. The server may still be available, but because of state information, the entire unit-of-work must be resubmitted Stack trace data … 67e21eb0155411db9c8c9c0bce6e93b9 NULL 67e21eb0155411db9c8c9c0bce6e93b9
2006-07-17 00:23:51 CDT EAIE1mOrderPublish.adapterServices:callN550043C [ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service EAIE1mOrderPublish.adapterServices:callN550043C. [ADA.7180.1018] SystemException: Fatal exception thrown when executing BSFN Method. Fail to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException: Server problem. The server may still be available, but because of state information, the entire unit-of-work must be resubmitted Stack trace data … 67e21eb0155411db9c8c9c0bce6e93b9 NULL 67e21eb0155411db9c8c9c0bce6e93b9
2006-07-17 00:23:51 CDT EAIE1mOrderPublish.adapterServices:callN550043C [ADA.7180.1018] SystemException: Fatal exception thrown when executing BSFN Method. Fail to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException: Server problem. The server may still be available, but because of state information, the entire unit-of-work must be resubmitted Stack trace data … 67e21eb0155411db9c8c9c0bce6e93b9 NULL 67e21eb0155411db9c8c9c0bce6e93b9
2006-07-17 00:23:51 CDT EAIE1mOrderPublish.adapterServices:callN550043C [ADA.7180.1018] SystemException: Fatal exception thrown when executing BSFN Method. Fail to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException: Server problem. The server may still be available, but because of state information, the entire unit-of-work must be resubmitted Stack trace data … 67e21eb0155411db9c8c9c0bce6e93b9 NULL 67e21eb0155411db9c8c9c0bce6e93b9
2006-07-17 00:23:51 CDT EAIE1mOrderPublish.adapterServices:callN550043C Fail to execute BSFNMethod com.jdedwards.system.kernel.CallObjectSystemException: Server problem. The server may still be available, but because of state information, the entire unit-of-work must be resubmitted.

Do you have any known fixes to this issue.

What I think can happen under the covers is that E1 code does some optimistic type inserts/updates where the exception is caught and dealt with so it is actually not an error. However in passing back to WM adapter via the (i think) call object kernel the “error” is detected and thrown as an error in ART.

Something to check / try is transaction handling and whether JDE is running without transactions. Try running the adapter with “no transaction” configuration and see if you get the same results.

Get an E1 developer/CNC looking at what is being called by the BSFN. You might find the problem is actually several layers down in the E1 code. Whether it’s ‘fixable’ may depend on the E1BSFN, what it’s purpose is and whether it is custom or std.

Smith,

We tried changing the transaction type in the adapter setting to “No Transaction” instead of local transacation. Now the problem mentioned got resolved.

Thx
Indrani

Indrani -
Please elaborate where you changed this transaction type setting. Is it in the adapter service in developer or in the connection definition in the EnterpriseOne Adapter admin? I don’t see it in either place.

Thanks
Roger

Roger,

We have changed the transaction type setting in EnterpriseOne adapter connection in admin page.
We are working on webmethods 6.1 version. And E1 adapter version is 6.2.

Thanks
Indrani

OK - now the bad news

As you are running without transaction control it means you can’t manage your transactions with E1. i.e. you can’t roll-back failures in try catch blocks.

E.g. you might insert order header, order details via BSFN’s. If order details fails your flow won’t roll back order header in the catch block.

Typically this is how E1 works. What they have to compensate is data integrity reports. Analyse your interfaces and make sure the appropriate data integrity reports are in place.

Also a suggestion - Use a JDBC connection rather than the E1 connection for inserting to things like interface ‘Z’ tables so at least you can transactionally control database records. Use the E1 connection for business functions.

I see what our problem is: we are using an ERP8 connection, not an “EnterpriseOne” connection (same adapter).