cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

IDOC error

Go to solution
Former Member

on ‎10-26-2009 12:45 PM

0 Kudos

Hi,

When i send IDOC from ECC system to MII there is no problem ECC side, i says message sent successfully.

Bu in MII side there is no IDOC in message monitor.

When i chek system logs and traces with http://host:port/nwa address, it is seen error message ocurred when to receive coming IDOC.

How can it be corrected?

Thanks.

Error message in MII logs and traces

java.util.zip.ZipException: error in opening zip file

at java.util.zip.ZipFile.open(Native Method)

at java.util.zip.ZipFile.<init>(ZipFile.java:111)

at java.util.zip.ZipFile.<init>(ZipFile.java:127)

at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchiveInfo(AbstractLog.java:328)

at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:454)

at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:477)

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

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

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

at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)

at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)

at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)

at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)

at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)

at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)

at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfo(LogControllerFacade.java:227)

at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfosWithPattern(LogControllerFacade.java:193)

at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfos(LogControllerFacade.java:174)

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

at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)

at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)

at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)

at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)

at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)

at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)

at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)

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

at com.sap.tc.logviewer.mbean.LocalLVMBeanServer.invoke(LocalLVMBeanServer.java:73)

at $Proxy139.getAttribute(Unknown Source)

at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getAttribute(AbstractLogDepot.java:236)

at com.sapmarkets.bam.application.logdepot.AbstractLogDepot.getLogDescriptors(AbstractLogDepot.java:84)

at com.sap.tc.logviewer.mbean.ServerModelLogDepot.getLogDescriptors(ServerModelLogDepot.java:79)

at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup$GetLogDescriptorsTask.run(ServerModelLogDepotGroup.java:60)

at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.execute(ServerModelLogDepotGroup.java:173)

at com.sap.tc.logviewer.mbean.ServerModelLogDepotGroup.getLogDescriptors(ServerModelLogDepotGroup.java:119)

at com.sap.tc.logviewer.mbean.LogviewerServer.getLogs(LogviewerServer.java:137)

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

at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)

at javax.management.StandardMBean.invoke(StandardMBean.java:286)

at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)

at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)

at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)

at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)

at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)

at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)

at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)

at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:776)

at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)

at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerInvoker.invoke(J2EELogviewerServerInvoker.java:111)

at com.sap.tc.logviewer.client.j2ee.J2EELogviewerServerProxy.getLogs(J2EELogviewerServerProxy.java:105)

at com.sap.tc.logviewer.client.base.LogviewerClientImpl$GetLogs.run(LogviewerClientImpl.java:442)

at java.lang.Thread.run(Thread.java:534)

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

agentry_src
Active Contributor
‎10-26-2009 1:48 PM
0 Kudos

cml_bzl,

Did you follow the documents on the IDOC Listener installation on the Wiki?

What version of ECC/ERP are you using?

What version of SAP-MII are you using?

What type of IDOCs are you downloading?

Regards,

Mike

Show replies
Show replies
Former Member
‎10-26-2009 2:14 PM
0 Kudos

Michael,

I followed you document How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener

We are using ECC 6.0

We are using MII 12.05

We are downloading custom IDOC.

http://host:port/nwa also give errore below

Thanks

Error

javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.

Error

application [XMII] Processing HTTP request to servlet [CMSAdmin] finished with error.

The error is: com.sap.engine.services.servlets_jsp.server.exceptions.WebIllegalStateException: The output is committed.

Exception id: [001CC458C1FE00770000001300001AFC000476D62FD7B5E8]

Former Member
‎10-26-2009 3:04 PM
0 Kudos

Michael,

IDOC type is ORDRSP /NFM/ORDERS05

Thanks

agentry_src
Active Contributor
‎10-26-2009 4:57 PM
0 Kudos

Have you been successful downloading standard IDoc formats (LOIPRO, MATMAS, etc.)?

Former Member
‎10-26-2009 8:27 PM
0 Kudos

Hi Michael,

There is no problem sending of ORDRSP idoc to another ECC system. Problem is MII can not receiving that idoc.

Last error messages that i send may point the root cause of the problem.

Is it NW needs patching? Or is there a sap note with it?

Thanks

Former Member
‎10-27-2009 11:10 AM
0 Kudos

I sent LOIPRO form ECC system to MII

Same problem occured.

When i attempt to see incoming IDOC messages using Message Monitor in MII side, it gets message Unknown error occurred; no message was provided

When i check http://host:port/nwa --> Monitoring --> logs and traces

There are errors same as below

Error

javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sap.engine.services.servlets_jsp.server.exceptions.WebIOException: An attempt to write after the stream had been closed.

agentry_src
Active Contributor
‎10-27-2009 3:06 PM
0 Kudos

Is there anything unusual in your network (SAP Router, etc.)?

Former Member
‎10-28-2009 8:34 AM
0 Kudos

Whole servers (ECC, MII ..etc) at same location and directly connect same network.

We did patghing NW of MII, but nothing changed.

When press Message Monitoring there is message below

Unknown error occurred; no message was provided

At http://host:port/nwa it writes Error in reading message list

Thanks.

Former Member
‎10-28-2009 9:38 AM
0 Kudos

Hi,

when I get this right, you are not able to start the MII Message Monitor because of the error message.

This reminds me of similar problems I have when there is a conflict between the language that MII uses in the MII portal and the language settings of the browser. For example, I encounter this problem if I set my user language to German to see a German MII Portal, but have my browser set to english. With this combination, I cannot open the Message Monitor, it only displays the error message you described.

Please check if you also have different language settings. If so, try to synchronize them and see if this helps.

Michael

Answers (0)

Ask a Question