We have several MIF configuration for importing data into several tables. All work but two of them. One of them is on an Object Structure of ITEM and ALTITEM. MIF reads the imported record, but first it holds it in messaging que, with an empty error description. By retrying, it through this message (both on screen and in LOG file):

psdi.util.MXSystemException: BMXAA4177E - Java class not found. Examine the location and identify which class is not found. Ensure that the class exists in the EAR file and whether deployment is correct.

at psdi.iface.mic.EntMicService.processDataIn(EntMicService.java:1397)

at psdi.iface.mic.EntMicService.processExternalData(EntMicService.java:1287)

at psdi.iface.jms.QueueToMaximoProcessor.processMessage(QueueToMaximoProcessor.java:129)

at psdi.iface.jms.JMSContQueueProcessor.processMessage(JMSContQueueProcessor.java:227)

at psdi.iface.jms.JMSListenerBean.onMessage(JMSListenerBean.java:203)

at psdi.iface.jms.MDBProxyJMSContQueueProcessor_1_5bf7eeaa.onMessage(MDBProxyJMSContQueueProcessor_1_5bf7eeaa.java)

at com.ibm.ws.sib.api.jmsra.impl.JmsJcaEndpointInvokerImpl.invokeEndpoint(JmsJcaEndpointInvokerImpl.java:258)

at com.ibm.ws.sib.ra.inbound.impl.SibRaDispatcher.dispatch(SibRaDispatcher.java:919)

at com.ibm.ws.sib.ra.inbound.impl.SibRaSingleProcessListener$SibRaWork.run(SibRaSingleProcessListener.java:597)

at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:669)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1909)

Caused by:

java.lang.ClassNotFoundException:

at java.lang.Class.forNameImpl(Native Method)

at java.lang.Class.forName(Class.java:297)

at psdi.iface.mic.EntMicService.processDataIn(EntMicService.java:1386)

... 10 more

It is unclear to us, what exactly causes this problem, as in other 15 configurations, everything works fine. We have the same problem on SPAREPART table.

Any help/idea/advise is appreciated.

are you using a clustered instance or are all enterprise services running from single server? check the IFACETABLECONSUMER cron task. Delete the cron task instance for the ones having problem. And recreate it connected to the proper maximo instance dedicated for MIF. I had the same issue where the cron task instance was running on another server not dedicated for MIF. Deleted the instance, connected to the MIF maximo instance and created the cron task instance and it worked.