Ronny Ekman

The system has been running over the night. Totally 12 wrapper services with 12 running java programs. I can't see any problems yet

Hi, thanks for fast respond. Actually yesterday evening I removed a lots of nice to have parameters in our wrapper config file and then it started to work. Parameter wrapper.console.pipestreams = true was also removed. Then I added the parameters again one by one and found out that with parameter wrapper.console.pipestreams = true it doesn't work !! I don't know why we have this parameter in the config file. It has been there fore many years and I didn't set it up from the beginning. Do you want...

Pproblem with YAJSW 13.0.3 and Openjdk 17.0.3 on windows server 2016

Hi, i have checked with my colleagues and we can't find any better solution than puting the java.exe copy in the java bin catalog to make windows to find java.dll. We think this will be god enough for us if we want to use a different name to show up in windows taskmanager window. This is maybe just a windows problem . YAJSW will automatically create a copy of java.exe to "rmi-service.exe" and put it in the bin catalog if we set our parameters like in this exampel java_homex = E:/SYSAPP/Java/jdk11.0.1...

One more thing to mention is that I have no other java version installed. No old Oracle java. I have checked the registry for hidden setting ..

Added to more files. They are included in wrapper.rmi.conf. Its just lists of our jar files for the system and doesen't have any inpact on this test

Added to more files. The are included in wrapper.rmi.conf. Its just lists of our jar files for the system

Hi I have trimmed my wrapper config to minimize our config. If I remove / comment the row with wrapper.java.customProcName=test.exe the wrapper starts up without an error like Error: could not find java.dll. I am testing with latest openjdk 11.0.1. It's the same problem with 10.0.2. Providing you with 1. config file 2. Word doc with screenshots etc from windows java settings 3. Start log when customerProcName i set (start_rmi.log) 4. Start log when customerProcName is not used (start_rmi_2.log)