FMS19.3 Plugin stopped loading

[JerrySalem]

I have the 360email plugin installed on our Server (FMS19.3.2) and it has been working fine for months. (Previous versions working for years!)

Starting Saturday just before 1AM the plugin Failed to load on the server. AFAIK we are up to date with licensing and nothing has changed on the server (OS updates FMS Updates) this week.

Here is part of the log file.

Any ideas?

TIA

Jerry

Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailReadMessages
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailAttachFile
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step IsValidEmail
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailRegister
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailReadMessageValue
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step IsValidEmail
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailMoveCurrentMessage
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailDisconnect
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailBCCRecipients
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailLastError
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailInboundIsConnected
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailMoveCurrentMessage
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailCreate
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailVersion
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailRecipients
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Unregistering plug-in script step EmailSend
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Starting shutdown of JVM child process
Nov 05, 2021 4:11:40 PM com.prosc.fmkit.PipeChild run
INFO: Shutting down session 2 on thread Message dispatch thread for parent thread: 6900
Nov 05, 2021 4:11:40 PM com.prosc.fmkit.PluginBridge2 onSessionEnd
INFO: No plugin instance existed for sessionId 2
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PipeChild run
INFO: Shutting down plug-in 3MLR on thread Message dispatch thread for parent thread: 5836
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PipeChild run
INFO: Shutting down plug-in 3MLR on thread Message dispatch thread for parent thread: 5836
ID: 14 / state: RUNNABLE / name: PluginBridge worker-1-thread-1
    sun.management.ThreadImpl.dumpThreads0(Native Method)
    sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:454)
    com.prosc.infrastructure.LogUtils.dumpThreadStackTrace(LogUtils.java:344)
    com.prosc.fmkit.PipeChild.lambda$doShutdown$5(PipeChild.java:213)
    com.prosc.fmkit.PipeChild$$Lambda$12/1187726406.run(Unknown Source)
    java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    java.util.concurrent.FutureTask.run(FutureTask.java:266)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)

ID: 13 / state: RUNNABLE / name: DestroyJavaVM

ID: 12 / state: WAITING / name: Message dispatch thread
    java.lang.Object.wait(Native Method)
    java.lang.Object.wait(Object.java:502)
    com.prosc.fmkit.PipeChild.run(PipeChild.java:122)
    com.prosc.fmkit.PipeChild.access$100(PipeChild.java:21)
    com.prosc.fmkit.PipeChild$2.run(PipeChild.java:98)

ID: 5 / state: RUNNABLE / name: Attach Listener

ID: 4 / state: RUNNABLE / name: Signal Dispatcher

ID: 3 / state: WAITING / name: Finalizer
    java.lang.Object.wait(Native Method)
    java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143)
    java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164)
    java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)

ID: 2 / state: WAITING / name: Reference Handler
    java.lang.Object.wait(Native Method)
    java.lang.Object.wait(Object.java:502)
    java.lang.ref.Reference.tryHandlePending(Reference.java:191)
    java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PipeChild lambda$doShutdown$5
INFO: End of PipeChild run loop
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PipeChild lambda$doShutdown$5
INFO: End of PipeChild run loop
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PluginBridge2 fmxShutdown
INFO: About to shut down allPlugins
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PluginBridge2 fmxShutdown
INFO: Pop all plugin contexts
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PluginBridge2 fmxShutdown
INFO: PluginBridge2 shutdown finished
Nov 06, 2021 12:18:48 AM com.prosc.fmkit.PipeChild sendMessage
INFO: Sending message to parent: finished, parent thread ID 5836 from thread PluginBridge worker-1-thread-1
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Finished shutdown of JVM child process in 195 ms with result of 0
Nov 06, 2021 12:18:48 AM C++ <Native>
WARNING: [C++] JVM shutdown succeeded
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Process with ID 6580 exited cleanly
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Terminating logging thread...
Nov 06, 2021 12:18:48 AM C++ <Native>
WARNING: [C++] An error occurred getting a log statement: An error occurred while reading byte from log statement: The pipe has been ended.
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Finished stderr logging
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Thread successfully terminated
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Closing pipes
Nov 06, 2021 12:18:48 AM C++ <Native>
INFO: [C++] Shutdown of 360Works Email complete in 398 ms
 

 

[ryan360Works]

Hi Jerry,

If the plugin is still not enabling, we will need to see the entire log file. Please email it to [email protected]

[JerrySalem]

Thanks Ryan.

When I checked the next day, the issue seems to resolve itself.

I didn't even touch the server.

Go figure!

 

Jerry

[ryan360Works]

Odd, if the issue comes back please let us know!