So in my SOI lab I have 4.1 SP2 running and I just tested the latest patch available to bring my system up to date:
SO03615 WIN-SOI 4.0SP2 MAY2018 MONTHLY UPDATE KIT
The only issue I'm seeing now is that my UniversalConnector Connector Version 220.127.116.110.20180517
constantly failed to initialize.
Is there a known issue for this?
In log I see this happen 2x when it tries to start and thread dumps.
2018-08-08 17:19:27,387 INFO [sendFilter CA:09997_SOI-MGR01@SOI-MGR01] util.FileUtil.compress(63) - Writing file2018-08-08 17:20:22,208 INFO [JobQueue Monitor] thread.JobQueue$MonitorThread.run(99) - 521s 4:55ms JMS Alert SOI-CNTR03_CatalystConnector2018-08-08 17:20:37,514 WARN [JMS SOI-CNTR03_CatalystConnector] common.DumpThreads.log(52) - SOI SERVER THREAD DUMPTotal number of threads: 226"[ThreadPool Manager] - Idle Thread" daemon pri=5 tid=0x79 nid=0x0 ( grp="main" cpu=156ms java.lang.Thread.State: WAITING on <0x570b24be> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor), blocked 109 times, waited 109 times at java.lang.Object.wait(Native Method) - waiting for <0x570b24be> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor) at java.lang.Object.wait(Object.java:502) at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106)
Just following up. Turns out I had to do another full SOI Mgr full stop on all services. Then start everything back up again and it finally worked. Thanks Kiet.