cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

iDoc not received in MII

Former Member
0 Likes
554

Hi All,

I am using SAP MII 12.1.5 Build 87.

I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.

We are able to send iDoc from SAP but we are not able to receive same in MII.

Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.

Following are the log details for SAP MII Logger as well as SAP NW Log.

SAP NW Log:

Error processing JRA IDOC message

SAP MII Log:

Error processing JRA IDOC message

Error processing JRA IDOC message [server=xxx, client=xxx]

[EXCEPTION]

java.lang.NullPointerException

at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

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

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

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

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:71)

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:110)

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:21)

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:16)

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:133)

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:77)

at $Proxy943.onMessage(Unknown Source)

at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)

at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)

at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)

at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)

at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)

at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)

at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)

at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)

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

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

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

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

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

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

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

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

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

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

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

Please help me out on this issue.

Regards,

Manoj Bilthare

Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Likes

Hi Manoj,

Please check the Java applications are in running status, follow this path to check the status

Operation management->Systems->Start&Stop--->JavaEE Aapplications..

Best regards,

Sudhir Kumar

Former Member
0 Likes

Dear Sudhir,

Java Application is running for my configured resource adapter.

or i need to check any specific java application?

Regards,

Manoj Bilthare

Former Member
0 Likes

Hi Manoj,

filter the search with xapps~ and make sure the applications are in running status and as you said it was working fine with earlier build please cross check the settings on ERP once again.

Regards,

Sudhir Kumar

Former Member
0 Likes

Dear Sudhir,

I have checked all application with xapps~ are running and also SAP Configuration is proper but still we are having issue.

look up the Error log this may be help to understand issue because in NW Log we are getting iDoc message.

I am not sure but i think there is some problem in SAP NW.

Regards,

Manoj Bilthare

Former Member
0 Likes

Hi Manoj,

Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.

If this doesn't help you,please try restarting your server again.

How about the credential editor have you configured this as well?

Regards,

Sudhir Kumar

Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

Former Member
0 Likes

Dear Sudhir,

We have configured iDoc properly and RFC destination test is successful and have SAP NW SP3.

We have also restarted the MII Server but issue is still there.

Regards,

Manoj Bilthare

Former Member
0 Likes

Hi Manoj,

Its tough to make out a solution from the log file, can you also test the JCO Creating the simple transaction on the workbench and can you confirm its working.

Regards,

Sudhir Kumar

Former Member
0 Likes

Dear Sudhir,

I have tested RFC Call (SAP In Bound) and i have posted iDoc successfully in SAP.

The only problem with iDoc (SAP Out Bound) from SAP to SAP MII.

Regards,

Manoj Bilthare