com.jniwrapper.win32.MessageLoopThread error


I got following error in console every second? Everything is still running nicely?
What can cause this…

Time	Logger	Message
18:15:03	com.jniwrapper.win32.MessageLoopThread	Failed to post the message to the thread. ThreadID = 2924, errorCode = 1444

com.jniwrapper.win32.LastErrorException: Invalid thread identifier.
at com.jniwrapper.win32.MessageLoopThread$LoopThread.postThreadMessage(
at com.jniwrapper.win32.MessageLoopThread.postSyncThreadMessage(
at com.jniwrapper.win32.MessageLoopThread.postSyncThreadMessage(
at com.jniwrapper.win32.MessageLoopThread$LoopThread.pingThread(
at com.jniwrapper.win32.MessageLoopThread.pingMessageLoopThread(
at com.jniwrapper.win32.MessageLoopThread.doInvokeAndWait(
at com.inductiveautomation.opccom.wrapper.OleJob.runInOLELoop(
at com.inductiveautomation.opccom.wrapper.subscriptions.COMSubscription.runRefreshState(
at com.inductiveautomation.opccom.wrapper.subscriptions.COMSubscription.setActive(
at com.inductiveautomation.opccom.wrapper.subscriptions.COMSubscription.disconnectServer(
at com.inductiveautomation.opccom.COMServerImpl.disconnectServer(
at com.inductiveautomation.opccom.COMServerImpl.shutdown(
at com.inductiveautomation.ignition.gateway.opc.OPCManagerImpl$ServerWrapper.shutdown(
at com.inductiveautomation.ignition.gateway.opc.OPCManagerImpl$OPCRecordListener.recordUpdated(
at com.inductiveautomation.ignition.gateway.opc.OPCManagerImpl$OPCRecordListener.recordUpdated(
at com.inductiveautomation.ignition.gateway.localdb.PersistenceInterfaceImpl.notifyRecordUpdated(
at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl._notifyRecordUpdated(
at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateListener.recordUpdated(
at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateMessage.notify(
at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateListener.receiveCall(
at com.inductiveautomation.ignition.gateway.cluster.QueueableMessageReceiver.receiveCall(
at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.dispatchMessage(
at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl$
at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$
at java.util.concurrent.Executors$ Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$ Source)
at Source)

I haven’t seen that before. It appears that the following happened:

  1. You edited the server, which would start a new one and shut down the old one.
  2. Something happened during shutdown for the old server.
  3. The Ignition thread is waiting for the “ole loop” (the thread used for COM operations) to finish
  4. The ole loop is erroring out while trying to detect its state.

So, everything is likely working correctly because a new Ole loop was created when starting up the new instance. Unfortunately, I think you’ll continue to get these errors until you restart the server.

This error is coming from the library we use for COM. I’m going to test the new version of the library this week, also in hopes of fixing the problems with 64-bit. However, it might be hard to tell if this is fixed, as this is the first time I’ve seen this error.


Hi Colby

I thing that there was power loss on server few days ago and after that one of my OPC servers did not startup automatically.
I started OPC server manually and it starts communicating with Ignition, but it can be that session which Ignition was started was staying offline.

If you need logs or anything else I can send those for you before restarting server.

Tommi Vahtera


I’m not sure additional logs would be helpful. I can try to see where that error was being caught and see if we can handle things differently, but unless we can figure out a sequence of events to cause it again, I’m not sure there’s much we can do.

If it does happen again soon, I can try sending you a version of the COM module with the latest com library in it.