java.io.WriteAbortedException: writing aborted; java.io.NotSerializableEx

[Former Member]

<b>anyone can explain this

i want to modify a value and hits this problem

</b>

[20070828 10:58:27:125] E [AppLog/MI/API/Services ] java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1278)

at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845)

at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769)

at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646)

at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274)

at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324)

at com.sap.ip.me.api.services.IOUtils.readSerializedObjectFromFile(IOUtils.java:934)

at com.sap.ip.me.api.services.IOUtils.readHashtableFromDirectory(IOUtils.java:835)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.<init>(InboundProcessorRegistryImpl.java:66)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

at java.lang.reflect.Constructor.newInstance(Constructor.java:274)

at java.lang.Class.newInstance0(Class.java:308)

at java.lang.Class.newInstance(Class.java:261)

at com.sap.ip.me.api.conf.Configuration.createInstanceForType(Configuration.java:512)

at com.sap.ip.me.api.conf.Configuration.getSingletonInstanceForType(Configuration.java:457)

at com.sap.ip.me.api.sync.InboundProcessorRegistry.<clinit>(InboundProcessorRegistry.java:78)

at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.initializeSmartSyncFramework(SmartSyncRuntimeManager.java:132)

at com.sap.ip.me.core.FrameworkInitializer.initSmartSync(FrameworkInitializer.java:883)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:367)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:126)

at com.sap.ip.me.mdk.api.runtime.Start.startME(Start.java:139)

at com.sap.ip.me.mdk.api.runtime.Start.main(Start.java:46)

Caused by: java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:875)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:801)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.mi.systemnews.NewsImpl.create(NewsImpl.java:313)

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn(StartListener.java:24)

at com.sap.ip.me.core.UserManagerImpl.fireLogon(UserManagerImpl.java:2283)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:766)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:744)

at com.sap.ip.me.apps.jsp.LoginServlet.doHandleEvent(LoginServlet.java:274)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:347)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:689)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:706)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:313)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

at org.apache.tomcat.core.Handler.service(Handler.java:287)

at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)

at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806)

at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752)

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)

at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)

at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)

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

[20070828 10:58:27:968] E [AppLog/MI/API/Services ] Problems while saving C:\Program Files\SAP Mobile Infrastructure\sync\inboundProcessors\1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:875)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:801)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors(ApplicationManager.java:198)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:379)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:126)

at com.sap.ip.me.mdk.api.runtime.Start.startME(Start.java:139)

at com.sap.ip.me.mdk.api.runtime.Start.main(Start.java:46)

[20070828 10:58:28:078] E [AppLog/MI/API/Services ] Problems while saving C:\Program Files\SAP Mobile Infrastructure\sync\inboundProcessors\1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:875)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:801)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors(ApplicationManager.java:200)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:379)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:126)

at com.sap.ip.me.mdk.api.runtime.Start.startME(Start.java:139)

at com.sap.ip.me.mdk.api.runtime.Start.main(Start.java:46)

[20070828 10:58:28:140] E [AppLog/MI/API/Services ] Problems while saving C:\Program Files\SAP Mobile Infrastructure\sync\inboundProcessors\1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:875)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:801)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework(FrameworkInitializer.java:382)

at com.sap.ip.me.core.FrameworkInitializer.main(FrameworkInitializer.java:126)

at com.sap.ip.me.mdk.api.runtime.Start.startME(Start.java:139)

at com.sap.ip.me.mdk.api.runtime.Start.main(Start.java:46)

[20070828 10:58:36:781] D [MI/API/Sync ] SyncEventListener com.sap.ip.me.core.StatusUpdater@b1cc87 was registered for key com.sap.ip.me.core.StatusUpdater/MI574f4e32

[20070828 10:58:36:781] D [MI/Sync ] Register inbound processor com.sap.ip.mi.systemnews.InboundListener for method SYSTEMNEWS

[20070828 10:58:36:812] E [AppLog/MI/API/Services ] Problems while saving C:\Program Files\SAP Mobile Infrastructure\sync\inboundProcessors\1.value

java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054)

at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332)

at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304)

at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247)

at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052)

at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)

at com.sap.ip.me.api.services.IOUtils.serializeObjectToFile(IOUtils.java:875)

at com.sap.ip.me.api.services.IOUtils.saveHashtableToDirectory(IOUtils.java:801)

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register(InboundProcessorRegistryImpl.java:285)

at com.sap.ip.mi.systemnews.NewsImpl.create(NewsImpl.java:313)

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn(StartListener.java:24)

at com.sap.ip.me.core.UserManagerImpl.fireLogon(UserManagerImpl.java:2283)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:766)

at com.sap.ip.me.core.UserManagerImpl.logOnUser(UserManagerImpl.java:744)

at com.sap.ip.me.apps.jsp.LoginServlet.doHandleEvent(LoginServlet.java:274)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGetNotThreadSafe(AbstractMEHttpServlet.java:347)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doGet(AbstractMEHttpServlet.java:689)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.doPost(AbstractMEHttpServlet.java:706)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at com.sap.ip.me.api.runtime.jsp.AbstractMEHttpServlet.service(AbstractMEHttpServlet.java:313)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405)

at org.apache.tomcat.core.Handler.service(Handler.java:287)

at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)

at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:806)

at org.apache.tomcat.core.ContextManager.service(ContextManager.java:752)

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213)

at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416)

at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501)

[Former Member]

MI framework tries to serialize all inbound listeners during the registration.

However, com.sap.ip.mi.systemnews.InboundListener seems to have a member

of type com.sap.ip.me.api.services.MEResourceBundle which is not Serializable.

basically this doesn't do any harm and you can just ignore this. In the previous MI

SP level, I think we have this observer serialization exception ignored in the code;

but it seems that implementation been changed...

regards

jo

[Former Member]

Hi

The exceptions shown above is nothing to do with modification of a record. These exceptions occur most of the time during sync. You can just ignore this and this does no harm.

Best Regards

Sivakumar