Worked as expected.
Thank you for the quick response, Mark. Very much appreciated!
--
Sent from: http://tomcat.10.x6.nabble.com/Tomcat-User-f1968778.html
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For addit
On 24/01/2019 20:46, syst...@calpers.ca.gov wrote:
> Would it be possible to get a more end-user based description of that
> workaround for those like me that find this thread? Something along the
> lines of "Go into your Windows service and change...", or whatever the
> workaround requires.
The
Would it be possible to get a more end-user based description of that
workaround for those like me that find this thread? Something along the
lines of "Go into your Windows service and change...", or whatever the
workaround requires.
Thanks!
--
Sent from: http://tomcat.10.x6.nabble.com/Tomcat-
On 08/01/2019 15:45, Mark Thomas wrote:
> On 08/01/2019 15:25, Jean-Pascal Houde wrote:
>> Thanks all,
>
>
>> "Catalina-utility-1" prio=1 tid=15 WAITING
>> at sun.misc.Unsafe.park(Native Method)
>> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
>> at
>> java.uti
On Tue, Jan 8, 2019 at 7:45 AM Rémy Maucherat wrote:
> On Tue, Jan 8, 2019 at 4:25 PM Jean-Pascal Houde
> wrote:
>
> > "Catalina-utility-1" prio=1 tid=15 WAITING
> >
>
Is DestroyJavaVM supposed to be the only non-daemon thread at that point?
Thanks,
Igal
>
> Ok, so the new default for the u
On 08/01/2019 15:25, Jean-Pascal Houde wrote:
> Thanks all,
> "Catalina-utility-1" prio=1 tid=15 WAITING
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer$Condit
On Tue, Jan 8, 2019 at 4:25 PM Jean-Pascal Houde wrote:
> "Catalina-utility-1" prio=1 tid=15 WAITING
>
Ok, so the new default for the utility thread is non daemon so you should
have your fix there. Is nothing calling Server.destroy then ? Normally it
should (Catalina.stop does it) and the utilit
ference.java:191)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:153)
"GC Daemon" daemon prio=2 tid=13 TIMED_WAITING
at java.lang.Object.wait(Native Method)
at sun.misc.GC$Daemon.run(GC.java:117)
JP
-Original Message-
From: Igal Sapir
Sent: Tuesda
On 07/01/2019 23:38, Jean-Pascal Houde wrote:
> Hello,
>
> I'm having a problem that seems to occur only since Tomcat 9.0.14. I'm using
> Tomcat installed as a service on a Windows 2012 R2 server.
> The service starts normally, but stopping it from the Windows Services window
> takes a long tim
On Mon, Jan 7, 2019 at 8:57 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Steve,
>
> On 1/7/19 19:47, Steve Demy wrote:
> > This sounds similar to:
> >
> > http://mail-archives.apache.org/mod_mbox/tomcat-dev/201812.mbox/ajax/%
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 1/7/19 19:47, Steve Demy wrote:
> This sounds similar to:
>
> http://mail-archives.apache.org/mod_mbox/tomcat-dev/201812.mbox/ajax/%
3Cbug-63041-78%40https.bz.apache.org%2Fbugzilla%2F%3E
>
>
and,
> http://mail-archives.apache.org/mod_mbo
This sounds similar to:
http://mail-archives.apache.org/mod_mbox/tomcat-dev/201812.mbox/ajax/%3Cbug-63041-78%40https.bz.apache.org%2Fbugzilla%2F%3E
and,
http://mail-archives.apache.org/mod_mbox/tomcat-users/201812.mbox/ajax/%3CDEB74971-2714-401F-9428-25EE0ECC6D11%40shaw.ca%3E
I’m not fluent in To
Hello,
I'm having a problem that seems to occur only since Tomcat 9.0.14. I'm using
Tomcat installed as a service on a Windows 2012 R2 server.
The service starts normally, but stopping it from the Windows Services window
takes a long time (about a minute). This happens even with no web applicat
13 matches
Mail list logo
