[
https://issues.apache.org/jira/browse/DAEMON-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719457#comment-17719457
]
Mark Thomas commented on DAEMON-457:
------------------------------------
I have followed the provided steps and am unable to recreate the issue on a
fully patched Windows 2019 server. I also tried running the same command
multiple times (~20) and generated a really long list of Java 9 options in the
registry without any error being reported.
It looks very much like there is something else about the environment on the
affected machines that is triggering the issue.
More detail about the issue when it happens (Does it happen for any option? Is
it related to the length of the added value? Is it related to the total length
of the new value? etc.) may help us narrow down where the problem may be.
> Tomcat9.exe crash in windows server 2016 and 2019 while updating service.
> -------------------------------------------------------------------------
>
> Key: DAEMON-457
> URL: https://issues.apache.org/jira/browse/DAEMON-457
> Project: Commons Daemon
> Issue Type: Bug
> Affects Versions: 1.3.3
> Environment: Windows Server 2016 and 2019
> Reporter: Denish Kothadiya
> Priority: Critical
> Attachments: logs.zip
>
>
> Tomcat9.exe crash in windows server 2016 and 2019 while updating service. We
> have observer issue from Tomcat 9 version 9.0.70 and above. It was working
> fine with Tomcat version 9.0.69.
> Environment details:
> OS: Windows server 2016 and 2019
> Disk space: More than 80 GB
> RAM: 8GB and more
> VC Redist x64: 14.29.30139.0
> Tomcat service details:
> JvmMs=512
> JvmMx=3076
> After creating tomcat service, We run below command to update service with
> JavaOption9
> {code}
> Tomcat9 //US//Tomcat9 ++JvmOptions9
> --add-opens=java.base/java.lang.reflect=ALL-UNNAMED#--add-opens=java.base/jdk.internal.reflect=ALL-UNNAMED#--add-opens=java.base/java.lang.annotation=ALL-UNNAMED#--add-opens=java.base/java.util.Date=ALL-UNNAMED#--add-opens=java.base/java.io=ALL-UNNAMED#--add-opens=java.base/java.util=ALL-UNNAMED#--add-opens=java.base/java.util.concurrent=ALL-UNNAMED#--add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED#--add-opens=java.base/java.math=ALL-UNNAMED#--add-opens=java.base/java.text=ALL-UNNAMED#--add-opens=java.base/javax.net.ssl=ALL-UNNAMED#--add-opens=java.base/java.time=ALL-UNNAMED
> {code}
> Above command fails with below crash in EventViewer:
> Faulting application name: tomcat9.exe, version: 1.3.3.0, time stamp:
> 0x637e7ca5
> Faulting module name: ntdll.dll, version: 10.0.17763.2237, time stamp:
> 0x65420ea4
> Exception code: 0xc0000374
> Fault offset: 0x00000000000fa979
> Faulting process id: 0x298
> Faulting application start time: 0x01d967f65ac00dce
> Faulting application path: C:\Program Files\DELL\WMS\Tomcat-9\bin\tomcat9.exe
> Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
> Report Id: 28b620b5-f3a0-40c3-99ae-962cab71bab8
> Faulting package full name:
> Please let me know if you need any more details.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
