Forums: Troubleshooting and Problems
Hello Jeroen,
Thank you for including a snippet of the logging. Could you please attach the full log file for further review? You can also email us at community@pinnacle21.com.
Kind regards,
Matt
Hello Jeroen,
During discussions with our internal team, we were able to reproduce the behavior with running on Windows 11 and are evaluating it. I will follow up with more information when able.
Hi,
I was wondering if a solution for this has been determined?
Hi, just wanted to check in again and see if there's an update on this one? Thanks.
Is there any news with the Windows 11 compatibility? Thank you.
Hello,
We expect this issue with Windows 11 compatibility to be resolved in our upcoming Community release which does not have a release date yet.
Kind regards,
Matt
We are getting the following error on windows 11 machine, the exact same config works fine on Windows 10:
at net.pinnacle21.oce.utils.ProcessUtils.startFromCommandLine(ProcessUtils.java:137) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.Main.main(Main.java:16) ~[p21-client-1.0.6.jar:1.0.6]
10/27/2022 13:20:03 WorkFlowController: Caused by: java.lang.IllegalStateException: Unmapped relationship: 7
at com.sun.jna.platform.win32.WinNT$SYSTEM_LOGICAL_PROCESSOR_INFORMATION_EX.fromPointer(WinNT.java:2999) ~[p21-client-1.0.6.jar:1.0.6]
at com.sun.jna.platform.win32.Kernel32Util.getLogicalProcessorInformationEx(Kernel32Util.java:715) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.driver.windows.LogicalProcessorInformation.getLogicalProcessorInformationEx(LogicalProcessorInformation.java:61) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.hardware.platform.windows.WindowsCentralProcessor.initProcessorCounts(WindowsCentralProcessor.java:158) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.hardware.common.AbstractCentralProcessor.<init>(AbstractCentralProcessor.java:73) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.hardware.platform.windows.WindowsCentralProcessor.<init>(WindowsCentralProcessor.java:69) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.hardware.platform.windows.WindowsHardwareAbstractionLayer.createProcessor(WindowsHardwareAbstractionLayer.java:60) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.util.Memoizer$1.get(Memoizer.java:87) ~[p21-client-1.0.6.jar:1.0.6]
at oshi.hardware.common.AbstractHardwareAbstractionLayer.getProcessor(AbstractHardwareAbstractionLayer.java:68) ~[p21-client-1.0.6.jar:1.0.6]
at net.bootstrap.core.utils.OSUtils.getProcessorCount(OSUtils.java:107) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.model.input.CommandLine.getNumberOfThreads(CommandLine.java:535) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.model.input.ParseResults.getConfig(ParseResults.java:108) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.model.input.ParseResults.parseArgs(ParseResults.java:62) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.utils.InputUtils.from(InputUtils.java:51) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.utils.ProcessUtils.start(ProcessUtils.java:161) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.utils.ProcessUtils.startFromCommandLine(ProcessUtils.java:149) ~[p21-client-1.0.6.jar:1.0.6]
at net.pinnacle21.oce.utils.ProcessUtils.startFromCommandLine(ProcessUtils.java:118) ~[p21-client-1.0.6.jar:1.0.6]
... 1 common frames omitted
If we search the errors it seems there is a bug in oshi that causes this, is there any workaround available?