java.io.IOException: SysCall : bind() failed

[Former Member]

Hello -

I am the support engineer for an OEM Itronix of a rugged handheld device with PXA25x (ARM4VI) processor that is running WM 5.0. Potential customer in Ireland has sent me the following log reporting that the main problem is probably the java.io.IOException: Syscall : bind() failed. I have attached the actual log file below.

My question is: 1. how can I best debug this issue? I doubt that anything is using port 45000? Unless customer unknowing is loading something before hand that would be using this port? I ran a netstat program on the ports of my device and by default there is nothing in our handheld that uses anything remotely close to port 45000.

2. I'm not certain as to what version of Creme they are using - I suspect it must be Creme 2.7a as they claim they have run this on another WM 5.0 device and sent me logs showing that it did not have a java.io.IOException: Syscall : bind() failed exception - only our handheld failed with this exception evidently?

Note that I don't have the MI System to attempt to recreate this, nor do I have any prior experience with SAP MI (although that may change real fast). I do have DB2e and Creme and have used both in the past.

Can anyone give me some suggestions and help on how to help debug this on our device?

Thanks Neal Davis

Sorry about the long log - but maybe it will help show big picture:

[20060101 14:49:24:000] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060101 14:49:24:000] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 18 Patch 00 Build 200607272043

[20060101 14:49:24:000] I [MI/API/Logging ] ***** Current timezone: PST

[20060101 14:49:37:121] E [MI/API/Services ] MultiObjectFileStorage: Error in data read access to mapping file /MI/data/LastSuccessfulSync/datreg.obj - Generating initial mapping (root cause: /MI/data/LastSuccessfulSync/datreg.obj [java.io.FileNotFoundException])

[20060101 14:49:49:050] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060101 14:49:51:039] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060101 14:49:53:824] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060101 14:51:53:152] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.mi.systemnews.NewsImpl.create()

at com.sap.ip.mi.systemnews.StartListener.userLoggedOn()

at com.sap.ip.me.core.UserManagerImpl.fireLogon()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

at com.sap.ip.me.core.UserManagerImpl.logOnUser()

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

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

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

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

at javax.servlet.http.HttpServlet.service()

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

at javax.servlet.http.HttpServlet.service()

at org.apache.tomcat.core.ServletWrapper.doService()

at org.apache.tomcat.core.Handler.service()

at org.apache.tomcat.core.ServletWrapper.service()

at org.apache.tomcat.core.ContextManager.internalService()

at org.apache.tomcat.core.ContextManager.service()

at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection()

at org.apache.tomcat.service.TcpWorkerThread.runIt()

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

at java.lang.Thread.run()

[20060101 15:00:39:734] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.ccms.remotetracing.RemoteTracingInboundProcessor.registerItself()

at com.sap.ip.me.ccms.remotetracing.RemoteTracingListener.actionPerformed()

at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()

at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20060101 15:00:47:332] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/0.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.sync.LogSenderInboundProcessor.registerItself()

at com.sap.ip.me.sync.LogSender.sendLogToBackend()

at com.sap.ip.me.sync.LogSender.actionPerformed()

at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()

at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20060101 15:00:58:958] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.registerItself()

at com.sap.ip.me.ccms.configinfo.ConfigInfoListener.actionPerformed()

at com.sap.ip.me.sync.SyncEventRegistryImpl.fireSyncEventNotifierMethod()

at com.sap.ip.me.sync.SyncManagerImpl.raiseSyncEvent()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20060101 15:01:11:889] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCollectorInboundProcessor.registerItself()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCollector.createConfigInfoContainer()

at com.sap.ip.me.ccms.configinfo.ConfigInfoCheckerInboundProcessor.process()

at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer()

at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers()

at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle()

at com.sap.ip.me.sync.SyncManagerImpl.syncForUser()

at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend()

at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend()

at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run()

at java.lang.Thread.run()

[20060101 15:07:01:133] I [MI/API/Logging ] ***** LOG / TRACE SWITCHED ON

[20060101 15:07:01:133] I [MI/API/Logging ] ***** Mobile Engine version: MI 25 SP 18 Patch 00 Build 200607272043

[20060101 15:07:01:133] I [MI/API/Logging ] ***** Current timezone: GMT

[20060101 15:07:12:071] E [AppLog/MI/API/Services ] java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

java.io.WriteAbortedException: Writing aborted by exception; java.io.NotSerializableException: com.sap.ip.me.api.services.MEResourceBundle

at java.io.ObjectInputStream.readObject()

at java.io.ObjectInputStream.defaultReadObject()

at java.io.ObjectInputStream.inputObject()

at java.io.ObjectInputStream.readObject()

at java.io.ObjectInputStream.readObject()

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

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

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

at java.lang.Class.newInstance()

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

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

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

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

at com.sap.ip.me.core.FrameworkInitializer.initSmartSync()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

Martyn Lewis (This is different) ??????????????????????????????

[20060101 15:07:59:692] E [MI/ComServer ] Exception while running communication server:

java.io.IOException: SysCall : bind() failed

at java.net.PlainSocketImpl.bind()

at java.net.ServerSocket.<init>()

at java.net.ServerSocket.<init>()

at com.sap.ip.me.core.CommunicationServer.run()

at java.lang.Thread.run()

[20060101 15:08:04:639] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060101 15:08:07:836] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.ApplicationManager.registerInboundProcessors()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[20060101 15:08:10:780] E [AppLog/MI/API/Services ] Problems while saving /MI/sync/inboundProcessors/1.value

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

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

at java.io.ObjectOutputStream.defaultWriteObject()

at java.io.ObjectOutputStream.outputObject()

at java.io.ObjectOutputStream.writeObject()

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

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

at com.sap.ip.me.sync.InboundProcessorRegistryImpl.register()

at com.sap.ip.me.core.FrameworkInitializer.initializeFramework()

at com.sap.ip.me.core.FrameworkInitializer.main()

at com.sap.ip.me.core.Startup.main()

[Former Member]

hello neal,

by looking at the log, it seems that you have some port

binding problem with the MI communication server. By default,

MI assigns 45000 as the communication server port. This

socket server is separate from the Tomcat's service ports.

try assigning a different port number by specifying a

different port number into the mobileengine.config file.

e.g. MobileEngine.CommunicationServer.Port=50000

regards

jo

[Former Member]

Jo,

Thanks very much for your response - I will try your suggestion given below. I did run a port scan on our handheld and nothing is showing up as using port 45000?

Also I am considering just writing a separate program that attempts to open port 45000 to see what happens.

Neal Davis

[Former Member]

hello neal,

some of these problems might have been caused by a bug in

the SP. please refer to this thread.

jo

[Former Member]

Thanks Jo for your input - I have investedigated and still not certain of what is really going on and if this applies or not.

I did get a screen shot back from the customer and here is what it looks like (had to type out as I don't see a way to post and image to this forum):

Internet Explorer

Screen Shot

SAP

Synchronization Log

-Synchroniztion started

-Connection set up (without proxy) to: http://

headsap001s:50000/meSync/servlet/meSync?

~sysid=mob&

-Successfully connected with server.

-Processing of inbound data began.

-Synchronisation problems: Transport-layer (http) sync

exception raised (root cause: Exception while

synchronizing (java.net.SocketException: Remote

Connection Closed: Remote connection closed))

One suspicious thing I noticed about the screen shot above is Syncronization or Syncronizing is always spelled with a "z" except in one case above is spelled with an "s" - the UK spelling method? I check the screen shot several times and this is not a typo on my part it is how it is in the actual screen shot - almost if someone changed the log file being reported to the screen?

Can someone comment on the error, has this been seen by anyone else and was there a solution?

Also how difficult is it to hook up the entire solution so that I can recreate at my desk? I have DB2e and Java Creme (3.28). I need SAP MI I guess and probably need to set up sometime of server so I can replicate the whole process of installation and synchronization. What is the minimum I can do to replicate this and can I get a SAP MI system as a demo to put this whole puzzle together?

Thanks so much for any input anyone can provide on above.

Neal Davis