NoClassDefFoundError in SXMB_MONI

[Former Member]

Hi,

In my sxmb_moni, I get failed messages with this error: [Screen Print|http://www.photostand.co.za/images/b34w01s0496jwhjjvd.jpg] but when I restart the messages they process fine. This happens everyday with allot of messages. I looked for the java.lang.NoClassDefFoundError: com.sap.mw.rfc.engine.Trc exception but nothing relates to my restart issue.

Does anyone know what causes this? Maybe a path or something needs to be updated. It might be that it cant refresh the cash?

Regards,

Jan

Here's my Stack Trace:

<Trace level="1" type="T">java.lang.NoClassDefFoundError: com.sap.mw.rfc.engine.Trc at com.sap.mw.rfc.exceptions.RfcException.<init>(RfcException.java:244) at com.sap.mw.rfc.api.RfcOptions.setProperties(RfcOptions.java:628) at com.sap.mw.jco.MiddlewareJRfc$Client.initialize(MiddlewareJRfc.java:989) at com.sap.mw.jco.JCO$Client.connect(JCO.java:3233) at com.sap.xi.tf._SpCustomerTransactionToR3CustomerTransaction_.preStart(_SpCustomerTransactionToR3CustomerTransaction_.java:401) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:409) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:142) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor242.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy210.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor241.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:62) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(AccessController.java:219) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Caused by: java.lang.ClassNotFoundException: com.sap.mw.rfc.engine.Trc Found in negative cache ------------------------- Loader Info ------------------------- ClassLoader name: [library:com.sap.mw.jco] Parent loader name: [Frame ClassLoader] References: library:tc~i18n~cp library:com.sap.util.monitor.jarm library:com.sap.tc.Logging Resources: /usr/sap/ZXP/DVEBMGS00/j2ee/cluster/server0/bin/ext/com.sap.mw.jco/jrfc.jar Loading model: {parent,local,references} --------------------------------------------------------------- at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360) ... 30 more</Trace>

[naveen_chichili]

Hi Jan,

There might be the problem with the no application threads will be free at that moment.because of this the messages get blocked in MONI and these process successfully after restarting them again.

Cheers!!!!

Naveen

[former_member4985]

Hi Jan,

Check if you have all the Java components using the same SP level;

Also check if the XI components are updated with the latest patches;

And in case they're fine, you may want to re-deploy the XI components

using the JSPM to guarantee they're correct installed.

Regards,

Caio Cagnani