cancel
Showing results for 
Search instead for 
Did you mean: 

Commit fault: ASJ.ejb.005043

Former Member
0 Kudos

Hi All,

The scenario is IDOC -> PI -> File. (I will change it later to IDOC -> PI -> JDBC)

I initially followed William Li's blog found here:

http://scn.sap.com/people/william.li/blog/2011/05/04/configuring-pi-730-java-idoc-adapter

I get the following error in SM58 when I try and move an IDOC from SAP to SAP PO (we are running SAP PO 7.31).  I had a look at all the notes suggested in other related discussions but could not find any notes for 7.31.

In the net weaver log viewer I get the following errors:

  • Caught runtime exception while notifying MonitoringStatusListener com.sap.aii.af.service.administration.impl.MonitoringStatusListenerImpl@d0065e7 of state change: java.lang.NullPointerException: while trying to invoke the method com.sap.aii.af.service.administration.impl.container.ProcessContextImpl.getNativePayloadId() of an object loaded from local variable 'pci'
  • No Service configured for key = xxx#yyy  (where xxx is my system id and yyy is my instance number.)
  • System exception [EXCEPTION] javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@4c19f46d for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException

com.sap.conn.idoc.IDocRuntimeException

at com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(IDocReceiverBean.java:133)

at sun.reflect.GeneratedMethodAccessor1562.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:111)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:78)

at $Proxy3514.onCommit(Unknown Source)

at com.sap.mw.jco.jra.JRA$ReaderThread.commit(JRA.java:7978)

at com.sap.conn.jco.rt.DefaultServerWorker.onCommit(DefaultServerWorker.java:222)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2683)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2546)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2367)

at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)

at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)

at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)

at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:8305)

at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:245)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

javax.ejb.EJBException: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@4c19f46d for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:82)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:47)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:111)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)

at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)

at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)

at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)

at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:78)

at $Proxy3514.onCommit(Unknown Source)

at com.sap.mw.jco.jra.JRA$ReaderThread.commit(JRA.java:7978)

at com.sap.conn.jco.rt.DefaultServerWorker.onCommit(DefaultServerWorker.java:222)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2683)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2546)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2367)

at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)

at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)

at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)

at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:8305)

at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:245)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: com.sap.conn.idoc.IDocRuntimeException

at com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(IDocReceiverBean.java:133)

at sun.reflect.GeneratedMethodAccessor1562.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)

... 33 more

  • [JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_ PID, Managed_Application_Thread_24, connectionId=4-172.16.4.98|sapgw01|XI_IDOC_DEFAULT_ PID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: Commit fault: ASJ.ejb.005043 (Failed in component: sap.com/com.sap.aii.adapter.idoc.app, BC-XI-CON-IDO) Exception raised from invocation of public void com.sap.aii.af.idoc.inbound.IDocReceiverBean.onCommit(java.lang.String) method on bean instance com.sap.aii.af.idoc.inbound.IDocReceiverBean@4c19f46d for bean sap.com/com.sap.aii.adapter.idoc.app*xml|com.sap.aii.adapter.idoc.ejb.jar*xml|IDocReceiverBean in application sap.com/com.sap.aii.adapter.idoc.app.; nested exception is: com.sap.conn.idoc.IDocRuntimeException (raised by system xxxxxxxxxxxxx)

Can anyone please help me?  Ive gone through 3 different blogs on how to configure the scenario but no luck.

Accepted Solutions (1)

Accepted Solutions (1)

Bhargavakrishna
Active Contributor
0 Kudos

Hi,

--> I hope you have created ICO configuration right?

--> Have you created JCO RFC Provider destination? is not necessary also check the IS_URL parameters are properly defined or not?

--> use XPI code inspector  to trace the bug..

--> Go to communication channel monitoring see the audit log.. check if is there any error..?

Or else

--> goto SCIM - restart u r  Java instance

Refer below links

http://scn.sap.com/thread/3278142

http://scn.sap.com/message/13699610#13699610

http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-ad...

Idoc_AAE to File configuration

http://scn.sap.com/docs/DOC-31398

Hope it will helpful..

Regards

Bhargava krishna

Former Member
0 Kudos

Hi Bhargava,

Thanks for the reply!  Thanks for all the links.  Ive seen most of them and gone through them all.

I found my mistake by looking at the channel monitoring and by searching in the trouble shooting guide for the error. I had to maintain adapter-specific identifier for my business component.  What should I fill in at IDOC Adapter : Logical System?  It seems the field has a very limited length (10 characters).

I get a new error now:

Error in look for the bindingcom.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=xxxxxxxxxxxxxxxxxx;TS=;AN=LOIMSO.LOIMSO01;ANS=urn:sap-com:document:sap:idoc:messages;

I searched SDN and everyone suggested I refresh the cache, I did with no success.

Any ideas how I can sort out my new error?  I am guessing it is because I might have a mistake in the adapter specific information.


Bhargavakrishna
Active Contributor
0 Kudos

Hi,

Yes, if you do the cache refresh, it should get resolved. if not its better to do the configuration again by deleting the old one.

Did you cleared all the caches? both IR and ID.

and SLD cache.

Go to PI home page-> administration--> and clear the cache from there and see.

So that all the run time/ Delta cache will be refreshed.

Once the refresh is done, try to restart the server and see. some times server restart will resolve these types of issues.

Hope it will help...

Regards

Bhargava krishna


Former Member
0 Kudos

I am still battling with this issue.  I tried clearing the cache, restarted etc. with no luck.

So the issue must be with my config.

To recap, I took  the following steps:

  • I did the config in SAP (The IDOC is sent to PI)
  • configured InboundRA and created a default destination, connection tests all ok
  • added a business and technical system in the SLD
  • added my software component as installed software to the Business system
  • ESB config:
    • Imported software component version and added a namespace
    • Imported SAP objects (relevant IDOC) created data type for outbound, created service interfaces, message mappings and operation mapping
    • In the operation mapping I used the imported IDOC as the Source operation and Outbound Service interface as target operation
  • IB config:
    • Created folder and assigned Business System
    • Ont the receiver tab inbound interfaces is blank, on sender tab outbound interfaces is blank
    • Created communication channel of type IDoc_AAE using imported comunication component (from business system)
    • Created Business Component and Communication Channel receiver
    • Created integrated config
      • Communication component: Generated Communication Component
      • Pasted namespace and Interface as per imported IDOC in ESR (I get no suitable data found when searching for the interface and namespace)

I am guessing that the interfaces that cant be found is my problem.  I tried all the suggestions in various SDN posts with no luck.

Was there something wrong in the steps I took?


Former Member
0 Kudos

If it is successful in all connections including:

RFC destination of type T in SAP system

inboundRA is green in NWA

inboundRA property : Maxthreads count is set to non zero.

Try with start / stop IDOC channel.

If still does not work, then I would suggest to create new obj in ESR and ID as last option.

We had faced similar issue, then recreating objects solved issue.

hope this helps.

--Divyesh

Former Member
0 Kudos

Hi,

There are couple of issues here in SLD.

1. Check the Business system is created for the sender client only of your technical system in SLD.

2.In SLD Check the business system created is having the appropriate logical system name associated and the same reflects in ID of your business system.

3. For the interface name to reflect under business system your product need to be assoicated to the technical system and the relavent SWC are assigned to the business system.

Abobe steps should your issue.

Gud luck

HTH
Rajesh

Former Member
0 Kudos

Hi All,

Thanks for all the replies.

I deleted everything and recreated all the config.  It is now working! 

The only difference between my new config and old config (after comparing screenshots) I could find was that the extension field in IDOC type in WE20 was blank where it had a value before.

Thanks for all the replies!!!

former_member194612
Active Participant
0 Kudos

Hi All,

I faced the same error, the solution is check your T-code : SLDCHECK in sender r/3 system.

Hope this fails.For more info about this error,pls check SAP NOTE - 1952406

Thanks

Satish

Answers (0)