Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

MI client starts failed

Hi,

After i've synchronized a new Mobile component to my local MI client, the MI client failed to start.

The trace log is as below:

[20071009 02:35:33:078] F [AppLog/MI/Core ] Cannot load conversation ids from persistence

com.sap.ip.me.core.InstallationException: Cannot overwrite ConversationId 7634C73797B5E842A68DD5AFDA82C17C / 7634C73797B5E842A68DD5AFDA82C17C (User: DEMO, MSD: Name: / ZCON6 (V. 1), Target=, Type=com.sap.ip.me.core.JspApplicationType) with 8BAE571F5F021941AA2D43E376907E43 / 8BAE571F5F021941AA2D43E376907E43 (User: DEMO, MSD: Name: / ZCON6 (V. 1), Target=, Type=com.sap.ip.me.core.JspApplicationType)

at com.sap.ip.me.core.ConversationIdHandler.addConversationIdWithoutSave(ConversationIdHandler.java:675)

at com.sap.ip.me.core.ConversationIdHandler.load(ConversationIdHandler.java:640)

at com.sap.ip.me.core.ConversationIdHandler.<init>(ConversationIdHandler.java:48)

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

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

at com.sap.ip.me.core.ConversationIdHandler.<clinit>(ConversationIdHandler.java:716)

at com.sap.ip.me.core.FrameworkInitializer.initSingletons(FrameworkInitializer.java:652)

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

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

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.ip.me.core.Startup.main(Startup.java:322)

[20071009 02:35:33:109] E [MI/Core ] Exception while instantiating com.sap.ip.me.core.ConversationIdHandler

java.lang.RuntimeException: Cannot load conversation ids from persistence

at com.sap.ip.me.core.ConversationIdHandler.load(ConversationIdHandler.java:649)

at com.sap.ip.me.core.ConversationIdHandler.<init>(ConversationIdHandler.java:48)

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

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

at com.sap.ip.me.core.ConversationIdHandler.<clinit>(ConversationIdHandler.java:716)

at com.sap.ip.me.core.FrameworkInitializer.initSingletons(FrameworkInitializer.java:652)

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

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

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.ip.me.core.Startup.main(Startup.java:322)

1. How do i solve this problem?

2. Is there any way to uninstalled the new Mobile Component which causing the error?

Any help would be highly appreciated. Thanks.

- julius

Former Member
Former Member replied

Hi Julius

You dont have to worry about this Exception it does not do any harm.Pleases refer to this java.io.WriteAbortedException: writing aborted; java.io.NotSerializableEx for the proceduere to run the replicator in merep_pd.

Thanks and Regards,

Rajan

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question