Changing java version can help sometimes since they regularly have issues with their process management (this is why JMX local connection is regularly broken for instance)
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le ven. 31 août 2018 à 10:06, Daniel Chiaramello < [email protected]> a écrit : > Hello Romain. > > Thanks for your answer. > > jstack <pid> returns the following line (from cmd.exe launched with > Administrator privileges): > 7848: Access is denied > The -F option can be used when the target process is not responding > > jstack -F <pid> returns the following lines: > Attaching to process ID 7848, please wait... > Error attaching to process: Windbg Error: WaitForEvent failed! > sun.jvm.hotspot.debugger.DebuggerException: Windbg Error: WaitForEvent > failed! > at > sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.attach0(Native Method) > at > > sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.attach(WindbgDebuggerLocal.java:152) > at > sun.jvm.hotspot.HotSpotAgent.attachDebugger(HotSpotAgent.java:671) > at > sun.jvm.hotspot.HotSpotAgent.setupDebuggerWin32(HotSpotAgent.java:569) > at > sun.jvm.hotspot.HotSpotAgent.setupDebugger(HotSpotAgent.java:335) > at sun.jvm.hotspot.HotSpotAgent.go(HotSpotAgent.java:304) > at sun.jvm.hotspot.HotSpotAgent.attach(HotSpotAgent.java:140) > at sun.jvm.hotspot.tools.Tool.start(Tool.java:185) > at sun.jvm.hotspot.tools.Tool.execute(Tool.java:118) > at sun.jvm.hotspot.tools.JStack.main(JStack.java:92) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at sun.tools.jstack.JStack.runJStackTool(JStack.java:140) > at sun.tools.jstack.JStack.main(JStack.java:106) > > I checked before trying to kill it, and jstack was correctly returning the > thread stacks. > > Even if I have no concrete argument, my current thought is that it may be > related to Windows... There has been an important upgrade on my PC around > the period when I started to have the problem - and we can find many posts > on Google about unkillable Windows processes (it seems to be an old > problem). Why would it impact Tomee Maven Plugin now, I don't know - and it > seems to concern "only" our office (I didn't find any message related to > that problem posted by other people, so maybe we are not using it "the > normal way", or there's something related to our network/environment). > > Anyways, thanks again for your answer. We have "solved" the problem by > installing Tomee on a VirtualBox VM, and configuring IntelliJ to deploy our > WAR on that VM, so it's less critical now in our day-to-day job - but I'll > keep monitoring that thread in case someone wants to have a look at that > problem to investigate what happens. > > Thanks again, > Daniel > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html >
