[SECURITY] CVE-2024-34750 Apache Tomcat - Denial of Service

[Mark Thomas]

CVE-2024-34750 Apache Tomcat - Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 11.0.0-M1 to 11.0.0-M20
Apache Tomcat 10.1.0-M1 to 10.1.24
Apache Tomcat 9.0.0-M1 to 9.0.89

Description:
When processing an HTTP/2 stream, Tomcat did not handle some cases of 
excessive HTTP headers correctly. This led to a miscounting of active 
HTTP/2 streams which in turn led to the use of an incorrect infinite 
timeout which allowed connections to remain open which should have been 
closed.


Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 11.0.0-M21 or later
- Upgrade to Apache Tomcat 10.1.25 or later
- Upgrade to Apache Tomcat 9.0.90 or later

Credit:
This vulnerability was reported responsibly to the Tomcat security team 
by devme4f from VNPT-VCI.


History:
2024-07-03 Original advisory

References:
[1] https://tomcat.apache.org/security-11.html
[2] https://tomcat.apache.org/security-10.html
[3] https://tomcat.apache.org/security-9.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2024-23672 Apache Tomcat - Denial of Service

[Mark Thomas]

CVE-2024-23672 Apache Tomcat - Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 11.0.0-M1 to 11.0.0-M16
Apache Tomcat 10.1.0-M1 to 10.1.18
Apache Tomcat 9.0.0-M1 to 9.0.85
Apache Tomcat 8.5.0 to 8.5.98

Description:
It was possible for a WebSocket client to keep a WebSocket connection 
open leading to increased resource consumption.


Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 11.0.0-M17 or later
- Upgrade to Apache Tomcat 10.1.19 or later
- Upgrade to Apache Tomcat 9.0.86 or later
- Upgrade to Apache Tomcat 8.5.99 or later

History:
2024-03-13 Original advisory

References:
[1] https://tomcat.apache.org/security-11.html
[2] https://tomcat.apache.org/security-10.html
[3] https://tomcat.apache.org/security-9.html
[4] https://tomcat.apache.org/security-8.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2024-24549 Apache Tomcat - Denial of Service

[Mark Thomas]

CVE-2024-24549 Apache Tomcat - Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 11.0.0-M1 to 11.0.0-M16
Apache Tomcat 10.1.0-M1 to 10.1.18
Apache Tomcat 9.0.0-M1 to 9.0.85
Apache Tomcat 8.5.0 to 8.5.98

Description:
When processing an HTTP/2 request, if the request exceeded any of the 
configured limits for headers, the associated HTTP/2 stream was not 
reset until after all of the headers had been processed.


Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 11.0.0-M17 or later
- Upgrade to Apache Tomcat 10.1.19 or later
- Upgrade to Apache Tomcat 9.0.86 or later
- Upgrade to Apache Tomcat 8.5.99 or later

Credit:
This vulnerability was reported responsibly to the Tomcat security team 
by Bartek Nowotarski (https://nowotarski.info/).


History:
2024-03-13 Original advisory

References:
[1] https://tomcat.apache.org/security-11.html
[2] https://tomcat.apache.org/security-10.html
[3] https://tomcat.apache.org/security-9.html
[4] https://tomcat.apache.org/security-8.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2023-42794 Apache Tomcat - denial of service

[Mark Thomas]

CVE-2023-42794 Apache Tomcat - denial of service

Severity: Low

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 9.0.70 to 9.0.80
Apache Tomcat 8.5.85 to 8.5.93

Description:
Tomcat's internal fork of a Commons FileUpload included an unreleased, 
in progress refactoring that exposed a potential denial of service on 
Windows if a web application opened a stream for an uploaded file but 
failed to close the stream. The file would never be deleted from disk 
creating the possibility of an eventual denial of service due to the 
disk being full.


Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 9.0.81 or later
- Upgrade to Apache Tomcat 8.5.94 or later

Credit:
This vulnerability was reported responsibly to the Tomcat security team 
by Mohammad Khedmatgozar (cellbox).


History:
2023-10-10 Original advisory

References:
[1] https://tomcat.apache.org/security-9.html
[2] https://tomcat.apache.org/security-8.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[systebo]

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 additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Mark Thomas]

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 workaround is to add utilityThreadsAsDaemon="true" to the Server
element in server.xml

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[syst...@calpers.ca.gov]

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-User-f1968778.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Mark Thomas]

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.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
>>Local Variable: 
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$Node#38
>>Local Variable: 
>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#1
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081)
>>Local Variable: java.util.concurrent.locks.ReentrantLock#1
>> at 
>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
>>Local Variable: 
>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue#1
>> at 
>> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
>>Local Variable: java.util.concurrent.ScheduledThreadPoolExecutor#1
>> at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>Local Variable: java.util.concurrent.ThreadPoolExecutor$Worker#10
>> at 
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>>Local Variable: 
>> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable#10
>> at java.lang.Thread.run(Thread.java:748)
> 
> This is the problem.
> 
> I can repeat this on a 2012 R2 test environment. I'm currently updating
> my Windows dev environment to see if I can repeat (and then debug) this
> there.
> 
> The above thread should have stopped when stop was called. It isn't
> immediately obvious why this is going wrong. A remote debugging session
> will hopefully shed some light.

Fixed for the next set of releases.

Until then, Rémy's work-around will fix it.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Igal Sapir]

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 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 utility executor will get shutdown
> then.
>
> Rémy
>

Re: Tomcat 9.0.14 Windows service slow to stop

[Mark Thomas]

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$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
>Local Variable: 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$Node#38
>Local Variable: 
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#1
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1081)
>Local Variable: java.util.concurrent.locks.ReentrantLock#1
> at 
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
>Local Variable: 
> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue#1
> at 
> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
>Local Variable: java.util.concurrent.ScheduledThreadPoolExecutor#1
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>Local Variable: java.util.concurrent.ThreadPoolExecutor$Worker#10
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>Local Variable: 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable#10
> at java.lang.Thread.run(Thread.java:748)

This is the problem.

I can repeat this on a 2012 R2 test environment. I'm currently updating
my Windows dev environment to see if I can repeat (and then debug) this
there.

The above thread should have stopped when stop was called. It isn't
immediately obvious why this is going wrong. A remote debugging session
will hopefully shed some light.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Rémy Maucherat]

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 utility executor will get shutdown
then.

Rémy

RE: Tomcat 9.0.14 Windows service slow to stop

[Jean-Pascal Houde]

: 
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue#1
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
   Local Variable: java.util.concurrent.ScheduledThreadPoolExecutor#1
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   Local Variable: java.util.concurrent.ThreadPoolExecutor$Worker#10
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
   Local Variable: 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable#10
at java.lang.Thread.run(Thread.java:748)

"FileHandlerLogFilesCleaner-1" daemon prio=5 tid=12 WAITING
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
   Local Variable: 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#6
   Local Variable: 
java.util.concurrent.locks.AbstractQueuedSynchronizer$Node#116
at 
java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
   Local Variable: java.util.concurrent.locks.ReentrantLock#128
   Local Variable: java.util.concurrent.atomic.AtomicInteger#7
   Local Variable: java.util.concurrent.LinkedBlockingQueue#1
at 
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
   Local Variable: java.util.concurrent.ThreadPoolExecutor#1
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   Local Variable: java.util.concurrent.ThreadPoolExecutor$Worker#12
at java.lang.Thread.run(Thread.java:748)

"Attach Listener" daemon prio=5 tid=5 RUNNABLE

"NioBlockingSelector.BlockPoller-1" daemon prio=5 tid=14 RUNNABLE
at sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
at 
sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
at 
sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
   Local Variable: sun.nio.ch.WindowsSelectorImpl$SubSelector#2
at sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
   Local Variable: java.util.Collections$UnmodifiableSet#4
   Local Variable: sun.nio.ch.Util$3#3
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
   Local Variable: sun.nio.ch.WindowsSelectorImpl#3
at 
org.apache.tomcat.util.net.NioBlockingSelector$BlockPoller.run(NioBlockingSelector.java:298)

"AsyncFileHandlerWriter-1020371697" daemon prio=5 tid=11 TIMED_WAITING
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
   Local Variable: 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject#4
   Local Variable: 
java.util.concurrent.locks.AbstractQueuedSynchronizer$Node#89
at 
java.util.concurrent.LinkedBlockingDeque.pollFirst(LinkedBlockingDeque.java:522)
   Local Variable: java.util.concurrent.locks.ReentrantLock#127
at 
java.util.concurrent.LinkedBlockingDeque.poll(LinkedBlockingDeque.java:684)
   Local Variable: java.util.concurrent.LinkedBlockingDeque#1
   Local Variable: java.util.concurrent.TimeUnit$3#1
at 
org.apache.juli.AsyncFileHandler$LoggerThread.run(AsyncFileHandler.java:159)

"Reference Handler" daemon prio=10 tid=2 WAITING
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at java.lang.ref.Reference.tryHandlePending(Reference.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: Tuesday, January 8, 2019 00:10
To: Tomcat Users List 
Subject: Re: Tomcat 9.0.14 Windows service slow to stop

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
> > /%
> 3Cbug-63041-78%40https.bz.apache.org%2Fbugzilla%2F%3E
> <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

Re: Tomcat 9.0.14 Windows service slow to stop

[Mark Thomas]

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 time (about a minute). This happens even with no web application 
> deployed on the server. I've tried downgrading to 9.0.13 and 9.0.12 and both 
> version stops normally, under 1-2 seconds.

I see the same thing with a clean 9.0.14 install on the same OS (fully
patched).

I'll take a look.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Igal Sapir]

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/%
> 3Cbug-63041-78%40https.bz.apache.org%2Fbugzilla%2F%3E
> <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
> <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 Tomcat, but it appears something changed in the
> > catalina.sh script of 9.0.14 that changed the stop/start
> > behaviour.
>
> Certainly nothing in catalina.sh affects Windows Services. Even
> catalina.bat is ignored for Windows Services.
>

+1


> Your issue is that Tomcat's scripts (well, actually, some 3rd-party
> scripts, actually) can't manage to stop Tomcat. Jean-Pascal's problem
> is that his shutdown is taking 60sec when he thinks it shouldn't take
> that long.
>

I've seen this happen when an application, or a 3rd-party library starts a
non-daemon thread and it is not stopped prior to the shutdown attempt.  I
think that there is a 60 second timeout because I've also noticed about
that same time frame when it happens.


>
> Jean-Pascal, what do the Tomcat logs say? There should be something
> like catalina.out or stdout.log or something like that.
>

+1

Another thing I would try is to look at a thread dump.

Igal


>
> - -chris
>
> >> On Jan 7, 2019, at 3:38 PM, 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 time (about a minute). This
> >> happens even with no web application deployed on the server. I've
> >> tried downgrading to 9.0.13 and 9.0.12 and both version stops
> >> normally, under 1-2 seconds.
> >>
> >> Here is what I am doing: 1. Download Tomcat Windows 64-bit zip 2.
> >> Install service using "service install tomcat9" 3. Open Windows
> >> "Services" control panel 3. Start Tomcat9 service -> very fast 4.
> >> Stop Tomcat9 service -> gets stuck on "stopping service..." for
> >> around a minute.
> >>
> >> This is what the commons-daemon log file shows: [2019-01-07
> >> 18:27:21] [info]  [ 7500] Commons Daemon procrun (1.1.0.0 64-bit)
> >> started [2019-01-07 18:27:21] [info]  [ 7500] Running 'tomcat9'
> >> Service... [2019-01-07 18:27:21] [info]  [ 3904] Starting
> >> service... [2019-01-07 18:27:22] [info]  [ 3904] Service started
> >> in 1190 ms. [2019-01-07 18:27:23] [info]  [ 9796] Stopping
> >> service... [2019-01-07 18:27:24] [info]  [ 9796] Service stop
> >> thread completed. [2019-01-07 18:28:24] [info]  [ 7500] Run
> >> service finished. [2019-01-07 18:28:24] [info]  [ 7500] Commons
> >> Daemon procrun finished
> >>
> >> You can see the full minute between the initial "Stopping
> >> services..." and the finish of the stopping process. Other log
> >> files don't show anything suspicious.
> >>
> >> Anyone seeing the same issue with this version?
> >>
> >> Thanks,
> >>
> >>
> >> Jean-Pascal Houde
> >>
> >>
> >> -
> >>
> >>
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> >> For additional commands, e-mail: users-h...@tomcat.apache.org
> >>
> >
> >
> > -
> >
> >
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> > For additional commands, e-mail: users-h...@tomcat.apache.org
> >
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw0LcEACgkQHPApP6U8
> pFgfsg//Yv9k+Lqnn/nH2Pd2iahEJnPRZVRUeg2bRFQGlpwRURApBzup8646UsFE
> zo9zxfJuuw2L/jea7rfZaXJaXay6nhaJ/h5+RPfq1CExNLjcK/3GjJwmZxSUqJxl
> PtNtpjsJr8lD3OXMzu9sqr26Zj3AtPbAqpJ

Re: Tomcat 9.0.14 Windows service slow to stop

[Christopher Schultz]

-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_mbox/tomcat-users/201812.mbox/ajax
/%3CDEB74971-2714-401F-9428-25EE0ECC6D11%40shaw.ca%3E
>
>  I’m not fluent in Tomcat, but it appears something changed in the
> catalina.sh script of 9.0.14 that changed the stop/start
> behaviour.

Certainly nothing in catalina.sh affects Windows Services. Even
catalina.bat is ignored for Windows Services.

Your issue is that Tomcat's scripts (well, actually, some 3rd-party
scripts, actually) can't manage to stop Tomcat. Jean-Pascal's problem
is that his shutdown is taking 60sec when he thinks it shouldn't take
that long.

Jean-Pascal, what do the Tomcat logs say? There should be something
like catalina.out or stdout.log or something like that.

- -chris

>> On Jan 7, 2019, at 3:38 PM, 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 time (about a minute). This
>> happens even with no web application deployed on the server. I've
>> tried downgrading to 9.0.13 and 9.0.12 and both version stops
>> normally, under 1-2 seconds.
>> 
>> Here is what I am doing: 1. Download Tomcat Windows 64-bit zip 2.
>> Install service using "service install tomcat9" 3. Open Windows
>> "Services" control panel 3. Start Tomcat9 service -> very fast 4.
>> Stop Tomcat9 service -> gets stuck on "stopping service..." for
>> around a minute.
>> 
>> This is what the commons-daemon log file shows: [2019-01-07
>> 18:27:21] [info]  [ 7500] Commons Daemon procrun (1.1.0.0 64-bit)
>> started [2019-01-07 18:27:21] [info]  [ 7500] Running 'tomcat9'
>> Service... [2019-01-07 18:27:21] [info]  [ 3904] Starting
>> service... [2019-01-07 18:27:22] [info]  [ 3904] Service started
>> in 1190 ms. [2019-01-07 18:27:23] [info]  [ 9796] Stopping
>> service... [2019-01-07 18:27:24] [info]  [ 9796] Service stop
>> thread completed. [2019-01-07 18:28:24] [info]  [ 7500] Run
>> service finished. [2019-01-07 18:28:24] [info]  [ 7500] Commons
>> Daemon procrun finished
>> 
>> You can see the full minute between the initial "Stopping
>> services..." and the finish of the stopping process. Other log
>> files don't show anything suspicious.
>> 
>> Anyone seeing the same issue with this version?
>> 
>> Thanks,
>> 
>> 
>> Jean-Pascal Houde
>> 
>> 
>> -
>>
>> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>> 
> 
> 
> -
>
> 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 
-BEGIN PGP SIGNATURE-
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlw0LcEACgkQHPApP6U8
pFgfsg//Yv9k+Lqnn/nH2Pd2iahEJnPRZVRUeg2bRFQGlpwRURApBzup8646UsFE
zo9zxfJuuw2L/jea7rfZaXJaXay6nhaJ/h5+RPfq1CExNLjcK/3GjJwmZxSUqJxl
PtNtpjsJr8lD3OXMzu9sqr26Zj3AtPbAqpJFr1A9LGlflpIi5ohqzVkpA3h2knEH
luxjEbsD5uaG7YlQdzal76a81RBN0glBUvdgP1dPsgXKscMdYkoIzNYL7G5TniAx
3Jsilp0oWYfDEJ0oFRmUAjN++jq4QefMZHow3QUEU8xZ8L47JQv6ZlmkSbqPndH0
/kdrUA9Cv82lN0czBz2u+KmKduot7tc+KEqS+RJD8Pkj9Jy7FOLCu9klLXk3LXFG
M22XPJdwnIDQeVnjJKxjiUhetFjOCSzH3FyL/VuxAsO4qsCqSgiW/RRrU+FdLYfs
OQPjOzGISu/9lwZ+M7yPJ1XzCoBbpVE1iHf0R5vuI0H922oXRu0dyx/IKnEpbGrv
GY6zRrte4AtLO0oMXeDxWH/iC9xgRn+B4oy8Gd3RY9l6A1vLeT41flCSjAvtSkeU
AE5N4iJp39mGJ/iUpWa7C5tzwbV1syv1weC4BzHVl5+W+YBBlv6x/HJX2Zc9dsMO
okn6tCEuKFnSCqc4N4IdocolkISqObVe35RYioYHxBStMDr5dpU=
=xtqK
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 9.0.14 Windows service slow to stop

[Steve Demy]

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 Tomcat, but it appears something changed in the catalina.sh 
script of 9.0.14 that changed the stop/start behaviour.

Steve


> On Jan 7, 2019, at 3:38 PM, 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 time (about a minute). This happens even with no web application 
> deployed on the server. I've tried downgrading to 9.0.13 and 9.0.12 and both 
> version stops normally, under 1-2 seconds.
> 
> Here is what I am doing:
> 1. Download Tomcat Windows 64-bit zip
> 2. Install service using "service install tomcat9"
> 3. Open Windows "Services" control panel
> 3. Start Tomcat9 service -> very fast
> 4. Stop Tomcat9 service -> gets stuck on "stopping service..." for around a 
> minute.
> 
> This is what the commons-daemon log file shows:
> [2019-01-07 18:27:21] [info]  [ 7500] Commons Daemon procrun (1.1.0.0 64-bit) 
> started
> [2019-01-07 18:27:21] [info]  [ 7500] Running 'tomcat9' Service...
> [2019-01-07 18:27:21] [info]  [ 3904] Starting service...
> [2019-01-07 18:27:22] [info]  [ 3904] Service started in 1190 ms.
> [2019-01-07 18:27:23] [info]  [ 9796] Stopping service...
> [2019-01-07 18:27:24] [info]  [ 9796] Service stop thread completed.
> [2019-01-07 18:28:24] [info]  [ 7500] Run service finished.
> [2019-01-07 18:28:24] [info]  [ 7500] Commons Daemon procrun finished
> 
> You can see the full minute between the initial "Stopping services..." and 
> the finish of the stopping process. Other log files don't show anything 
> suspicious.
> 
> Anyone seeing the same issue with this version? 
> 
> Thanks,
> 
> 
> Jean-Pascal Houde
> 
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 9.0.14 Windows service slow to stop

[Jean-Pascal Houde]

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 application 
deployed on the server. I've tried downgrading to 9.0.13 and 9.0.12 and both 
version stops normally, under 1-2 seconds.

Here is what I am doing:
1. Download Tomcat Windows 64-bit zip
2. Install service using "service install tomcat9"
3. Open Windows "Services" control panel
3. Start Tomcat9 service -> very fast
4. Stop Tomcat9 service -> gets stuck on "stopping service..." for around a 
minute.

This is what the commons-daemon log file shows:
[2019-01-07 18:27:21] [info]  [ 7500] Commons Daemon procrun (1.1.0.0 64-bit) 
started
[2019-01-07 18:27:21] [info]  [ 7500] Running 'tomcat9' Service...
[2019-01-07 18:27:21] [info]  [ 3904] Starting service...
[2019-01-07 18:27:22] [info]  [ 3904] Service started in 1190 ms.
[2019-01-07 18:27:23] [info]  [ 9796] Stopping service...
[2019-01-07 18:27:24] [info]  [ 9796] Service stop thread completed.
[2019-01-07 18:28:24] [info]  [ 7500] Run service finished.
[2019-01-07 18:28:24] [info]  [ 7500] Commons Daemon procrun finished

You can see the full minute between the initial "Stopping services..." and the 
finish of the stopping process. Other log files don't show anything suspicious.

Anyone seeing the same issue with this version? 

Thanks,


Jean-Pascal Houde


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2018-1336 Apache Tomcat - Denial of Service

[Jean-Frederic Clere]

CVE-2018-1336 Apache Tomcat - Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 9.0.0.M9 to 9.0.7
Apache Tomcat 8.5.0 to 8.5.30
Apache Tomcat 8.0.0.RC1 to 8.0.51
Apache Tomcat 7.0.28 to 7.0.86

Description:

An improper handing of overflow in the UTF-8 decoder with
supplementary characters can lead to an infinite loop in the
decoder causing a Denial of Service.

Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 9.0.7 or later.
- Upgrade to Apache Tomcat 8.5.32 or later.
- Upgrade to Apache Tomcat 8.0.52 or later.
- Upgrade to Apache Tomcat 7.0.90 or later.

History:
2018-07-22 Original advisory

References:
[1] http://tomcat.apache.org/security-9.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to update new JDK version in apache-tomcat-7.0.84 windows service

[Shawn Heisey]

On 4/18/2018 10:18 AM, Somu Sundar Reddy.Y wrote:
> Hi,  Recently I installed Tomcat windows service using 
> apache-tomcat-7.0.84.exe  installation file and during installation, I was 
> using JDK 1.8 Update 162 in my computer.  With this installation file , 
> windows service is automatically created and am able to start and stop the 
> service without any issues.
>  Today I installed JDK 1.8 Update 172 and modified JAVA_HOME   environment 
> variable to refer newer JDK version and uninstalled the  previous JDK version 
> ( i.e JDK 1.8 update 162).
> After previous JDK uninstallation, I am unable to start the tomcat windows 
> service using new JDK  version and I can see that   windows service is still 
> pointing to older JDK version.
> Could you pl let me know how can I update new JDK version in order to start 
> Tomcat service?

I found this:

https://serverfault.com/a/226697

Thanks,
Shawn


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: How to update new JDK version in apache-tomcat-7.0.84 windows service

[Mark Thomas]

On 18/04/18 17:18, Somu Sundar Reddy.Y wrote:
> Hi,  Recently I installed Tomcat windows service using 
> apache-tomcat-7.0.84.exe  installation file and during installation, I was 
> using JDK 1.8 Update 162 in my computer.  With this installation file , 
> windows service is automatically created and am able to start and stop the 
> service without any issues.
>  Today I installed JDK 1.8 Update 172 and modified JAVA_HOME   environment 
> variable to refer newer JDK version and uninstalled the  previous JDK version 
> ( i.e JDK 1.8 update 162).
> After previous JDK uninstallation, I am unable to start the tomcat windows 
> service using new JDK  version and I can see that   windows service is still 
> pointing to older JDK version.
> Could you pl let me know how can I update new JDK version in order to start 
> Tomcat service?

Use tomcat7w.exe to edit the service config.

(or you can edit the registry directly)

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

How to update new JDK version in apache-tomcat-7.0.84 windows service

[Somu Sundar Reddy.Y]

Hi,  Recently I installed Tomcat windows service using apache-tomcat-7.0.84.exe 
 installation file and during installation, I was using JDK 1.8 Update 162 in 
my computer.  With this installation file , windows service is automatically 
created and am able to start and stop the service without any issues.
 Today I installed JDK 1.8 Update 172 and modified JAVA_HOME   environment 
variable to refer newer JDK version and uninstalled the  previous JDK version ( 
i.e JDK 1.8 update 162).
After previous JDK uninstallation, I am unable to start the tomcat windows 
service using new JDK  version and I can see that   windows service is still 
pointing to older JDK version.
Could you pl let me know how can I update new JDK version in order to start 
Tomcat service?

-- Thanks,Somu

Re: tomcat 8 windows service logs

[Gili B]

hi

In case anyone wonders ..

I used another logging.properties in the application to overcome that.

(placed under WEB_INF/classes)


Thanks

-gili



From: Gili B <gilib...@hotmail.com>
Sent: Wednesday, May 24, 2017 3:56 PM
To: users@tomcat.apache.org
Subject: tomcat 8 windows service logs

hi

Im using tomcat 8 as a windows service.

Most of the logs are going to .stderr

I use the same logging.config as I use in linux (and it works in linux).


The files are created under logs directory, but are empty.

When I configure tomcat LogLevel to WARNING, I still see INFO messages in 
stderr file.


Please help.


Thanks

-gili

tomcat 8 windows service logs

[Gili B]

hi

Im using tomcat 8 as a windows service.

Most of the logs are going to .stderr

I use the same logging.config as I use in linux (and it works in linux).


The files are created under logs directory, but are empty.

When I configure tomcat LogLevel to WARNING, I still see INFO messages in 
stderr file.


Please help.


Thanks

-gili

[SECURITY] CVE-2017-5650 Apache Tomcat Denial of Service

[Mark Thomas]

CVE-2017-5650 Apache Tomcat Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 9.0.0.M1 to 9.0.0.M18
Apache Tomcat 8.5.0 to 8.5.12
Apache Tomcat 8.0.x and earlier are not affected

Description
The handling of an HTTP/2 GOAWAY frame for a connection did not close
streams associated with that connection that were currently waiting for
a WINDOW_UPDATE before allowing the application to write more data.
These waiting streams each consumed a thread. A malicious client could
therefore construct a series of HTTP/2 requests that would consume all
available processing threads.

Mitigation:
Users of the affected versions should apply one of the following
mitigations:
- Upgrade to Apache Tomcat 9.0.0.M19 or later
- Upgrade to Apache Tomcat 8.5.13 or later

Credit:
This issue was identified by Chun Han Hsiao and reported responsibly to
the Tomcat security team.

History:
2017-04-10 Original advisory

References:
[1] http://tomcat.apache.org/security-9.html
[2] http://tomcat.apache.org/security-8.html


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2016-6817 Apache Tomcat Denial of Service

[Mark Thomas]

CVE-2016-6817 Apache Tomcat Information Disclosure

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
Apache Tomcat 9.0.0.M1 to 9.0.0.M11
Apache Tomcat 8.5.0 to 8.5.6
Earlier versions are not affected.

Description
The HTTP/2 header parser entered an infinite loop if a header was
received that was larger than the available buffer. This made a denial
of service attack possible.

Mitigation
Users of affected versions should apply one of the following mitigations
- Upgrade to Apache Tomcat 9.0.0.M13 or later
  (Apache Tomcat 9.0.0.M12 has the fix but was not released)
- Upgrade to Apache Tomcat 8.5.8 or later
  (Apache Tomcat 8.5.7 has the fix but was not released)

Credit:
This issue was reported as a bug and the security implications
identified by the Apache Tomcat Security Team.

References:
[1] http://tomcat.apache.org/security-9.html
[2] http://tomcat.apache.org/security-8.html


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as Windows Service

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Amit,

On 9/8/16 12:49 AM, Amit Pande wrote:
> Hello experts,
> 
> We have configured the Tomcat to  run as a Windows Service. And
> Windows SCM has a default time of 30 seconds, but the Tomcat
> process does not start/stop within this time.
> 
> So, if we restart the service via SCM, we receive the Address in
> Use exceptions (as previous Tomcat process hasn't been stopped
> yet).
> 
> We're using our own custom mechanism to hook the Tomcat process
> with the Windows SCM and haven't gone the below mentioned way.
> 
> https://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html
>
>  Any pointers on how to solve this issue ?
> 
> 1. Increasing Windows SCM timeout for this process might work but 
> doesn't sound really clean solution.

It might be your only solution.

> 2. Issue a Catalina stop, and if it does not stop in some time ,
> do a task kill or something similar of the corresponding java.exe
> ?

Windows has a few[1] kill[2] commands[3]. I don't know what the
repercussions of killing your application are, though. Presumably,
your application needs to clean up after itself.

> Appreciate your help here.

What's taking Tomcat (really your application) so long to shutdown?

If there are requests taking a long time to complete, you can
configure Tomcat to cancel those requests after a particular
timeout[4]. I couldn't find a configuration setting for when using an
. Hmm...

- -chris

[1]
http://www.howtogeek.com/145882/how-to-kill-a-process-from-the-cli-in-wi
ndows/
[2] http://tweaks.com/windows/39559/kill-processes-from-command-prompt/
[3] https://technet.microsoft.com/en-us/library/bb491009.aspx
[4] https://tomcat.apache.org/tomcat-8.0-doc/config/http.html,
executorTerminationTimeoutMillis
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJX0YEEAAoJEBzwKT+lPKRYXMEP/R/pjvAIXyp8LsPhGyR1T1BZ
6HW4MSScWIvaVIwIxfCs73vL3KcIIzrEEN69PClVItLKMFOwtdUC5zW/w9emkWFb
ppDhmFn5QOetldm3E/KiXp0gYpc9e5C/QKwjOsTwXKI3rA6kWsRMa6Tldve5cn81
9TV1F83iICj36n31jkYZJ6EPo9YQDrGvb9ezFhselZEXoSeTVF8q0T4P7fQkoX+q
yqMEHyQQHR3RE6WOHkoz8NX06oSeEFdDrPISblvrqdxYEZD9AsToIR3uqalb29wo
y72nOQPjpONnEcNBy2FpzXAvSPih6YFAlr/14v2W7Bfhdt+szutLkth3+3MDA9bK
tWMXWf11tav4SUeXyb5vpaduSJ+iPXyQdW+UDakqQ2M77vuzbxVSRwXEjvswOhNh
IhY5laFLHglEb/O9FfuNjXtMh0vVlyPJLGEAbsKAQnF5bQB7MckiVWBr7+thAHnM
OCSnDoAwNqk+9hMs4CVPVWNT/kHWWzC6B7iawyoYdqjyln7zQp9YfKEUWudRzw+z
JHQfeFOJsi7xXKHXuxFoNqJKuw5tx6o+Wjy/ElJpAlrOMhGzBPoTQobU/ukSQUUW
X7rF1Sa0cg2UeOeaLe9TQ4yuCDgC02ExD2yxJ7Z2srFG88rCXyxJipwloXTWnyBq
iuAEdD29FZ7n+hiQTfNL
=ZnzF
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat as Windows Service

[Amit Pande]

Hello experts,

We have configured the Tomcat to  run as a Windows Service. And Windows SCM has 
a default time of 30 seconds, but the Tomcat process does not start/stop within 
this time.

So, if we restart the service via SCM, we receive the Address in Use exceptions 
(as previous Tomcat process hasn't been stopped yet).

We're using our own custom mechanism to hook the Tomcat process with the 
Windows SCM and haven't gone the below mentioned way.

https://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html

Any pointers on how to solve this issue ?

  1.  Increasing Windows SCM timeout for this process might work but doesn't 
sound really clean solution.
  2.  Issue a Catalina stop, and if it does not stop in some time , do a task 
kill or something similar of the corresponding java.exe ?

Appreciate your help here.

Thanks,
Amit

Re: [SECURITY][CORRECTION] CVE-2016-3092 Apache Tomcat Denial of Service

[Mark Thomas]

On 30/06/2016 09:20, Kyohei Nakamura wrote:
> Hi,
> 
> I have a question about the maxHttpHeaderSize.
> 
> In this announcement, the recommended value is 3072 bytes.
> However, in the announcement from the Apache Commons project, the
> recommended value is 2048 bytes.
> http://mail-archives.apache.org/mod_mbox/www-announce/201606.mbox/%3c45a20804-abff-4fed-a297-69ac95ab9...@apache.org%3E
> 
> If an application uses the Apache Commons FileUpload (not use the
> Tomcat File Upload feature), which one should I use? "3072" or "2048".

Use the lowest value you can that doesn't cause your application to break.

Better still, just update the version of Commons FileUpload you are
using so you don't need this work-around.

Mark


> 
> 
> 2016-06-22 19:02 GMT+09:00 Mark Thomas <ma...@apache.org>:
>> Note: This announcement corrects several errors and omissions in the
>> Tomcat aspects of the announcement for CVE-2016-3092 from the Apache
>> Commons project that was recently forwarded to various Apache Tomcat
>> mailing lists.
>>
>> For the sake of clarity, the Tomcat specific corrections are as follows:
>> 1. This is a Denial of Service vulnerability, not an Information
>> Disclosure vulnerability.
>> 2. Apache Tomcat 8.5.x is also affected. The vulnerability exists in
>> 8.5.0 to 8.5.2 and affected users of 8.5.x should upgrade to 8.5.3.
>> 3. Apache Tomcat 6.x and earlier are not affected.
>> 4. Applications that do not use the File Upload feature introduced in
>> Servlet 3.0 are not vulnerable via Tomcat.
>>
>> A corrected announcement, for Tomcat only, follows.
>>
>>
>> CVE-2016-3092: Apache Tomcat Denial of Service
>>
>> Severity: Moderate
>>
>> Vendor:
>> The Apache Software Foundation
>>
>> Versions Affected:
>> Apache Tomcat 9.0.0.M1 to 9.0.0M6
>> Apache Tomcat 8.5.0 to 8.5.2
>> Apache Tomcat 8.0.0.RC1 to 8.0.35
>> Apache Tomcat 7.0.0 to 7.0.69
>> Earlier versions are not affected.
>>
>> Description:
>> CVE-2016-3092 is a denial of service vulnerability that has been
>> corrected in the Apache Commons FileUpload component. It occurred when
>> the length of the multipart boundary was just below the size of the
>> buffer (4096 bytes) used to read the uploaded file. This caused the file
>> upload process to take several orders of magnitude longer than if the
>> boundary length was the typical tens of bytes.
>>
>> Apache Tomcat uses a package renamed copy of Apache Commons FileUpload
>> to implement the file upload requirements of the Servlet specification
>> and was therefore also vulnerable to the denial of service vulnerability.
>>
>> Applications that do not use the File Upload feature introduced in
>> Servlet 3.0 are not affected by the Tomcat aspect of this vulnerability.
>> If those applications use Apache Commons FileUpload, they may still be
>> affected.
>>
>> Mitigation:
>> Users of affected versions should apply one of the following mitigations
>> - Upgrade to Apache Tomcat 9.0.0.M8 or later
>>   (9.0.0.M7 has the fix but was not released)
>> - Upgrade to Apache Tomcat 8.5.3 or later
>> - Upgrade to Apache Tomcat 8.0.36 or later
>> - Upgrade to Apache Tomcat 7.0.70 or later
>>
>> Workaround:
>> The issue may be mitigated by limiting the length of the boundary.
>> Applications could do this with a custom Filter to reject requests that
>> use large boundaries.
>> Tomcat provides the maxHttpHeaderSize attribute on the Connector that
>> can be used to limit the total HTTP header size. Users should be aware
>> that reducing this to 3072 (which should be low enough to protect
>> against this DoS) may cause other issues as applications can require
>> larger headers than this for correct operation, particularly if the
>> application uses relatively large cookie values.
>>
>> Credit:
>> This issue was identified by the TERASOLUNA Framework Development Team
>> at the Software Engineering, Research and Development Headquarters and
>> reported to the ASF via JPCERT.
>>
>> References:
>> http://tomcat.apache.org/security-9.html
>> http://tomcat.apache.org/security-8.html
>> http://tomcat.apache.org/security-7.html
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: dev-h...@tomcat.apache.org
>>
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
> 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [SECURITY][CORRECTION] CVE-2016-3092 Apache Tomcat Denial of Service

[Kyohei Nakamura]

Hi,

I have a question about the maxHttpHeaderSize.

In this announcement, the recommended value is 3072 bytes.
However, in the announcement from the Apache Commons project, the
recommended value is 2048 bytes.
http://mail-archives.apache.org/mod_mbox/www-announce/201606.mbox/%3c45a20804-abff-4fed-a297-69ac95ab9...@apache.org%3E

If an application uses the Apache Commons FileUpload (not use the
Tomcat File Upload feature), which one should I use? "3072" or "2048".


2016-06-22 19:02 GMT+09:00 Mark Thomas <ma...@apache.org>:
> Note: This announcement corrects several errors and omissions in the
> Tomcat aspects of the announcement for CVE-2016-3092 from the Apache
> Commons project that was recently forwarded to various Apache Tomcat
> mailing lists.
>
> For the sake of clarity, the Tomcat specific corrections are as follows:
> 1. This is a Denial of Service vulnerability, not an Information
> Disclosure vulnerability.
> 2. Apache Tomcat 8.5.x is also affected. The vulnerability exists in
> 8.5.0 to 8.5.2 and affected users of 8.5.x should upgrade to 8.5.3.
> 3. Apache Tomcat 6.x and earlier are not affected.
> 4. Applications that do not use the File Upload feature introduced in
> Servlet 3.0 are not vulnerable via Tomcat.
>
> A corrected announcement, for Tomcat only, follows.
>
>
> CVE-2016-3092: Apache Tomcat Denial of Service
>
> Severity: Moderate
>
> Vendor:
> The Apache Software Foundation
>
> Versions Affected:
> Apache Tomcat 9.0.0.M1 to 9.0.0M6
> Apache Tomcat 8.5.0 to 8.5.2
> Apache Tomcat 8.0.0.RC1 to 8.0.35
> Apache Tomcat 7.0.0 to 7.0.69
> Earlier versions are not affected.
>
> Description:
> CVE-2016-3092 is a denial of service vulnerability that has been
> corrected in the Apache Commons FileUpload component. It occurred when
> the length of the multipart boundary was just below the size of the
> buffer (4096 bytes) used to read the uploaded file. This caused the file
> upload process to take several orders of magnitude longer than if the
> boundary length was the typical tens of bytes.
>
> Apache Tomcat uses a package renamed copy of Apache Commons FileUpload
> to implement the file upload requirements of the Servlet specification
> and was therefore also vulnerable to the denial of service vulnerability.
>
> Applications that do not use the File Upload feature introduced in
> Servlet 3.0 are not affected by the Tomcat aspect of this vulnerability.
> If those applications use Apache Commons FileUpload, they may still be
> affected.
>
> Mitigation:
> Users of affected versions should apply one of the following mitigations
> - Upgrade to Apache Tomcat 9.0.0.M8 or later
>   (9.0.0.M7 has the fix but was not released)
> - Upgrade to Apache Tomcat 8.5.3 or later
> - Upgrade to Apache Tomcat 8.0.36 or later
> - Upgrade to Apache Tomcat 7.0.70 or later
>
> Workaround:
> The issue may be mitigated by limiting the length of the boundary.
> Applications could do this with a custom Filter to reject requests that
> use large boundaries.
> Tomcat provides the maxHttpHeaderSize attribute on the Connector that
> can be used to limit the total HTTP header size. Users should be aware
> that reducing this to 3072 (which should be low enough to protect
> against this DoS) may cause other issues as applications can require
> larger headers than this for correct operation, particularly if the
> application uses relatively large cookie values.
>
> Credit:
> This issue was identified by the TERASOLUNA Framework Development Team
> at the Software Engineering, Research and Development Headquarters and
> reported to the ASF via JPCERT.
>
> References:
> http://tomcat.apache.org/security-9.html
> http://tomcat.apache.org/security-8.html
> http://tomcat.apache.org/security-7.html
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: dev-h...@tomcat.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY][CORRECTION] CVE-2016-3092 Apache Tomcat Denial of Service

[Mark Thomas]

Note: This announcement corrects several errors and omissions in the
Tomcat aspects of the announcement for CVE-2016-3092 from the Apache
Commons project that was recently forwarded to various Apache Tomcat
mailing lists.

For the sake of clarity, the Tomcat specific corrections are as follows:
1. This is a Denial of Service vulnerability, not an Information
Disclosure vulnerability.
2. Apache Tomcat 8.5.x is also affected. The vulnerability exists in
8.5.0 to 8.5.2 and affected users of 8.5.x should upgrade to 8.5.3.
3. Apache Tomcat 6.x and earlier are not affected.
4. Applications that do not use the File Upload feature introduced in
Servlet 3.0 are not vulnerable via Tomcat.

A corrected announcement, for Tomcat only, follows.


CVE-2016-3092: Apache Tomcat Denial of Service

Severity: Moderate

Vendor:
The Apache Software Foundation

Versions Affected:
Apache Tomcat 9.0.0.M1 to 9.0.0M6
Apache Tomcat 8.5.0 to 8.5.2
Apache Tomcat 8.0.0.RC1 to 8.0.35
Apache Tomcat 7.0.0 to 7.0.69
Earlier versions are not affected.

Description:
CVE-2016-3092 is a denial of service vulnerability that has been
corrected in the Apache Commons FileUpload component. It occurred when
the length of the multipart boundary was just below the size of the
buffer (4096 bytes) used to read the uploaded file. This caused the file
upload process to take several orders of magnitude longer than if the
boundary length was the typical tens of bytes.

Apache Tomcat uses a package renamed copy of Apache Commons FileUpload
to implement the file upload requirements of the Servlet specification
and was therefore also vulnerable to the denial of service vulnerability.

Applications that do not use the File Upload feature introduced in
Servlet 3.0 are not affected by the Tomcat aspect of this vulnerability.
If those applications use Apache Commons FileUpload, they may still be
affected.

Mitigation:
Users of affected versions should apply one of the following mitigations
- Upgrade to Apache Tomcat 9.0.0.M8 or later
  (9.0.0.M7 has the fix but was not released)
- Upgrade to Apache Tomcat 8.5.3 or later
- Upgrade to Apache Tomcat 8.0.36 or later
- Upgrade to Apache Tomcat 7.0.70 or later

Workaround:
The issue may be mitigated by limiting the length of the boundary.
Applications could do this with a custom Filter to reject requests that
use large boundaries.
Tomcat provides the maxHttpHeaderSize attribute on the Connector that
can be used to limit the total HTTP header size. Users should be aware
that reducing this to 3072 (which should be low enough to protect
against this DoS) may cause other issues as applications can require
larger headers than this for correct operation, particularly if the
application uses relatively large cookie values.

Credit:
This issue was identified by the TERASOLUNA Framework Development Team
at the Software Engineering, Research and Development Headquarters and
reported to the ASF via JPCERT.

References:
http://tomcat.apache.org/security-9.html
http://tomcat.apache.org/security-8.html
http://tomcat.apache.org/security-7.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Chris Brown]

Here is the code to shut down the pools.  When I was running a single pool the 
issue did not occur.  It's when I added the second pool that the issue started.

Arrays.asList(universalConnectionPoolManager.getConnectionPoolNames())
.forEach(poolName -> {
try {
universalConnectionPoolManager
.destroyConnectionPool(poolName);
} catch (Exception e) {
exceptionHandler.handleError(
e,
String.join(
":",
"Destroy Connection Pool Error",
poolName));
}
});

The jdbc driver and connection pool .jar files are in the tomcat lib folder and 
not in the applications lib folder.

I never tried Tomcat's version of connection pooling.

Thank you,
Chris Brown
Systems Consultant
National Council on
Compensation Insurance
901 Peninsula Corporate Circle
Boca Raton, FL 33487-1362
(P) 561-893-2324
chris_br...@ncci.com


-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, March 07, 2016 10:33 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/7/16 9:51 AM, Chris Brown wrote:
> Tomcat is shutting down the web service when I deploy a new .war file.

Okay. You said you were closing the connection pool, though:

On 3/4/16 2:13 PM, Chris Brown wrote:
> I added a ServletContextListener to our web service.  On the
> contextDestroyed method we destroy the connection pools.  Our web
> service uses 2 connection pools.

So, how, precisely, are you shutting those pools down?

> There is no documentation on the threads and what they are for in
> oracle or tomcats documentation.

Tomcat would not contain information on a Vendor's product. A quick Google 
search for "oracle ojdbc7 ucp-worker-thread" yields the following very relevant 
result:

http://stackoverflow.com/questions/9671270/oracle-ucp-driver-and-tomcat-
threads-failing-to-stop

Also, searching for the OJDBC manual has a FAQ which mentions threads and their 
lifetimes:
http://www.oracleimg.com/technetwork/articles/sql/jdbc-faq-090281.html

> The threads are not shutting down and they stay alive when the web
> service is shut down. I know this because I count the number of
> threads each time the web service context is destroyed and number
> keeps growing for each deployment of the .war file.

Oh, I believe you that they are piling up.

Is there a particular reason you are using Oracle's connection pool rather than 
the one provided by the container (Tomcat)? Tomcat's pool won't leak like this 
one does. Then again, the Oracle driver itself might still leak, but it will be 
less leaky.

It's possible that the driver needs to be loaded before the application in 
order to avoid pinning the ClassLoader into memory.
That can be done with Tomcat's configuration, but I'd only recommend that you 
do this if nothing else is working.

I'd still like to know that those other threads (e.g. Thread-0) are doin g.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlbdnygACgkQ9CaO5/Lv0PCClgCfUmDNGz68sT6beiMOwx2Pkewb
UGcAoJNpSVJ8wagZRiGZMS9LxO3g0KY9
=qWGg
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.

Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/7/16 9:51 AM, Chris Brown wrote:
> Tomcat is shutting down the web service when I deploy a new .war 
> file.

Okay. You said you were closing the connection pool, though:

On 3/4/16 2:13 PM, Chris Brown wrote:
> I added a ServletContextListener to our web service.  On the 
> contextDestroyed method we destroy the connection pools.  Our web 
> service uses 2 connection pools.

So, how, precisely, are you shutting those pools down?

> There is no documentation on the threads and what they are for in 
> oracle or tomcats documentation.

Tomcat would not contain information on a Vendor's product. A quick
Google search for "oracle ojdbc7 ucp-worker-thread" yields the
following very relevant result:

http://stackoverflow.com/questions/9671270/oracle-ucp-driver-and-tomcat-
threads-failing-to-stop

Also, searching for the OJDBC manual has a FAQ which mentions threads
and their lifetimes:
http://www.oracleimg.com/technetwork/articles/sql/jdbc-faq-090281.html

> The threads are not shutting down and they stay alive when the web
>  service is shut down. I know this because I count the number of 
> threads each time the web service context is destroyed and number 
> keeps growing for each deployment of the .war file.

Oh, I believe you that they are piling up.

Is there a particular reason you are using Oracle's connection pool
rather than the one provided by the container (Tomcat)? Tomcat's pool
won't leak like this one does. Then again, the Oracle driver itself
might still leak, but it will be less leaky.

It's possible that the driver needs to be loaded before the
application in order to avoid pinning the ClassLoader into memory.
That can be done with Tomcat's configuration, but I'd only recommend
that you do this if nothing else is working.

I'd still like to know that those other threads (e.g. Thread-0) are doin
g.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlbdnygACgkQ9CaO5/Lv0PCClgCfUmDNGz68sT6beiMOwx2Pkewb
UGcAoJNpSVJ8wagZRiGZMS9LxO3g0KY9
=qWGg
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Chris Brown]

Tomcat is shutting down the web service when I deploy a new .war file.  There 
is no documentation on the threads and what they are for in oracle or tomcats 
documentation.

The threads are not shutting down and they stay alive when the web service is 
shut down.  I know this because I count the number of threads each time the web 
service context is destroyed and number keeps growing for each deployment of 
the .war file.

Thank you,
Chris Brown
Systems Consultant
National Council on
Compensation Insurance
901 Peninsula Corporate Circle
Boca Raton, FL 33487-1362
(P) 561-893-2324
chris_br...@ncci.com


-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Monday, March 07, 2016 9:47 AM
To: Tomcat Users List
Subject: Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/7/16 8:26 AM, Chris Brown wrote:
> The .jar comes with the Oracle 12c client.   Oracle JDBC Drivers
> release 12.1.0.2.0

Thanks.

> I upgraded to tomcat 8.  The latest stable version.  The issue still
> occurred, but the messages in the logs were "Warnings"
> instead of being "SEVERE" errors.

You said that.

How about taking a thread dump after your web application stops, to see a few 
things:

1. Whether this is a spurious notification, since Tomcat was just going down 
faster than the threads were able to (gracefully) shut down

2. What those threads are doing, especially the ones with the somewhat 
anonymous names

You haven't said how you were shutting-down the thread pool.

You also haven't said whether you read any or Oracle's documentation about what 
those threads are doing or how they should be terminated.

- -chris

> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Friday, March 04, 2016
> 4:33 PM To: Tomcat Users List Subject: Re: Tomcat 7 Web Service
> Shutdown Can't Stop Threads
>
> Chris,
>
> On 3/4/16 2:13 PM, Chris Brown wrote:
>> Tomcat version: 7.0.42 Server OS: Sun Solaris UCP Version: Oracle 12c
>> Oracle Driver: ojdbc7
>
> That doesn't look like an Oracle JDBC driver version I've seen before.
> Can you clarify?
>
>> JDK version: 1.8.0_31
>
> You might want to upgrade Tomcat and Java. Those are somewhat old.
>
>> Issue Description: When tomcat shuts down our web service during a
>> hot deployment threads are left running that tomcat cannot shutdown.
>> I believe the threads are from the universal connection pool. We use
>> oracle's universal connection pool (ucp.jar). After multiple
>> deployments the threads build up and cause high CPU usage from the 2
>> tomcat threads.
>
>> Log Error Examples: Feb 08, 2016 8:00:25 PM
>> org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application [/RatingService]
>> appears to have started a thread named [UCP-worker-thread-3] but has
>> failed to stop it. This is very likely to create a memory leak. Feb
>> 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application [/RatingService]
>> appears to have started a thread named [Thread-438] but has failed to
>> stop it. This is very likely to create a memory leak. Feb 27, 2016
>> 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application [/RatingService]
>> appears to have started a thread named
>> [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockRelea
s
>
>>
er]
>> but has failed to stop it. This is very likely to create a
>> memory leak. Feb 27, 2016 6:15:14 PM
>> org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named
>> [ForkJoinPool.commonPool-worker-32] but has failed to stop it.
>> This is very likely to create a memory leak. Feb 27, 2016 6:15:14
>> PM org.apache.catalina.loader.WebappClassLoader
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named
>> [Timer-121] but has failed to stop it. This is very likely to
>> create a memory leak.
>
>> Correction made to code to try and fix issue: I added a
>> ServletContextListener to our web service. On the
>> contextDestroyed method we destroy the connection pools. Our web
>> service uses 2 connection pools.
>
> How exactly are you destroying the connection pools?
>
>> I also upgraded to Tomcat 8 and the issue still occurred, but
>> the messages are now warnings instead of SEVERE errors.
>
> That's just an effect of Tomcat downgrading the log level under
> which it log

Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/7/16 8:26 AM, Chris Brown wrote:
> The .jar comes with the Oracle 12c client.   Oracle JDBC Drivers 
> release 12.1.0.2.0

Thanks.

> I upgraded to tomcat 8.  The latest stable version.  The issue
> still occurred, but the messages in the logs were "Warnings"
> instead of being "SEVERE" errors.

You said that.

How about taking a thread dump after your web application stops, to
see a few things:

1. Whether this is a spurious notification, since Tomcat was just
going down faster than the threads were able to (gracefully) shut down

2. What those threads are doing, especially the ones with the somewhat
anonymous names

You haven't said how you were shutting-down the thread pool.

You also haven't said whether you read any or Oracle's documentation
about what those threads are doing or how they should be terminated.

- -chris

> -Original Message- From: Christopher Schultz
> [mailto:ch...@christopherschultz.net] Sent: Friday, March 04, 2016
> 4:33 PM To: Tomcat Users List Subject: Re: Tomcat 7 Web Service
> Shutdown Can't Stop Threads
> 
> Chris,
> 
> On 3/4/16 2:13 PM, Chris Brown wrote:
>> Tomcat version: 7.0.42 Server OS: Sun Solaris UCP Version: Oracle
>> 12c Oracle Driver: ojdbc7
> 
> That doesn't look like an Oracle JDBC driver version I've seen
> before. Can you clarify?
> 
>> JDK version: 1.8.0_31
> 
> You might want to upgrade Tomcat and Java. Those are somewhat old.
> 
>> Issue Description: When tomcat shuts down our web service during
>> a hot deployment threads are left running that tomcat cannot
>> shutdown. I believe the threads are from the universal connection
>> pool. We use oracle's universal connection pool (ucp.jar). After
>> multiple deployments the threads build up and cause high CPU
>> usage from the 2 tomcat threads.
> 
>> Log Error Examples: Feb 08, 2016 8:00:25 PM 
>> org.apache.catalina.loader.WebappClassLoader 
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named
>> [UCP-worker-thread-3] but has failed to stop it. This is very
>> likely to create a memory leak. Feb 08, 2016 8:00:25 PM
>> org.apache.catalina.loader.WebappClassLoader 
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named
>> [Thread-438] but has failed to stop it. This is very likely to
>> create a memory leak. Feb 27, 2016 6:15:14 PM
>> org.apache.catalina.loader.WebappClassLoader 
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named 
>> [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockRelea
s
>
>> 
er]
>> but has failed to stop it. This is very likely to create a
>> memory leak. Feb 27, 2016 6:15:14 PM 
>> org.apache.catalina.loader.WebappClassLoader 
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named 
>> [ForkJoinPool.commonPool-worker-32] but has failed to stop it.
>> This is very likely to create a memory leak. Feb 27, 2016 6:15:14
>> PM org.apache.catalina.loader.WebappClassLoader 
>> clearReferencesThreads SEVERE: The web application
>> [/RatingService] appears to have started a thread named
>> [Timer-121] but has failed to stop it. This is very likely to
>> create a memory leak.
> 
>> Correction made to code to try and fix issue: I added a 
>> ServletContextListener to our web service. On the
>> contextDestroyed method we destroy the connection pools. Our web
>> service uses 2 connection pools.
> 
> How exactly are you destroying the connection pools?
> 
>> I also upgraded to Tomcat 8 and the issue still occurred, but
>> the messages are now warnings instead of SEVERE errors.
> 
> That's just an effect of Tomcat downgrading the log level under
> which it logs those issues.
> 
>> I've searched the web and have tried many suggestions that have
>> not helped except destroying the connection pools, but the issue
>> still occurs. Please help!!!
> 
> After you get those messages in the log, if you do a thread dump on
> the JVM, do you still see those threads running?
> 
> Generally speaking, Tomcat should be able to shut down even with
> the above errors. Hopefully, none of those threads are non-daemon
> threads, meaning that they shouldn't stop the JVM from stopping
> once the JVM's main thread terminates. If your web application
> leaves those threads running after deployment, then multiple
> re-deployments without a Tomcat/JVM restart will l

RE: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Chris Brown]

The .jar comes with the Oracle 12c client.   Oracle JDBC Drivers release 
12.1.0.2.0

I upgraded to tomcat 8.  The latest stable version.  The issue still occurred, 
but the messages in the logs were "Warnings" instead of being "SEVERE" errors.

Thank you,
Chris Brown
Systems Consultant
National Council on
Compensation Insurance
901 Peninsula Corporate Circle
Boca Raton, FL 33487-1362
(P) 561-893-2324
chris_br...@ncci.com

-Original Message-
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Friday, March 04, 2016 4:33 PM
To: Tomcat Users List
Subject: Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/4/16 2:13 PM, Chris Brown wrote:
> Tomcat version: 7.0.42 Server OS: Sun Solaris UCP Version: Oracle 12c
> Oracle Driver: ojdbc7

That doesn't look like an Oracle JDBC driver version I've seen before.
Can you clarify?

> JDK version: 1.8.0_31

You might want to upgrade Tomcat and Java. Those are somewhat old.

> Issue Description: When tomcat shuts down our web service during a hot
> deployment threads are left running that tomcat cannot shutdown. I
> believe the threads are from the universal connection pool. We use
> oracle's universal connection pool (ucp.jar). After multiple
> deployments the threads build up and cause high CPU usage from the 2
> tomcat threads.
>
> Log Error Examples: Feb 08, 2016 8:00:25 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [UCP-worker-thread-3] but has
> failed to stop it. This is very likely to create a memory leak. Feb
> 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [Thread-438] but has failed to
> stop it. This is very likely to create a memory leak. Feb 27,
> 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named
> [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleas
er]
> but has failed to stop it. This is very likely to create a memory
> leak. Feb 27, 2016 6:15:14 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named
> [ForkJoinPool.commonPool-worker-32] but has failed to stop it. This is
> very likely to create a memory leak. Feb 27, 2016 6:15:14 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [Timer-121] but has failed to
> stop it. This is very likely to create a memory leak.
>
> Correction made to code to try and fix issue: I added a
> ServletContextListener to our web service. On the contextDestroyed
> method we destroy the connection pools. Our web service uses 2
> connection pools.

How exactly are you destroying the connection pools?

> I also upgraded to Tomcat 8 and the issue still occurred, but the
> messages are now warnings instead of SEVERE errors.

That's just an effect of Tomcat downgrading the log level under which it logs 
those issues.

> I've searched the web and have tried many suggestions that have not
> helped except destroying the connection pools, but the issue still
> occurs. Please help!!!

After you get those messages in the log, if you do a thread dump on the JVM, do 
you still see those threads running?

Generally speaking, Tomcat should be able to shut down even with the above 
errors. Hopefully, none of those threads are non-daemon threads, meaning that 
they shouldn't stop the JVM from stopping once the JVM's main thread 
terminates. If your web application leaves those threads running after 
deployment, then multiple re-deployments without a Tomcat/JVM restart will 
likely result in a large memory leak. (Those threads will pin the web 
application's ClassLoader in memory along with all the classes it ever loaded, 
and these will pile-up until you have exhausted your permgen or other heap 
spaces).

> [UCP-worker-thread-3]

This is almost certainly something form Oracle's UCP

> [Thread-438]

This could be anything. A thread dump could tell you what it might be.

>
[oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser
]

Obviously, this is a thread from Oracle's JDBC driver.

> [ForkJoinPool.commonPool-worker-32]

Maybe something from UCP? Not sure.

> [Timer-121]

This is usually a thread started by TimerTask, a stock Java class. But any 
component may have created this thread. It might be worth searching your own 
code to see if a TimerTask is being launched and never shut-d

Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

[patrycio .]

Chris sing a song for us.
Em 04/03/2016 16:13, "Chris Brown"  escreveu:

> Tomcat version: 7.0.42
> Server OS: Sun Solaris
> UCP Version: Oracle 12c
> Oracle Driver: ojdbc7
> JDK version: 1.8.0_31
>
> Issue Description:
> When tomcat shuts down our web service during a hot deployment threads are
> left running that tomcat cannot shutdown.  I believe the threads are from
> the universal connection pool.  We use oracle's universal connection pool
> (ucp.jar).  After multiple deployments the threads build up and cause high
> CPU usage from the 2 tomcat threads.
>
> Log Error Examples:
> Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/RatingService] appears to have started a
> thread named [UCP-worker-thread-3] but has failed to stop it. This is very
> likely to create a memory leak.
> Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/RatingService] appears to have started a
> thread named [Thread-438] but has failed to stop it. This is very likely to
> create a memory leak.
> Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/RatingService] appears to have started a
> thread named
> [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser]
> but has failed to stop it. This is very likely to create a memory leak.
> Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/RatingService] appears to have started a
> thread named [ForkJoinPool.commonPool-worker-32] but has failed to stop it.
> This is very likely to create a memory leak.
> Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads
> SEVERE: The web application [/RatingService] appears to have started a
> thread named [Timer-121] but has failed to stop it. This is very likely to
> create a memory leak.
>
> Correction made to code to try and fix issue:
> I added a ServletContextListener to our web service.  On the
> contextDestroyed method we destroy the connection pools.  Our web service
> uses 2 connection pools.
>
> I also upgraded to Tomcat 8 and the issue still occurred, but the messages
> are now warnings instead of SEVERE errors.
>
> I've searched the web and have tried many suggestions that have not helped
> except destroying the connection pools, but the issue still occurs.  Please
> help!!!
>
> Thank you,
> Chris Brown
> Systems Consultant
> National Council on
> Compensation Insurance
> 901 Peninsula Corporate Circle
> Boca Raton, FL 33487-1362
> (P) 561-893-2324
> chris_br...@ncci.com
>
>
>
> 
>
> The information contained in this e-mail message is intended only for the
> personal and confidential use of the recipient(s) named above. This message
> may be an attorney-client communication and/or work product and as such is
> privileged and confidential. If the reader of this message is not the
> intended recipient or an agent responsible for delivering it to the
> intended recipient, you are hereby notified that you have received this
> document in error and that any review, dissemination, distribution, or
> copying of this message is strictly prohibited. If you have received this
> communication in error, please notify us immediately by e-mail, and delete
> the original message.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: Tomcat 7 Web Service Shutdown Can't Stop Threads

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris,

On 3/4/16 2:13 PM, Chris Brown wrote:
> Tomcat version: 7.0.42 Server OS: Sun Solaris UCP Version: Oracle
> 12c Oracle Driver: ojdbc7

That doesn't look like an Oracle JDBC driver version I've seen before.
Can you clarify?

> JDK version: 1.8.0_31

You might want to upgrade Tomcat and Java. Those are somewhat old.

> Issue Description: When tomcat shuts down our web service during a
> hot deployment threads are left running that tomcat cannot
> shutdown. I believe the threads are from the universal connection
> pool. We use oracle's universal connection pool (ucp.jar). After
> multiple deployments the threads build up and cause high CPU usage
> from the 2 tomcat threads.
> 
> Log Error Examples: Feb 08, 2016 8:00:25 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [UCP-worker-thread-3] but
> has failed to stop it. This is very likely to create a memory
> leak. Feb 08, 2016 8:00:25 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [Thread-438] but has failed
> to stop it. This is very likely to create a memory leak. Feb 27,
> 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named
> [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleas
er]
> but has failed to stop it. This is very likely to create a memory
> leak. Feb 27, 2016 6:15:14 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named
> [ForkJoinPool.commonPool-worker-32] but has failed to stop it. This
> is very likely to create a memory leak. Feb 27, 2016 6:15:14 PM
> org.apache.catalina.loader.WebappClassLoader
> clearReferencesThreads SEVERE: The web application [/RatingService]
> appears to have started a thread named [Timer-121] but has failed
> to stop it. This is very likely to create a memory leak.
> 
> Correction made to code to try and fix issue: I added a
> ServletContextListener to our web service. On the contextDestroyed
> method we destroy the connection pools. Our web service uses 2
> connection pools.

How exactly are you destroying the connection pools?

> I also upgraded to Tomcat 8 and the issue still occurred, but the 
> messages are now warnings instead of SEVERE errors.

That's just an effect of Tomcat downgrading the log level under which
it logs those issues.

> I've searched the web and have tried many suggestions that have
> not helped except destroying the connection pools, but the issue
> still occurs. Please help!!!

After you get those messages in the log, if you do a thread dump on
the JVM, do you still see those threads running?

Generally speaking, Tomcat should be able to shut down even with the
above errors. Hopefully, none of those threads are non-daemon threads,
meaning that they shouldn't stop the JVM from stopping once the JVM's
main thread terminates. If your web application leaves those threads
running after deployment, then multiple re-deployments without a
Tomcat/JVM restart will likely result in a large memory leak. (Those
threads will pin the web application's ClassLoader in memory along
with all the classes it ever loaded, and these will pile-up until you
have exhausted your permgen or other heap spaces).

> [UCP-worker-thread-3]

This is almost certainly something form Oracle's UCP

> [Thread-438]

This could be anything. A thread dump could tell you what it might be.

> 
[oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser
]

Obviously, this is a thread from Oracle's JDBC driver.

> [ForkJoinPool.commonPool-worker-32]

Maybe something from UCP? Not sure.

> [Timer-121]

This is usually a thread started by TimerTask, a stock Java class. But
any component may have created this thread. It might be worth
searching your own code to see if a TimerTask is being launched and
never shut-down when your web application is shutting down. Make
arrangements to make sure that you shut these down when the
application is going out of service.

For the Oracle-specific threads, read the documentation or search
online for how to stop those threads as the application is coming
down. There could be a bug in the library(ies) that might be fixed in
a more recent version.

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlbZ/woACgkQ9CaO5/Lv0PBwvwCeLblpAKfIen1G0nmZvoqkLgWe
qCoAnR84mW3an4+BOVKvzuQTI2fTTodx
=5+gA
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, 

Tomcat 7 Web Service Shutdown Can't Stop Threads

[Chris Brown]

Tomcat version: 7.0.42
Server OS: Sun Solaris
UCP Version: Oracle 12c
Oracle Driver: ojdbc7
JDK version: 1.8.0_31

Issue Description:
When tomcat shuts down our web service during a hot deployment threads are left 
running that tomcat cannot shutdown.  I believe the threads are from the 
universal connection pool.  We use oracle's universal connection pool 
(ucp.jar).  After multiple deployments the threads build up and cause high CPU 
usage from the 2 tomcat threads.

Log Error Examples:
Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/RatingService] appears to have started a thread 
named [UCP-worker-thread-3] but has failed to stop it. This is very likely to 
create a memory leak.
Feb 08, 2016 8:00:25 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/RatingService] appears to have started a thread 
named [Thread-438] but has failed to stop it. This is very likely to create a 
memory leak.
Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/RatingService] appears to have started a thread 
named [oracle.jdbc.driver.BlockSource.ThreadedCachingBlockSource.BlockReleaser] 
but has failed to stop it. This is very likely to create a memory leak.
Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/RatingService] appears to have started a thread 
named [ForkJoinPool.commonPool-worker-32] but has failed to stop it. This is 
very likely to create a memory leak.
Feb 27, 2016 6:15:14 PM org.apache.catalina.loader.WebappClassLoader 
clearReferencesThreads
SEVERE: The web application [/RatingService] appears to have started a thread 
named [Timer-121] but has failed to stop it. This is very likely to create a 
memory leak.

Correction made to code to try and fix issue:
I added a ServletContextListener to our web service.  On the contextDestroyed 
method we destroy the connection pools.  Our web service uses 2 connection 
pools.

I also upgraded to Tomcat 8 and the issue still occurred, but the messages are 
now warnings instead of SEVERE errors.

I've searched the web and have tried many suggestions that have not helped 
except destroying the connection pools, but the issue still occurs.  Please 
help!!!

Thank you,
Chris Brown
Systems Consultant
National Council on
Compensation Insurance
901 Peninsula Corporate Circle
Boca Raton, FL 33487-1362
(P) 561-893-2324
chris_br...@ncci.com





The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: AW: Problems to configure tomcat as windows service

[Aurélien Terrestris]

OK good that it's finally working.
There is a weakness in the documentation since it duplicates a big part of
the original procrun doc, and it would more readable to just give a short
explanation and give a link as you suggest. You can ask for an improvement
in the bug database ( http://tomcat.apache.org/bugreport.html) but I'm not
sure they will spend time on it as there is no "real" mistake in the doc.

regards


2015-10-09 9:15 GMT+02:00 Arno Schäfer :

> Aurélien,
>
> > still investigating for you in the documentation (
> http://commons.apache.org/proper/commons-daemon/procrun.html ), can you
> try again with --ServiceUser & --ServicePassword instead of --User &
> --Password ?
>
> thanks for that hint. I try it and it works now. :-)
> I miss the point, that my start mode 'jvm' was excluded, but no
> alternative is described in the tomcat documentation.
> Perhaps it will be a good idea to integrate a link to the original procrun
> documentation, when it is more up to date and complete. I didn't recognize
> til today, that this is a separate project.
>
> Thanks for your patience,
> best regards
> Arno
>
>

AW: AW: Problems to configure tomcat as windows service

[Arno Schäfer]

Aurélien,

> still investigating for you in the documentation ( 
> http://commons.apache.org/proper/commons-daemon/procrun.html ), can you try 
> again with --ServiceUser & --ServicePassword instead of --User & --Password ?

thanks for that hint. I try it and it works now. :-)
I miss the point, that my start mode 'jvm' was excluded, but no alternative is 
described in the tomcat documentation.
Perhaps it will be a good idea to integrate a link to the original procrun 
documentation, when it is more up to date and complete. I didn't recognize til 
today, that this is a separate project.

Thanks for your patience,
best regards
Arno

AW: AW: Problems to configure tomcat as windows service

[Arno Schäfer]

Hi Aurélien,

> Arno, can you try with these parameters : --StdOutput out.txt --StdError 
> err.txt 
> and check if this writes anything to these files (I don't bet a pence on this 
> but let's try) ?

That isn't the point. My problem is, that I can't configure a different service 
user as the local system account with this utility. 'tomcat7.exe' configure all 
other parameter as you can see afterwards in the 'serverconsole' utility except 
the '--User' and '--Password' on Windows 8.1 64 bit with no error message. It 
only ignores these both values.
The service is running in all cases under the local system account and I can 
manualy change to an other user and it still works.
So, do you know, what is the normal process to report a bug to the development?

I have to revert my statement from the mail before: It didn't work also with 
tomcat6 on Windows 8.1 64 Bit

> Taken from the doc :
> http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html

I know this document very well ;-)

regards
Arno

Re: AW: Problems to configure tomcat as windows service

[Aurélien Terrestris]

Arno, can you try with these parameters : --StdOutput out.txt --StdError
err.txt and check if this writes anything to these files (I don't bet a
pence on this but let's try) ?

Taken from the doc :
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html



2015-10-02 17:52 GMT+02:00 Arno Schäfer <arno.schae...@sqs.com>:

> André,
>
> > Maybe it is not only the version of Tomcat that has changed, but also
> the machine/OS on which
> > you do this ? Maybe the user under which you execute this command does
> not have the
> > required
> > privileges, at OS level on this machine, to do this ?
>
> On the same machine/OS it work's with tomcat 6.
>
>
> > Maybe the user-id *to* which you are trying to set the Tomcat service,
> does not have enough
> > privileges to "run as a Service" ?
> > (In the services.msc applet, it would ask you interactively to grant
> these privileges first, but
> > maybe the command-line tool cannot do that).
>
> Like I said in my first mail, I install it as an local administrator and
> the service was registered and I am able to run it under the local system
> account.
> And also if I fill in the user data manually, what I used in the
> tomcat7.exe call, I am able to start and run the tomcat server, so missing
> privileges shouldn't be the problem.
>
> Regards
> Arno
>
>

Re: AW: Problems to configure tomcat as windows service

[Aurélien Terrestris]

Arno,

still investigating for you in the documentation (
http://commons.apache.org/proper/commons-daemon/procrun.html ), can you try
again with --ServiceUser & --ServicePassword instead of --User & --Password
?

regards

2015-10-08 17:35 GMT+02:00 Arno Schäfer <arno.schae...@sqs.com>:

> Hi Aurélien,
>
> > Arno, can you try with these parameters : --StdOutput out.txt --StdError
> err.txt
> > and check if this writes anything to these files (I don't bet a pence on
> this but let's try) ?
>
> That isn't the point. My problem is, that I can't configure a different
> service user as the local system account with this utility. 'tomcat7.exe'
> configure all other parameter as you can see afterwards in the
> 'serverconsole' utility except the '--User' and '--Password' on Windows 8.1
> 64 bit with no error message. It only ignores these both values.
> The service is running in all cases under the local system account and I
> can manualy change to an other user and it still works.
> So, do you know, what is the normal process to report a bug to the
> development?
>
> I have to revert my statement from the mail before: It didn't work also
> with tomcat6 on Windows 8.1 64 Bit
>
> > Taken from the doc :
> > http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html
>
> I know this document very well ;-)
>
> regards
> Arno
>
>

Problems to configure tomcat as windows service

[Arno Schäfer]

Hi all,

using tomcat 7.0.54 on Windows 8.1 64 Bit system, I encounter the problem, that 
I can not configure a user/password
with the tomcat7.exe utility. I run this as a local administrator in a DOS box 
with a valid user and password it returned
with errorlevel 0, but the user was not set in the service settings.

What can be the reason for this? The same solution run before in a tomcat 6 
environment with no problems and I
recognize no changes in the documentation in this area.

best regard
Arno

_



Vorsitzender des Aufsichtsrats: David Bellin
Vorstand: Diederik Vos (CEO) ? Ralph Gillessen (COO) ? René Gawron (CFO)
SQS AG ? Stollwerckstraße 11 ? 51149 Köln
Sitz der Gesellschaft: Köln ? Amtsgericht Köln, HRB 12764

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient
(or have received this e-mail in error) please notify the sender immediately 
and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this 
e-mail is strictly forbidden.

AW: Problems to configure tomcat as windows service

[Arno Schäfer]

Thanks for the hint Aurélien,

> there *maybe is* documentation about this, see question & comments from 
> Konstantin Kolinko in 
> http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html

but I asked this question, because I recognize, that it didn't worked like it 
is described, but in version 6 the description was the same and it has worked.

Regards
Arno

Re: AW: Problems to configure tomcat as windows service

[tomcat]

On 02.10.2015 17:12, Arno Schäfer wrote:

Thanks for the hint Aurélien,


there *maybe is* documentation about this, see question & comments from 
Konstantin Kolinko in 
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html


but I asked this question, because I recognize, that it didn't worked like it 
is described, but in version 6 the description was the same and it has worked.



Maybe it is not only the version of Tomcat that has changed, but also the 
machine/OS on which

you do this ? Maybe the user under which you execute this command does not have 
the required

privileges, at OS level on this machine, to do this ?

Maybe the user-id *to* which you are trying to set the Tomcat service, does not have 
enough privileges to "run as a Service" ?
(In the services.msc applet, it would ask you interactively to grant these privileges 
first, but maybe the command-line tool cannot do that).


(I am not really a Windows OS specialist, but I have seen variations of the above kind of 
issues previously)




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Problems to configure tomcat as windows service

[Aurélien Terrestris]

Arno,

there *maybe is* documentation about this, see question & comments
from Konstantin Kolinko in
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html





2015-10-02 16:36 GMT+02:00 Arno Schäfer <arno.schae...@sqs.com>:

> Hi all,
>
> using tomcat 7.0.54 on Windows 8.1 64 Bit system, I encounter the problem,
> that I can not configure a user/password
> with the tomcat7.exe utility. I run this as a local administrator in a DOS
> box with a valid user and password it returned
> with errorlevel 0, but the user was not set in the service settings.
>
> What can be the reason for this? The same solution run before in a tomcat
> 6 environment with no problems and I
> recognize no changes in the documentation in this area.
>
> best regard
> Arno
>
> _
>
>
>
> Vorsitzender des Aufsichtsrats: David Bellin
> Vorstand: Diederik Vos (CEO) ? Ralph Gillessen (COO) ? René Gawron (CFO)
> SQS AG ? Stollwerckstraße 11 ? 51149 Köln
> Sitz der Gesellschaft: Köln ? Amtsgericht Köln, HRB 12764
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient
> (or have received this e-mail in error) please notify the sender
> immediately and destroy this e-mail.
> Any unauthorised copying, disclosure or distribution of the material in
> this e-mail is strictly forbidden.
>

AW: AW: Problems to configure tomcat as windows service

[Arno Schäfer]

André,

> Maybe it is not only the version of Tomcat that has changed, but also the 
> machine/OS on which
> you do this ? Maybe the user under which you execute this command does not 
> have the 
> required
> privileges, at OS level on this machine, to do this ?

On the same machine/OS it work's with tomcat 6.


> Maybe the user-id *to* which you are trying to set the Tomcat service, does 
> not have enough 
> privileges to "run as a Service" ?
> (In the services.msc applet, it would ask you interactively to grant these 
> privileges first, but 
> maybe the command-line tool cannot do that).

Like I said in my first mail, I install it as an local administrator and the 
service was registered and I am able to run it under the local system account.
And also if I fill in the user data manually, what I used in the tomcat7.exe 
call, I am able to start and run the tomcat server, so missing privileges 
shouldn't be the problem.

Regards
Arno

Re: Problems to configure tomcat as windows service

[tomcat]

On 02.10.2015 16:36, Arno Schäfer wrote:

Hi all,

using tomcat 7.0.54 on Windows 8.1 64 Bit system, I encounter the problem, that 
I can not configure a user/password
with the tomcat7.exe utility. I run this as a local administrator in a DOS box 
with a valid user and password it returned
with errorlevel 0, but the user was not set in the service settings.

What can be the reason for this? The same solution run before in a tomcat 6 
environment with no problems and I
recognize no changes in the documentation in this area.



Hi.
What exactly /is/ the problem ?
- that you cannot change the user-id under which it runs (which by default should be 
something like LocalService) ?

- or that you can change it, but then it crashes when you run it ?

If the last, then one more question : does your Tomcat or any of its applications need 
access to any network shared directory ?




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

AW: Problems to configure tomcat as windows service

[Arno Schäfer]

Hi Andre,

> What exactly /is/ the problem ?

'XXX' is not configured and doesn't exist. if I then call 
'tomcat7 //IS//XXX --User="domain\user" --Password="xx" 
the call return with exitcode 0 and if I look in the services.msc the service 
XXX is installed, but run as local system account. The --User and --Password 
was ignored. All other parameters was accepted. I have also double checked it 
with the serverconsole.bat.

Regards
Arno


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[André Warnier]

Alapan Sur wrote:

Hi Team,

 


We have .Net application consuming tomcat solr3.5 services and deployed on
Windows Server 2012. Its is 64 bit machine with 32 GB RAM and Tomcat veriosn
is 6 and is installed at :C:\Program Files (x86)\Apache Software
Foundation\Tomcat 6.0. During the peak load, the solr sevice
stops/unresponsive and it is happening very frequently. We didnt fount any
erro logs in windows event viewer but in tomcat logs we got the following
exception :

Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
369) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at
org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
at
org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.ja
va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at
sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at
sun.nio.cs.StreamEncoder.write(Unknown Source) at
java.io.OutputStreamWriter.write(Unknown Source) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at
org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at
org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at
org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) at
org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.java:35)
at
org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.
java:343) at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:
265) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:235) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103
) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:606) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at
java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException:
Software caused connection abort: socket write error at
java.net.SocketOutputStream.socketWrite0(Native Method) at
java.net.SocketOutputStream.socketWrite(Unknown Source) at
java.net.SocketOutputStream.write(Unknown Source) at
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputB
uffer.java:761) at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:448) at
org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:363) at
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri
te(InternalOutputBuffer.java:785) at
org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFi
lter.java:126) at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j
ava:598) at org.apache.coyote.Response.doWrite(Response.java:560) at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
364) ... 36 more

Aug 06, 2014 10:51:29 AM org.apache.solr.common.SolrException log SEVERE:
java.lang.OutOfMemoryError: Java heap space at
org.apache.lucene.search.ExactPhraseScorer.(ExactPhraseScorer.java:38) at
org.apache.lucene.search.PhraseQuery$PhraseWeight.scorer(PhraseQuery.java:22
7) at
org.apache.lucene.search.BooleanQuery$BooleanWeight.scorer(BooleanQuery.java
:298) at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:577) at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:364) at
org.apache.solr.search.SolrIndexSearcher.getDocListAndSetNC(SolrIndexSearche
r.java:1408) at

Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[Luciano Fioriti]

Hi,

try to increase Maximum number of threads in server.xml

bie


2014-08-07 6:57 GMT+02:00 Alapan Sur alapan@valuelabs.com:

 Hi Team,



 We have .Net application consuming tomcat solr3.5 services and deployed on
 Windows Server 2012. Its is 64 bit machine with 32 GB RAM and Tomcat
 veriosn
 is 6 and is installed at :C:\Program Files (x86)\Apache Software
 Foundation\Tomcat 6.0. During the peak load, the solr sevice
 stops/unresponsive and it is happening very frequently. We didnt fount any
 erro logs in windows event viewer but in tomcat logs we got the following
 exception :

 Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:
 ClientAbortException: java.net.SocketException: Software caused connection
 abort: socket write error at

 org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
 369) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at

 org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)
 at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
 at

 org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.ja
 va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at
 sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at
 sun.nio.cs.StreamEncoder.write(Unknown Source) at
 java.io.OutputStreamWriter.write(Unknown Source) at
 org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at
 org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at
 org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at
 org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at
 org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at
 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at
 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
 org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) at
 org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.java:35)
 at

 org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.
 java:343) at

 org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:
 265) at

 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
 FilterChain.java:235) at

 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
 ain.java:206) at

 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
 va:233) at

 org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
 va:191) at

 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
 ) at

 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103
 ) at

 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
 :109) at
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
 at
 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
 at

 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
 11Protocol.java:606) at
 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at
 java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException:
 Software caused connection abort: socket write error at
 java.net.SocketOutputStream.socketWrite0(Native Method) at
 java.net.SocketOutputStream.socketWrite(Unknown Source) at
 java.net.SocketOutputStream.write(Unknown Source) at

 org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputB
 uffer.java:761) at
 org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:448) at
 org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:363) at

 org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri
 te(InternalOutputBuffer.java:785) at

 org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFi
 lter.java:126) at

 org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j
 ava:598) at org.apache.coyote.Response.doWrite(Response.java:560) at

 org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
 364) ... 36 more

 Aug 06, 2014 10:51:29 AM org.apache.solr.common.SolrException log SEVERE:
 java.lang.OutOfMemoryError: Java heap space at
 org.apache.lucene.search.ExactPhraseScorer.(ExactPhraseScorer.java:38) at

 org.apache.lucene.search.PhraseQuery$PhraseWeight.scorer(PhraseQuery.java:22
 7) at

 org.apache.lucene.search.BooleanQuery$BooleanWeight.scorer(BooleanQuery.java
 :298) at
 

Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[André Warnier]

Luciano,

1) try to not top-post on this list. See 
https://tomcat.apache.org/lists.html#tomcat-users, item # 6


2)

Luciano Fioriti wrote:

Hi,

try to increase Maximum number of threads in server.xml

bie


Not so fast...
Tomcat is indeed running out of threads, as the last INFO message indicates.
But this is probably more a *symptom* of some other underlying issue, as shown by the 
previous exceptions.

Don't treat the symptom, treat the cause.




2014-08-07 6:57 GMT+02:00 Alapan Sur alapan@valuelabs.com:


Hi Team,



We have .Net application consuming tomcat solr3.5 services and deployed on
Windows Server 2012. Its is 64 bit machine with 32 GB RAM and Tomcat
veriosn
is 6 and is installed at :C:\Program Files (x86)\Apache Software
Foundation\Tomcat 6.0. During the peak load, the solr sevice
stops/unresponsive and it is happening very frequently. We didnt fount any
erro logs in windows event viewer but in tomcat logs we got the following
exception :

Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error at


this is ClientAbortException, happening (as the chain below seems to show) when the 
application is trying to write a response to the client (presumably the user browser).
This generally happens when Tomcat tries to send back a response, but the client has 
already closed the connection.  Which in turn may happen if the client has been waiting 
too long for this response (more than 2-3 minutes).
(It can also happen if the human user of that browser got tired of waiting, and clicked 
somewhere else, or closed the window).


But a web application should not normally take so long to respond (or at least not without 
letting the user know that it can take long, or provide some kind of feedback while the 
user is waiting).


So again, there is probably something else going on..



org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
369) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at

org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
at

org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.ja
va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at
sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at
sun.nio.cs.StreamEncoder.write(Unknown Source) at
java.io.OutputStreamWriter.write(Unknown Source) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at
org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at
org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at
org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) at
org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.java:35)
at

org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.
java:343) at

org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:
265) at

org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:235) at

org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206) at

org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233) at

org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191) at

org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
) at

org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103
) at

org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
at

org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:606) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at
java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException:
Software caused connection abort: socket write error at
java.net.SocketOutputStream.socketWrite0(Native Method) at
java.net.SocketOutputStream.socketWrite(Unknown Source) at
java.net.SocketOutputStream.write(Unknown Source) at

RE: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[Alapan Sur]

Hi Andre,

 

Thanks for the quick reply.

 

I have verified the below requested memory related queries as suggested by
you. The Initial memory pool and Maximum memory pool are empty and please
find the attachment for the same.



 

We have checked the heap size with the command : java -XX:+PrintFlagsFinal
-version | findstr /i HeapSize PermSize ThreadStackSize



 

Can you please guide how to increase the java memory pool heap size to 1GB ?

 

Cheers,

Alapan

-Original Message-
From: André Warnier [mailto:a...@ice-sa.com] 
Sent: 07 August 2014 13:47
To: Tomcat Users List
Subject: Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in
windows server 2012

 

Alapan Sur wrote:

 Hi Team,

 

  

 

 We have .Net application consuming tomcat solr3.5 services and 

 deployed on Windows Server 2012. Its is 64 bit machine with 32 GB RAM 

 and Tomcat veriosn is 6 and is installed at :C:\Program Files 

 (x86)\Apache Software Foundation\Tomcat 6.0. During the peak load, 

 the solr sevice stops/unresponsive and it is happening very 

 frequently. We didnt fount any erro logs in windows event viewer but 

 in tomcat logs we got the following exception :

 

 Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:

 ClientAbortException: java.net.SocketException: Software caused 

 connection

 abort: socket write error at


org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:

 369) at 

 org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at

 org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.jav

 a:392) at 

 org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381

 )

 at

 org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStr

 eam.ja

 va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at 

 sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at 

 sun.nio.cs.StreamEncoder.write(Unknown Source) at 

 java.io.OutputStreamWriter.write(Unknown Source) at

 org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at

 org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at

 org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at

 org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at

 org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at

 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at

 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 

 at

 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at

 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 

 at

 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at

 org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 

 at

 org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at

 org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) 

 at

 org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.jav

 a:35)

 at


org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.

 java:343) at


org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:

 265) at

 org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli

 cation

 FilterChain.java:235) at

 org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi

 lterCh

 ain.java:206) at

 org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa

 lve.ja

 va:233) at

 org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa

 lve.ja

 va:191) at

 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja

 va:127

 ) at

 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja

 va:103

 ) at

 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv

 e.java

 :109) at

 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java

 :293)

 at

 org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:

 861)

 at

 org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proces

 s(Http

 11Protocol.java:606) at

 org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489

 ) at java.lang.Thread.run(Unknown Source) Caused by:
java.net.SocketException:

 Software caused connection abort: socket write error at 

 java.net.SocketOutputStream.socketWrite0(Native Method) at 

 java.net.SocketOutputStream.socketWrite(Unknown Source) at 

 java.net.SocketOutputStream.write(Unknown Source) at 

 org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalO

 utputB

 uffer.java:761) at

 org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:448) 

 at

 org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:363) at 

 org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer

 .doWri

 te(InternalOutputBuffer.java:785) at

 org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite

Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[André Warnier]

Alapan Sur wrote:

Hi Andre,

 


Thanks for the quick reply.

 


I have verified the below requested memory related queries as suggested by
you. The Initial memory pool and Maximum memory pool are empty and please
find the attachment for the same.


This list usually strips attachments.
Either paste the info in-line (if it is text), or load the attachments somewhere else and 
post a link.






 


We have checked the heap size with the command : java -XX:+PrintFlagsFinal
-version | findstr /i HeapSize PermSize ThreadStackSize



 


Can you please guide how to increase the java memory pool heap size to 1GB ?



I will, but please read this first, to understand how it works :

http://wiki.apache.org/tomcat/FAQ/Windows#Q11

It will save you time in the end, and will save us further questions which are already 
answered.
It will also explain why the numbers which you are getting with the above command, do not 
represent the same settings as your Tomcat, running as a Windows Service.
As a Windows Service, the JVM which runs Tomcat uses the settings which you see in the GUI 
program tomcat6w.exe (and which are stored in the Windows Registry).
This same program tomcat6w.exe, is also the one which should appear as a little Tomcat 
icon on the task bar of your Windows server.

Thus :
- call up this GUI program
- navigate to the java tab
- set Initial Memory pool and Maximum Memory pool to, for example, 1024 MB
   (or more). Use the same value for both.
- click OK
- then restart the Tomcat Service

 


Cheers,

Alapan

-Original Message-
From: André Warnier [mailto:a...@ice-sa.com] 
Sent: 07 August 2014 13:47

To: Tomcat Users List
Subject: Re: Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in
windows server 2012

 


Alapan Sur wrote:


Hi Team,



 



We have .Net application consuming tomcat solr3.5 services and 


deployed on Windows Server 2012. Its is 64 bit machine with 32 GB RAM 


and Tomcat veriosn is 6 and is installed at :C:\Program Files 


(x86)\Apache Software Foundation\Tomcat 6.0. During the peak load, 


the solr sevice stops/unresponsive and it is happening very 


frequently. We didnt fount any erro logs in windows event viewer but 



in tomcat logs we got the following exception :




Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:


ClientAbortException: java.net.SocketException: Software caused 



connection



abort: socket write error at


org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:

369) at 



org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at



org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.jav


a:392) at 



org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381



)



at



org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStr



eam.ja


va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at 


sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at 


sun.nio.cs.StreamEncoder.write(Unknown Source) at 



java.io.OutputStreamWriter.write(Unknown Source) at



org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at



org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at



org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at



org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at



org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at



org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at


org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 



at



org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at


org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 



at



org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at


org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) 



at



org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at


org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) 



at



org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.jav



a:35)



at


org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.


java:343) at


org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:


265) at



org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appli



cation



FilterChain.java:235) at



org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFi



lterCh



ain.java:206) at



org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperVa



lve.ja



va:233) at



org.apache.catalina.core.StandardContextValve.invoke(StandardContextVa



lve.ja



va:191) at



org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.ja



va:127



) at



org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.ja



va:103



) at



org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValv



e.java

Apache Tomcat 6.0 Tomcat6 service stopped unexpectedly in windows server 2012

[Alapan Sur]

Hi Team,

 

We have .Net application consuming tomcat solr3.5 services and deployed on
Windows Server 2012. Its is 64 bit machine with 32 GB RAM and Tomcat veriosn
is 6 and is installed at :C:\Program Files (x86)\Apache Software
Foundation\Tomcat 6.0. During the peak load, the solr sevice
stops/unresponsive and it is happening very frequently. We didnt fount any
erro logs in windows event viewer but in tomcat logs we got the following
exception :

Aug 06, 2014 10:51:18 AM org.apache.solr.common.SolrException log SEVERE:
ClientAbortException: java.net.SocketException: Software caused connection
abort: socket write error at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
369) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:339) at
org.apache.catalina.connector.OutputBuffer.writeBytes(OutputBuffer.java:392)
at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:381)
at
org.apache.catalina.connector.CoyoteOutputStream.write(CoyoteOutputStream.ja
va:89) at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source) at
sun.nio.cs.StreamEncoder.implWrite(Unknown Source) at
sun.nio.cs.StreamEncoder.write(Unknown Source) at
java.io.OutputStreamWriter.write(Unknown Source) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:55) at
org.apache.solr.common.util.FastWriter.write(FastWriter.java:50) at
org.apache.solr.response.XMLWriter.startTag(XMLWriter.java:269) at
org.apache.solr.response.XMLWriter.writePrim(XMLWriter.java:780) at
org.apache.solr.response.XMLWriter.writeInt(XMLWriter.java:691) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:565) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeNamedList(XMLWriter.java:621) at
org.apache.solr.response.XMLWriter.writeVal(XMLWriter.java:594) at
org.apache.solr.response.XMLWriter.writeResponse(XMLWriter.java:132) at
org.apache.solr.response.XMLResponseWriter.write(XMLResponseWriter.java:35)
at
org.apache.solr.servlet.SolrDispatchFilter.writeResponse(SolrDispatchFilter.
java:343) at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:
265) at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:235) at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206) at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233) at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:191) at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127
) at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103
) at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109) at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http
11Protocol.java:606) at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at
java.lang.Thread.run(Unknown Source) Caused by: java.net.SocketException:
Software caused connection abort: socket write error at
java.net.SocketOutputStream.socketWrite0(Native Method) at
java.net.SocketOutputStream.socketWrite(Unknown Source) at
java.net.SocketOutputStream.write(Unknown Source) at
org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputB
uffer.java:761) at
org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:448) at
org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:363) at
org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWri
te(InternalOutputBuffer.java:785) at
org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFi
lter.java:126) at
org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.j
ava:598) at org.apache.coyote.Response.doWrite(Response.java:560) at
org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:
364) ... 36 more

Aug 06, 2014 10:51:29 AM org.apache.solr.common.SolrException log SEVERE:
java.lang.OutOfMemoryError: Java heap space at
org.apache.lucene.search.ExactPhraseScorer.(ExactPhraseScorer.java:38) at
org.apache.lucene.search.PhraseQuery$PhraseWeight.scorer(PhraseQuery.java:22
7) at
org.apache.lucene.search.BooleanQuery$BooleanWeight.scorer(BooleanQuery.java
:298) at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:577) at
org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:364) at
org.apache.solr.search.SolrIndexSearcher.getDocListAndSetNC(SolrIndexSearche
r.java:1408) at

Re: [SECURITY] CVE-2014-0095 Apache Tomcat denial of service

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

All,

On 5/27/14, 2:41 PM, Christopher Schultz wrote:
 All,
 
 On 5/27/14, 8:46 AM, Mark Thomas wrote:
 CVE-2014-0095 Denial of Service
 
 Severity: Important
 
 Vendor: The Apache Software Foundation
 
 Versions Affected: - Apache Tomcat 8.0.0-RC2 to 8.0.3
 
 Description: A regression was introduced in  revision 1519838
 that caused AJP requests to hang if an explicit content length of
 zero was set on the request. The hanging request consumed a
 request processing thread which could lead to a denial of
 service.
 
 Mitigation: Users of affected versions should apply one of the 
 following mitigations - Upgrade to Apache Tomcat 8.0.5 or later 
 (8.0.4 contains the fix but was not released)
 
 Alternate mitigation:
 
 SetEnvIf Content-Length ^0$ no-jk=1

After a bit of testing, I can see that clients will often send
Content-Length: 0 for a POST request that in fact has no form data
(e.g. all fields are DISABLED or there simply are no child input
elements for a form). Beware, as this may have an adverse impact on
your web application if you have used the above mitigation: Tomcat
will never see these form submissions and clients will likely get a
404 error.

Apologies for the bad advice.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTh28EAAoJEBzwKT+lPKRYrOEQAKkgB6psAONqCqftqjaqLCy2
uY4HgaZpp1znhpju5Lavzib/3eDMewb43ge9FlUEpkkpa1wGazej0k8rlQw1Blsd
9YdHY5/nMhyF09B3qj8pocF+V5TWq0faqsb64XntHArS29Q5/iCFchPSwGP6YlMD
S4iULE61YZj5tkVT+QSJoU/Q0AhdBLyIb2gpvNHF+qrJE+EqvCY7ticuUh0YiwuM
nCmszteNJb9EW+AdC6rbeAxT7QlZcE2krLWNjf75NZOP42+GlRnBi2BuP/v/FSAV
h8XNxFw/361/mGgeZG0olE+Dniv/4BY5JXX7CoSj0oYtn3UzabVY9WoUSqlMoKUB
1NXQRGm3+pVLSKtf1EJCnH2MJP2MRAw4GXTlOUxZLGJqUvcYZ0ih5TJAwKE6f19n
Y+jyfddKbKYTwz2Muxcj4AYFPmQnXsD6eq5R/ziAxBz3rzX8wCYw2eS+O2QGRzy0
52RnFmzDKcIaZTN5LPvGvNcmWOMQEB2+mPwjkBOXv/jb5MEqMdruqGtkeAtjRJ/a
dAPdpJb8DBBIfle68AW4rhsPvIHTOc5a7wlQjyr3VOLztKfaI8dOZD0jM0LN/mwH
3Be7/zBCnNuN4UpzBCZPfQRHKBRReAUfNepIBZA4yOpTqMhk1SJlqlNQ/u2tPFVZ
ihkIIQrRyi5jb3CUrDNq
=aNQ4
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2014-0075 Apache Tomcat denial of service

[Mark Thomas]

CVE-2014-0075 Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
- Apache Tomcat 8.0.0-RC1 to 8.0.3
- Apache Tomcat 7.0.0 to 7.0.52
- Apache Tomcat 6.0.0 to 6.0.39

Description:
It was possible to craft a malformed chunk size as part of a chucked
request that enabled an unlimited amount of data to be streamed to the
server, bypassing the various size limits enforced on a request. This
enabled a denial of service attack.

Mitigation:
Users of affected versions should apply one of the following mitigations
- Upgrade to Apache Tomcat 8.0.5 or later
  (8.0.4 contains the fix but was not released)
- Upgrade to Apache Tomcat 7.0.53 or later
- Upgrade to Apache Tomcat 6.0.41 or later
  (6.0.40 contains the fix but was not released)

Credit:
This issue was reported to the Tomcat security team by David Jorm of the
Red Hat Security Response Team.

References:
[1] http://tomcat.apache.org/security-8.html
[2] http://tomcat.apache.org/security-7.html
[3] http://tomcat.apache.org/security-6.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2014-0095 Apache Tomcat denial of service

[Mark Thomas]

CVE-2014-0095 Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
- Apache Tomcat 8.0.0-RC2 to 8.0.3

Description:
A regression was introduced in  revision 1519838 that caused AJP
requests to hang if an explicit content length of zero was set on the
request. The hanging request consumed a request processing thread which
could lead to a denial of service.

Mitigation:
Users of affected versions should apply one of the following mitigations
- Upgrade to Apache Tomcat 8.0.5 or later
  (8.0.4 contains the fix but was not released)

Credit:
This issue was reported as a possible bug via the Tomcat users mailing
list and the security implications were identified by theTomcat security
team.

References:
[1] http://tomcat.apache.org/security-8.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: [SECURITY] CVE-2014-0095 Apache Tomcat denial of service

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

All,

On 5/27/14, 8:46 AM, Mark Thomas wrote:
 CVE-2014-0095 Denial of Service
 
 Severity: Important
 
 Vendor: The Apache Software Foundation
 
 Versions Affected: - Apache Tomcat 8.0.0-RC2 to 8.0.3
 
 Description: A regression was introduced in  revision 1519838 that
 caused AJP requests to hang if an explicit content length of zero
 was set on the request. The hanging request consumed a request
 processing thread which could lead to a denial of service.
 
 Mitigation: Users of affected versions should apply one of the
 following mitigations - Upgrade to Apache Tomcat 8.0.5 or later 
 (8.0.4 contains the fix but was not released)

Alternate mitigation:

  SetEnvIf Content-Length ^0$ no-jk=1

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJThNxLAAoJEBzwKT+lPKRYUAQP/jG3mbXNsti249+OTkXldsiZ
uRb9daxgArTH3HaOH9YuL/TPbq6cwOhDlHbIRDFzAEZFpyKySbGBkmpkBdeYUTLX
qWWU4IZIGuK8uUysopZ9nohxzi3JghrkE3kSrrUcCGUjmqX1i+MMy/eCdqvOZzxE
PlCvCIkQpyCdyodUlW8LmKiofc9/FUEn/820orm+BzMyMTJgZLbxyGtOKPcJkyQA
ib/Lky2EmLcP1q/RjlI5ACeFubxNVmdu2Vy4KWkjZQLfVqc4AcBcbDy4INYK+RPs
hA2iwctSBul5RXuHcKEJOHDD3FCQJ1u4vchMzmBFj3NnZicf9mbTmk3PXxpT3a3/
HnLxKcQOg0htWSuObMDo/FontTUoid9WJb7jV6Bia1TNEvSgpfjhahcRKIXhvBTw
7+kmQTtdJmL2o/qvlR3ju+zIDMFHCXIHznlhzkcsHQnRWFU4DAEyGQ4z48rXc46U
BPVQAZwEkE0V8VzfpvwRG4hQ5bOHPvRX1dVFzZGnuoHMyvpqEolkeQYHWFmlxjMx
MEi7oaRAz/cbHwyWmtUd8bjiCcJYy5jF0w2DhQFSi7digjuJc2++tk1vp8touKYA
u3nArG5q37uDSk75DAR5tH/lrwtAgpOJe0C9elBygicvK4Al0vCnc3N5G4zFzUJm
WjrJ3SUuRSPSChbHyvz0
=FF7n
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Fwd: Unable to start tomcat as a service.

[akshay jain]

Hey,

I just modified service.bat to set the JRE_HOME. It working really good
now.
Thanks for the help.

Akshay Jain

Fwd: Unable to start tomcat as a service.

[akshay jain]

Hi,

I downloaded *apache-tomcat-7.0.52-windows-x64.zip* from the apache
website.
I am running windows 7 64 bit operating system.

I have setup the file setenv.bat file and apache starts without any problem
when started using startup.bat script.

To run apache as a windows service I did the following steps:
1. Extracted the zip to location C:\tmp
2. Opened command line in the said folder and ran command :
 tomcat7 //IS//
3. Then ran command :
  sc start tomcat7

Following was the output :

C:\tmp\apache-tomcat-7.0.52\bintomcat7.exe //IS//

C:\tmp\apache-tomcat-7.0.52\binsc start tomcat7

SERVICE_NAME: tomcat7
TYPE   : 10  WIN32_OWN_PROCESS
STATE  : 2  START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE,
IGNORES_SHUTDOWN)
WIN32_EXIT_CODE: 0  (0x0)
SERVICE_EXIT_CODE  : 0  (0x0)
CHECKPOINT : 0x0
WAIT_HINT  : 0x7d0
PID: 1848
FLAGS  :

C:\tmp\apache-tomcat-7.0.52\binsc query tomcat7

SERVICE_NAME: tomcat7
TYPE   : 10  WIN32_OWN_PROCESS
STATE  : 1  STOPPED
WIN32_EXIT_CODE: 1066  (0x42a)
SERVICE_EXIT_CODE  : 1  (0x1)
CHECKPOINT : 0x0
WAIT_HINT  : 0x0

C:\tmp\apache-tomcat-7.0.52\bin


Am I missing anything. Please help.


-- 
*Akshay Jain*

Re: Fwd: Unable to start tomcat as a service.

[Christoph P.U. Kukulies]

Am 08.04.2014 11:42, schrieb akshay jain:

Hi,

I downloaded *apache-tomcat-7.0.52-windows-x64.zip* from the apache
website.
I am running windows 7 64 bit operating system.



Are you planning to leave it installed under c:\tmp ?

Did you try to use service.bat install?

What does the System Eventlog say?

--
Christoph Kukulies



I have setup the file setenv.bat file and apache starts without any problem
when started using startup.bat script.

To run apache as a windows service I did the following steps:
1. Extracted the zip to location C:\tmp
2. Opened command line in the said folder and ran command :
  tomcat7 //IS//
3. Then ran command :
  



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Unable to start tomcat as a service.

[Konstantin Kolinko]

2014-04-08 13:42 GMT+04:00 akshay jain uniquejainaks...@gmail.com:
 Hi,

 I downloaded *apache-tomcat-7.0.52-windows-x64.zip* from the apache
 website.
 I am running windows 7 64 bit operating system.

 I have setup the file setenv.bat file and apache starts without any problem
 when started using startup.bat script.

 To run apache as a windows service I did the following steps:
 1. Extracted the zip to location C:\tmp
 2. Opened command line in the said folder and ran command :
  tomcat7 //IS//

That just installs procrun (the service wrapper executable), but DOES
NOT configure it.
Procrun with an empty configuration does not know what Java
application it launches and with what settings. (It does not know that
it belongs to Tomcat, etc.)

There is service.bat that both installs and configures it, but note
that you either need to run the command prompt in as administrator
mode, or use 7.0.53 or later due to
http://issues.apache.org/bugzilla/show_bug.cgi?id=56143


 3. Then ran command :
   sc start tomcat7

 Following was the output :

 C:\tmp\apache-tomcat-7.0.52\bintomcat7.exe //IS//

 C:\tmp\apache-tomcat-7.0.52\binsc start tomcat7

 (...)


Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Unable to start tomcat as a service.

[Jeffrey Janner]

 -Original Message-
 From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
 Sent: Tuesday, April 08, 2014 5:24 AM
 To: Tomcat Users List
 Subject: Re: Unable to start tomcat as a service.
 
 2014-04-08 13:42 GMT+04:00 akshay jain uniquejainaks...@gmail.com:
  Hi,
 
  I downloaded *apache-tomcat-7.0.52-windows-x64.zip* from the apache
  website.
  I am running windows 7 64 bit operating system.
 
  I have setup the file setenv.bat file and apache starts without any
  problem when started using startup.bat script.
 
  To run apache as a windows service I did the following steps:
  1. Extracted the zip to location C:\tmp 2. Opened command line in the
  said folder and ran command :
   tomcat7 //IS//
 
 That just installs procrun (the service wrapper executable), but DOES
 NOT configure it.
 Procrun with an empty configuration does not know what Java application
 it launches and with what settings. (It does not know that it belongs
 to Tomcat, etc.)
 
 There is service.bat that both installs and configures it, but note
 that you either need to run the command prompt in as administrator
 mode, or use 7.0.53 or later due to
 http://issues.apache.org/bugzilla/show_bug.cgi?id=56143
 
 
  3. Then ran command :
sc start tomcat7
 
  Following was the output :
 
  C:\tmp\apache-tomcat-7.0.52\bintomcat7.exe //IS//
 
  C:\tmp\apache-tomcat-7.0.52\binsc start tomcat7
 
  (...)
 
 
 Best regards,
 Konstantin Kolinko
 
You know, it still baffles me why folks still go this route on Windows when 
there's a perfectly good installer package that will take care of all the 
fiddly-bits for you. The only reason I can think of is they are trying to 
install on the GUI-less version of the Server OS, for which the service.bat 
file is a necessity.
Jeff


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Fwd: Unable to start tomcat as a service.

[akshay jain]

On Tue, Apr 8, 2014 at 3:35 PM, Christoph P.U. Kukulies
k...@kukulies.orgwrote:

 Am 08.04.2014 11:42, schrieb akshay jain:

 Hi,

 I downloaded *apache-tomcat-7.0.52-windows-x64.zip* from the apache

 website.
 I am running windows 7 64 bit operating system.



 Are you planning to leave it installed under c:\tmp ?

No. It was for trial only. I am actually writing an installer for my web
application,
which takes the apache zip and extracts it to the Programs folder of
windows.
It also configures a couple of things of apache like port and all.


 Did you try to use service.bat install?

I am able to install it using  service.bat intall command and the service
is running fine.
But I want apache to use a particular jre which my installer would be
copying to the system while installing. I found that setting JRE_HOME
variable
in setenv.bat doesn't work if service.bat install is used to install the
service.


 What does the System Eventlog say?

 --
 Christoph Kukulies



 I have setup the file setenv.bat file and apache starts without any
 problem
 when started using startup.bat script.

 To run apache as a windows service I did the following steps:
 1. Extracted the zip to location C:\tmp
 2. Opened command line in the said folder and ran command :
   tomcat7 //IS//
 3. Then ran command :




 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 
*Akshay Jain*
B-Tech. Computer (*College of Engineering, Pune*)

Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[Neven Cvetkovic]

On Fri, Feb 7, 2014 at 11:59 PM, Jain, Shailesh shj...@suncor.com wrote:

 Hello  Chris,

 Iam  getting very high memory utilization issue in tomcat 7 , which is
 installed on Windows (Vmware)

 Let me know if oyu want logs , and let me know the ftp link where I can
 upload the logs.

 Regards,
 Shailesh Jain
 Suncor MW


Shailesh,

Did you not read Chuck's message to you? He has already suggested what you
should do:

1. Read the http://www.catb.org/~esr/faqs/smart-questions.html

2. Read the mailing list rules:
http://tomcat.apache.org/lists.html#tomcat-users (things under IMPORTANT
section)

3. See how that applies to your case:

a. Do not top post, but rather put your reply text under the text you are
responding to
b. Specify what tomcat version you are using, e.g. 7.0.51
c. Specify what platform you are using (ok you mentioned Windows on VMWare)
d. Specify any other relevant information, what JDK you use
e. Clearly describe your problem, what are the symptoms you observed, how
did you observe them, how would someone replicate your problem? More
specific you are, more likely is that someone on the list will volunteer to
help you troubleshoot your issue.

4. Understand that this mailing list is a community of generous volunteers
that are selflessly sharing their time and experience with you. While it
might be that the primary goal is to resolve your issue, it is more
important that community benefits from your experience and problem solving!
You are probably not the only one with the same issue, and others would
greatly benefit from your sharing how you solved your issue.

5. Be patient. If you cannot wait, there is always an option to seek Tomcat
professional services company, pay for the support, and submit your ticket
to them: http://wiki.apache.org/tomcat/SupportAndTraining

Good luck!

Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[Christoph P.U. Kukulies]

I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it into
c:\program files\Apache_Group\Tomcat_6.0.39 and ran the service.bat 
which established the service.


As system environment variables I have set:

CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3
JAVA_HOME=c:\Program Files\java\jdk1.7.0_51
JRE_HOME=c:\program files\java\jre7

The service does not start at boot and starting it manually gives a 
return code 1.

The event log only shows:
Der Dienst Apache Tomcat 6 wurde mit folgendem dienstspezifischem 
Fehler beendet: Unzulässige Funktion..


starting tomcat6 manually (interactivelym using startup.bat) seems to work:

C:\Program Files\Apache_Group\Tomcat_6.0.39\binstartup
Using CATALINA_BASE:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_HOME:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_TMPDIR: c:\Program Files\Apache_Group\Tomcat_6.0.39\temp
Using JRE_HOME:c:\program files\java\jre7
Using CLASSPATH:   c:\Program 
Files\Apache_Group\Tomcat_6.0.39\bin\bootstra

p.jar
C:\Program Files\Apache_Group\Tomcat_6.0.39\bin


Any clues?


--
Christoph Kukulies


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[André Warnier]

Christoph P.U. Kukulies wrote:

I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it into
c:\program files\Apache_Group\Tomcat_6.0.39 and ran the service.bat 
which established the service.


As system environment variables I have set:

CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3
JAVA_HOME=c:\Program Files\java\jdk1.7.0_51
JRE_HOME=c:\program files\java\jre7

The service does not start at boot and starting it manually gives a 
return code 1.

The event log only shows:
Der Dienst Apache Tomcat 6 wurde mit folgendem dienstspezifischem 
Fehler beendet: Unzulässige Funktion..


starting tomcat6 manually (interactivelym using startup.bat) seems to work:

C:\Program Files\Apache_Group\Tomcat_6.0.39\binstartup
Using CATALINA_BASE:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_HOME:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_TMPDIR: c:\Program Files\Apache_Group\Tomcat_6.0.39\temp
Using JRE_HOME:c:\program files\java\jre7
Using CLASSPATH:   c:\Program 
Files\Apache_Group\Tomcat_6.0.39\bin\bootstra

p.jar
C:\Program Files\Apache_Group\Tomcat_6.0.39\bin


Any clues?



Hi.
This issue seems to be identical to the very recent thread on this list entitled unable 
to start Tomcat through the Windows Services panel.
To avoid long repetitions, could you consult the list archives and see if it provides the 
solution for you too ?

(See : http://tomcat.apache.org/lists.html)

In the meantime, just one thing :
- running Tomcat in a command window uses the BAT files and environment 
variables
- running Tomcat as a Service does not use these at all.
For more details, see : http://wiki.apache.org/tomcat/FAQ/Windows#Q11

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[Christoph P.U. Kukulies]

Thanks for the quick answer. You were faster than I. I had already 
answered myself, but the post bounced since I'm not allowed to post 
HTML. :) I will examine the thread you posted also. Anyway here is my 
finding:


Solved!

Minutes after I posted this, I gave the GUI Windows Installer (32/64) 
32-bit/64-bit%20Windows%20Service%20Installer a try and, lo and 
behold, it worked!


Thanks for listening.

--
Christoph Kukulies

 Am 07.02.2014 10:16, schrieb André Warnier:

Christoph P.U. Kukulies wrote:

I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it into
c:\program files\Apache_Group\Tomcat_6.0.39 and ran the service.bat 
which established the service.


As system environment variables I have set:

CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3
JAVA_HOME=c:\Program Files\java\jdk1.7.0_51
JRE_HOME=c:\program files\java\jre7

The service does not start at boot and starting it manually gives a 
return code 1.

The event log only shows:
Der Dienst Apache Tomcat 6 wurde mit folgendem dienstspezifischem 
Fehler beendet: Unzulässige Funktion..


starting tomcat6 manually (interactivelym using startup.bat) seems to 
work:


C:\Program Files\Apache_Group\Tomcat_6.0.39\binstartup
Using CATALINA_BASE:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_HOME:   c:\Program Files\Apache_Group\Tomcat_6.0.39
Using CATALINA_TMPDIR: c:\Program 
Files\Apache_Group\Tomcat_6.0.39\temp

Using JRE_HOME:c:\program files\java\jre7
Using CLASSPATH:   c:\Program 
Files\Apache_Group\Tomcat_6.0.39\bin\bootstra

p.jar
C:\Program Files\Apache_Group\Tomcat_6.0.39\bin


Any clues?



Hi.
This issue seems to be identical to the very recent thread on this 
list entitled unable to start Tomcat through the Windows Services 
panel.
To avoid long repetitions, could you consult the list archives and see 
if it provides the solution for you too ?

(See : http://tomcat.apache.org/lists.html)

In the meantime, just one thing :
- running Tomcat in a command window uses the BAT files and 
environment variables

- running Tomcat as a Service does not use these at all.
For more details, see : http://wiki.apache.org/tomcat/FAQ/Windows#Q11

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Christoph,

On 2/7/14, 4:01 AM, Christoph P.U. Kukulies wrote:
 I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it
 into c:\program files\Apache_Group\Tomcat_6.0.39 and ran the
 service.bat which established the service.
 
 As system environment variables I have set:
 
 CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3 
 JAVA_HOME=c:\Program Files\java\jdk1.7.0_51 JRE_HOME=c:\program
 files\java\jre7

Note that, when using the Windows Service, the above environment
variables are completely irrelevant.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS9TzsAAoJEBzwKT+lPKRYj5AQAKu35feq5MtnjhlsUClo0Qhk
axY7S+W9IRxB73QifQybU6I+8L2CJpLbIlE0y+xXInkPZM/I0S7xTaIi+S+AyxQw
jwpE4aiTZK/Bu5ECynIiFYTmabANnGZWCyJeYSuVUnAFhNg2oK3cLbBt6b+b1hyt
iDeKBOSiKIxMkVJiIvHZfnMr/sEhetW2KBab7WH+BPPuTRSkpyxiSAy/CHd9TaoP
/NRIZIaHLX4HlpTrjGO3SJ5NkYVNx7fiJlq26ZAJuhOkx7VLudG+aDtowTc02Sqx
fNtUaPMUXphd0V+zVUNMLofsqHtq+43fEQ3OEhVS3SGirixIeMHTMNj2y4jVg0V1
lSZcEr298eehEdnTCT8Yf3cRRLya8oCsP7FlpW3LbguH/logJo1+aUWOnVadY2hf
XDNJ7uugB/sa7rSAANQySZpCNm2GTv1PxEZ9R9J2HOlXGdzeDh8wz4fxF13peDi/
3W3oBkQ2ZYxTPrS7zmGfwNzj2ZUaMBvu68sY3k9+xLQgDUQqTmsH3gx0EGdBELbf
duOxjHgJWUBsx0ZEa/Q+MhPEeQ5ozFANhUeVorF30P63L3aSOJDBlYwQ/zCOMAzW
8aAaP8lyMH3uM/7k0d6Qt5wFlXwzLMxFIzghiQlXu734enB10e6+LCWYja9y+rgB
7DH1LePymVtJZr+KfzgA
=+x1c
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[chris derham]

Christopher

 On 2/7/14, 4:01 AM, Christoph P.U. Kukulies wrote:
 I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it
 into c:\program files\Apache_Group\Tomcat_6.0.39 and ran the
 service.bat which established the service.

 As system environment variables I have set:

 CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3
 JAVA_HOME=c:\Program Files\java\jdk1.7.0_51 JRE_HOME=c:\program
 files\java\jre7

 Note that, when using the Windows Service, the above environment
 variables are completely irrelevant.

For the benefit of the mailing archive, when using the windows
service the variables are not relevant. However when I read
Christoph's post, I think that it is more along the lines of I set
these variables when I ran service.bat, in which case the values at
that time are critical. True they don't have to be system environment
variables - plain environment variables in the console will do.
However it is wrong to say environment variables are completely
irrelevant.

Chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

[Jain, Shailesh]

Hello  Chris,

Iam  getting very high memory utilization issue in tomcat 7 , which is 
installed on Windows (Vmware)

Let me know if oyu want logs , and let me know the ftp link where I can upload 
the logs.

Regards,
Shailesh Jain
Suncor MW

-Original Message-
From: cjder...@gmail.com [mailto:cjder...@gmail.com] On Behalf Of chris derham
Sent: Saturday, February 08, 2014 5:02 AM
To: Tomcat Users List
Subject: Re: Problem starting Tomcat 6.0.39 (64) service under Windows 7/64

Christopher

 On 2/7/14, 4:01 AM, Christoph P.U. Kukulies wrote:
 I downloaded tomcat 6.0.39 (64) from tomcat.apache.org, put it into
 c:\program files\Apache_Group\Tomcat_6.0.39 and ran the service.bat
 which established the service.

 As system environment variables I have set:

 CATALINA_HOME=c:\Program Files\Apache_Group\Tomcat_6.0.3
 JAVA_HOME=c:\Program Files\java\jdk1.7.0_51 JRE_HOME=c:\program
 files\java\jre7

 Note that, when using the Windows Service, the above environment
 variables are completely irrelevant.

For the benefit of the mailing archive, when using the windows service the 
variables are not relevant. However when I read Christoph's post, I think that 
it is more along the lines of I set these variables when I ran service.bat, 
in which case the values at that time are critical. True they don't have to be 
system environment variables - plain environment variables in the console will 
do.
However it is wrong to say environment variables are completely irrelevant.

Chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



This email and its contents are private and confidential, for the sole use of 
the addressees. If you are not an intended recipient, copying, forwarding or 
other distribution of this email or its contents by any means is prohibited. If 
you believe that you received this email in error please notify the original 
sender immediately.

Petro-Canada is a Suncor Energy business.



Ce courriel et son contenu sont privés et confidentiels, et sont destinés à 
l’usage exclusif des destinataires. Si vous n'êtes pas le destinataire prévu, 
toute reproduction, transfert ou autre forme de diffusion de ce courriel ou de 
son contenu par quelque moyen que ce soit est interdit. Si vous croyez avoir 
reçu ce courriel par erreur, veuillez en aviser l'expéditeur original 
immédiatement.

Petro-Canada est une entreprise de Suncor Énergie.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat as Windows service under technical user

[Strobel, Stefan (TS IC)]

Hi everybody,

I would like to run a Tomcat 7.0.47 as Windows service. But that service shall 
not be executed as Administrator but as a local technical user. That user is 
existent, let's call it A. The account is secured with password B.
The question is, how do I install Tomcat as a service (that starts at Windows 
startup) as the technical user A? I tried various commands, but didn't get it 
working.

Any ideas, solutions?

Thanks
Stefan

Re: Tomcat as Windows service under technical user

[Cédric Couralet]

2014/1/27 Strobel, Stefan (TS IC) stefan.stro...@hp.com:
 Hi everybody,

 I would like to run a Tomcat 7.0.47 as Windows service. But that service 
 shall not be executed as Administrator but as a local technical user. That 
 user is existent, let's call it A. The account is secured with password B.
 The question is, how do I install Tomcat as a service (that starts at Windows 
 startup) as the technical user A? I tried various commands, but didn't get it 
 working.

 Any ideas, solutions?


Once the service installed, you can change the User with the sc utility :

sc.exe config serviceName obj= domain\username password= password

 Thanks
 Stefan


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat 7.0.39 windows service setenv not used

[Satyendra Singh]

I have created multiple windows services and for one of the service, i have
-Dcatalina.base=C:\servers\applications\service1
-Dcatalina.home=C:\servers\apache-tomcat-7.0.39

i have C:\servers\applications\service1\bin\setenv.bat where i have

set JAVA_HOME= C:\

Set JAVA_OPTS=-D..

set CATALINA_OPTS=-Xms.

running service1 does not seem to use these values, it only use those that
i can see at  tomcat7w.exe on this service.

any help would be appreciated.

Thank You

Re: Tomcat 7.0.39 windows service setenv not used

[Konstantin Kolinko]

2013/4/25 Satyendra Singh satya...@gmail.com:
 I have created multiple windows services and for one of the service, i have
 -Dcatalina.base=C:\servers\applications\service1
 -Dcatalina.home=C:\servers\apache-tomcat-7.0.39

 i have C:\servers\applications\service1\bin\setenv.bat where i have

 set JAVA_HOME= C:\

 Set JAVA_OPTS=-D..

 set CATALINA_OPTS=-Xms.

 running service1 does not seem to use these values, it only use those that
 i can see at  tomcat7w.exe on this service.



As documented,
[quote]
All the environment variables described here and the setenv script are
used only if you use the standard scripts to launch Tomcat. For example, if
you have installed Tomcat as a service on Windows, the service wrapper
launches Java directly and does not use the script files.
[/quote]

http://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat 7.0.39 windows service setenv not used

[Caldarale, Charles R]

 From: Satyendra Singh [mailto:satya...@gmail.com] 
 Subject: Tomcat 7.0.39 windows service setenv not used

 running service1 does not seem to use these values, it only use those that
 i can see at  tomcat7w.exe on this service.

Services do not use _any_ .bat scripts, nor any environment variables.  All 
properties must be configured in the tomcat7w.exe program associated with each 
service, which then stores the values in the Windows registry for use when the 
service is started.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat 7.0.39 windows service setenv not used

[Satyendra Singh]

Thanks!, so there is no other way to set these except to put in registry
via tomcat7w.exe.


On Wed, Apr 24, 2013 at 4:50 PM, Konstantin Kolinko
knst.koli...@gmail.comwrote:

 2013/4/25 Satyendra Singh satya...@gmail.com:
  I have created multiple windows services and for one of the service, i
 have
  -Dcatalina.base=C:\servers\applications\service1
  -Dcatalina.home=C:\servers\apache-tomcat-7.0.39
 
  i have C:\servers\applications\service1\bin\setenv.bat where i have
 
  set JAVA_HOME= C:\
 
  Set JAVA_OPTS=-D..
 
  set CATALINA_OPTS=-Xms.
 
  running service1 does not seem to use these values, it only use those
 that
  i can see at  tomcat7w.exe on this service.
 


 As documented,
 [quote]
 All the environment variables described here and the setenv script are
 used only if you use the standard scripts to launch Tomcat. For example, if
 you have installed Tomcat as a service on Windows, the service wrapper
 launches Java directly and does not use the script files.
 [/quote]

 http://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service: system tray?

[André Warnier]

Sam Takoy wrote:

Hi,

This is related to the questions that I asked yesterday and got such insightful 
responses (thanks!).

If I am running Tomcat as a Windows service, is it possible to control it 
through a System Tray icon?



Yes, but why don't you try it ?  It is really easy to download and install Tomcat as a 
Service on any Windows workstation, and you'll get the system tray icon automatically.



(By the way, I don't know where to report irrelevant typos in the documentation, but 
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html says system 
try.)

Unless you want to submit patches - which are always welcome but do require some 
preparatory work - probably the best thing to do would be to collect a list of such typos, 
and when you've found a dozen or so, post the list here, with precise references like 
above.  Someone might then pick up the list and go through all of them in one go.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service: system tray?

[Sam Takoy]

Actually, I download the .zip version of Tomcat. I installed the service using 
the service install command. So now I'm wondering, given my current 
situation, how to activate the system tray option.

(OK, I'll be collecting the typos as you suggested.)

Thanks!



 From: André Warnier a...@ice-sa.com
To: Tomcat Users List users@tomcat.apache.org 
Sent: Tuesday, March 12, 2013 4:44 AM
Subject: Re: Tomcat as a service: system tray?
 
Sam Takoy wrote:
 Hi,
 
 This is related to the questions that I asked yesterday and got such 
 insightful responses (thanks!).
 
 If I am running Tomcat as a Windows service, is it possible to control it 
 through a System Tray icon?
 

Yes, but why don't you try it ?  It is really easy to download and install 
Tomcat as a Service on any Windows workstation, and you'll get the system tray 
icon automatically.

 (By the way, I don't know where to report irrelevant typos in the 
 documentation, but 
 http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html says 
 system try.)
 
Unless you want to submit patches - which are always welcome but do require 
some preparatory work - probably the best thing to do would be to collect a 
list of such typos, and when you've found a dozen or so, post the list here, 
with precise references like above.  Someone might then pick up the list and go 
through all of them in one go.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat as a service: system tray?

[Caldarale, Charles R]

 From: Sam Takoy [mailto:sam.ta...@yahoo.com] 
 Subject: Re: Tomcat as a service: system tray?

Don't top-post.

 I installed the service using the service install command. So now I'm 
 wondering, 
 given my current situation, how to activate the system tray option.

Read the doc:

http://commons.apache.org/proper/commons-daemon//procrun.html

Use the //MS or //MR directive.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service: system tray?

[Konstantin Kolinko]

2013/3/12 Sam Takoy sam.ta...@yahoo.com:
 Hi,

 This is related to the questions that I asked yesterday and got such 
 insightful responses (thanks!).

 If I am running Tomcat as a Windows service, is it possible to control it 
 through a System Tray icon?


Tomcat7.exe //MS

http://commons.apache.org/proper/commons-daemon/procrun.html

Tomcat windows installer creates a shortcut for it in Startup group
in Windows menu, but on latest versions of Windows that app should
actually be started in run as administrator mode to be useful.


 (By the way, I don't know where to report irrelevant typos in the 
 documentation, but 
 http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html says 
 system try.)

Online Tomcat 7 documentation is integrated with comments.apache.org
If you scroll to the bottom of that page you can leave a comment
there.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service: system tray?

[André Warnier]

Sam Takoy wrote:

Actually, I download the .zip version of Tomcat. I installed the service using the 
service install command. So now I'm wondering, given my current situation, 
how to activate the system tray option.


Sam, sorry.
I was under the impression that when you install Tomcat as a Windows Service, it 
automatically creates a system tray icon.  But now that I think further about it, I may 
have been confusing this with Apache httpd (which I am sure does install a system tray 
icon).  It has been a while since I last installed a Windows-based Tomcat.

Anyway, if Tomcat doesn't, I apologise and take back my imprudent answer.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service: system tray?

[Howard W. Smith, Jr.]

On Tue, Mar 12, 2013 at 12:42 PM, Sam Takoy sam.ta...@yahoo.com wrote:

 Actually, I download the .zip version of Tomcat. I installed the service
 using the service install command. So now I'm wondering, given my current
 situation, how to activate the system tray option.


Since I'm running Windows Server 2008 (64 bit) as my development server and
Windows Server 2008 R2 (64 bit) as my production server, I decided to give
this a go.

1. Searched google for the following:

tomcat windows service system tray

2. The first search result in the list of search results was the following:

http://tomcat.apache.org/tomcat-7.0-doc/setup.html

3. Went to that page and read the following:


   - *Tray icon*: When Tomcat is run as a service, there will not be any
   tray icon present when Tomcat is running. Note that when choosing to run
   Tomcat at the end of installation, the tray icon will be used even if
   Tomcat was installed as a service.
   - Refer to the Windows Service
HOW-TOhttp://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html
for
   information on how to manage Tomcat as a Windows service.


4. I didn't quite understand the first bulleted item above (at all; i'll be
waiting for someone to respond about my lack of understanding about that
first bulleted item above), so I proceeded to the Windows Service HOW-TO
page, since it was referenced in the second bulleted item

5. On the Windows Service HOW-TO page, it stated the following:

*Tomcat7w monitor application*

*Tomcat7w* is a GUI application for monitoring and configuring Tomcat
services.

The available command line options are:

//ES//Edit service configurationThis is the default operation. It is called
if the no option is provided but the executable is renamed to*
servicenameW.exe*//MS//Monitor servicePut the icon in the system try


6. All of that was so very understandable, that I decided to give it a try,
even though i have 'no' need for a system tray option, since I created a
shortcut to tomcat7w.exe and dragged the shortcut to the Start menu, and
that surely/definitely meets my requirements/needs! :)

7. Opened up a Command Prompt window, did a 'cd' (change directory) to
tomcat7/bin folder, and then did 'tomcat7w.exe //MS//', and immediately,
tomcat7w.exe shortcut/icon showed up in System Tray.

8. I've seen this mentioned on the list so many times, so it was very easy
to refer to documentation while having in mind, what others have
mentioned/recommended on this/tomcat user list. And the little typo 'try'
(instead of 'tray') did not 'prevent' me from following these instructions
in tomcat7 documentation and completing this very simple task to 'put the
icon in the system tray'.

9. Last but not least, I only download and use/install .zip file, too, and
install service via service install tomcat7.

10. please forgive my copy and pasting above from tomcat7 documentation
pages. this email was not sent as plain text, so i don't know how it will
be formatted after i click the Send button. :)

Tomcat as a service: system tray?

[Sam Takoy]

Hi,

This is related to the questions that I asked yesterday and got such insightful 
responses (thanks!).

If I am running Tomcat as a Windows service, is it possible to control it 
through a System Tray icon?

(By the way, I don't know where to report irrelevant typos in the 
documentation, but 
http://tomcat.apache.org/tomcat-7.0-doc/windows-service-howto.html says system 
try.)

Thank you!

Sam

CVE-2012-4534 Apache Tomcat denial of service

[Mark Thomas]

CVE-2012-4534 Apache Tomcat denial of service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
- Tomcat 7.0.0 to 7.0.27
- Tomcat 6.0.0 to 6.0.35

Description:
When using the NIO connector with sendfile and HTTPS enabled, if a
client breaks the connection while reading the response an infinite loop
is entered leading to a denial of service. This was originally reported
as https://issues.apache.org/bugzilla/show_bug.cgi?id=52858.

Mitigation:
Users of affected versions should apply one of the following mitigations:
- Tomcat 7.0.x users should upgrade to 7.0.28 or later
- Tomcat 6.0.x users should upgrade to 6.0.36 or later

Credit:
The security implications of this bug were identified by Arun Neelicattu
of the Red Hat Security Response Team.

References:
http://tomcat.apache.org/security.html
http://tomcat.apache.org/security-7.html
http://tomcat.apache.org/security-6.html

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: CVE-2012-4534 Apache Tomcat denial of service

[Stephen Caine]

Jim,

Check your Tomcat version.

http://localhost:8080/

Stephen

On Dec 4, 2012, at 2:47 PM, Mark Thomas ma...@apache.org wrote:

 CVE-2012-4534 Apache Tomcat denial of service
 
 Severity: Important
 
 Vendor: The Apache Software Foundation
 
 Versions Affected:
 - Tomcat 7.0.0 to 7.0.27
 - Tomcat 6.0.0 to 6.0.35
 
 Description:
 When using the NIO connector with sendfile and HTTPS enabled, if a
 client breaks the connection while reading the response an infinite loop
 is entered leading to a denial of service. This was originally reported
 as https://issues.apache.org/bugzilla/show_bug.cgi?id=52858.
 
 Mitigation:
 Users of affected versions should apply one of the following mitigations:
 - Tomcat 7.0.x users should upgrade to 7.0.28 or later
 - Tomcat 6.0.x users should upgrade to 6.0.36 or later
 
 Credit:
 The security implications of this bug were identified by Arun Neelicattu
 of the Red Hat Security Response Team.
 
 References:
 http://tomcat.apache.org/security.html
 http://tomcat.apache.org/security-7.html
 http://tomcat.apache.org/security-6.html
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Upgrading Tomcat 7.0.29 windows service

[Łukasz Matuszewski]

Welcome,
  i have installed Apache Tomcat 7.0.29 as windows service onto Windows
Server 2008. I want to upgrade Apache Tomcat 7.0.29 to new version 7.0.33.
My question is simple:

Can i just copy all jars from Apache Tomcat 7.0.33 to appriopriate place in
my Apache Tomcat 7.0.29 installation ?

Re: Upgrading Tomcat 7.0.29 windows service

[Mark Thomas]

Łukasz Matuszewski matuszewski.luk...@gmail.com wrote:

Welcome,
  i have installed Apache Tomcat 7.0.29 as windows service onto Windows
Server 2008. I want to upgrade Apache Tomcat 7.0.29 to new version
7.0.33.
My question is simple:

Can i just copy all jars from Apache Tomcat 7.0.33 to appriopriate
place in
my Apache Tomcat 7.0.29 installation ?

It is not recommended but in this case it should work. You need to:
- stop the service
- replace the JARs
- empty the work directory
- apply config file updates (see 
http://tomcat.apache.org/migration-7.html#Upgrading_7.0.x)
- cross your fingers
- start the service

It is one of those, if you know what you are doing you should be OK 
situations. You could also mess things up fairly easily.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

[SECURITY] CVE-2012-2733 Apache Tomcat Denial of Service

[Mark Thomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

CVE-2012-2733 Apache Tomcat Denial of Service

Severity: Important

Vendor: The Apache Software Foundation

Versions Affected:
- - Tomcat 7.0.0 to 7.0.27
- - Tomcat 6.0.0 to 6.0.35

Description:
The checks that limited the permitted size of request headers were
implemented too late in the request parsing process for the HTTP NIO
connector. This enabled a malicious user to trigger an
OutOfMemoryError by sending a single request with very large headers.

Mitigation:
Users of affected versions should apply one of the following mitigations:
- - Tomcat 7.0.x users should upgrade to 7.0.28 or later
- - Tomcat 6.0.x users should upgrade to 6.0.36 or later

Credit:
This issue was identified by Josh Spiewak.

References:
http://tomcat.apache.org/security.html
http://tomcat.apache.org/security-7.html
http://tomcat.apache.org/security-6.html

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQmERaAAoJEBDAHFovYFnnn3MQAOpo2bXRZqp7m6B9Baixivr3
XsahCY6g+lk1G9PZewYirHQ9I8rX0Zte0c+7M+D0jfn5kxDsvOzHGSHxn9IMQkYU
4dRKYrSi75b2RvwxWB1AT0PMDLEk6ttaPLSlA0/JdnPluh54dzVJ+4DPCm1NDfzh
7+UTGSIXESstOo9ogJG8oslXdv5m4aYscMdxrJMEDe3SeHp/vtphY8JfO5F8aGlF
zUVrl/JY8lXl0UH79dMUHoyFbVeLLfv5vyNauSEQZKIa/2y58B9396H4sMlfAXoe
+NcVTo9vb419CQs6I0G4qiN15lZKQk9+bF5hgjTX0GSxi3E88ZJMGuk9rCK8MXr+
XfTTX+YjnRfSjRlrbbd4zejovFUJukVGqkbmXj01Zm42kDmqQnem5lsKWo8IrmCJ
Qe9gQstoqfWUY+gBAJ2msfg3HkJkPvehYYvmVO+pIdI7EemOAKOfgGxSjg947gtd
gf97Z2BOmpWHUH8+erZ3ro8OaOdhHa9ixmDl2EZxZwjngAn59f9P/srBwmPtTsbh
o9GYr3KgU7rfEVOgsZN1aUXvTFjwF50Ju8Yz4D+PagLPnGaraQLIkFc/MdvAFRm6
VP/UxJCRJDdxwjU/cj9jx6/6ZS99JL1ItfYF/v+v/0GCsERcKLphKNzhYpcY888u
gpYL4yE7b4ZmqBUuoK1T
=+jW7
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service question

[Konstantin Kolinko]

2012/10/2 J.V. jvsr...@gmail.com:
 I am attempting to create a windows service using apache commons-daemon to
 create a service from a Java program I have written (a server).

 I know that tomcat uses this lib and successfully, but I am having a number
 of problem completing the task.  I have posted on commons-daemon but no
 response, I believe that project is dead or not supported well.

 I am asking for some help here or to be pointed to the tomcat code that
 creates and starts tomcat as a service as an example.


Which code? Java? C?

There is no such code that starts tomcat as a service. It all
belongs to commons-daemon.

You may want to look at bin/service.bat (see source distributive or
Windows variants of zip binary distributive). That is the script
that installs the service.

Note that tomcatN.exe, tomcatNw.exe are renamed copies of prunsrv.exe,
prunmgr.exe. You may want to rename your ones in the same way. See
commons-daemon docs for details.


 I can install and uninstall the service just OK, but I cannot start it
 either from the command line or through the service manager.

 The error I am getting is:
   The data area passed to a system call is too small.

 There are no messages in any log file anywhere,

No messages at all? Even with debug logging being enabled?

a) The log files are not writeable
b) The process does not start at all

 so I have nothing to go on.
 I have checked all my parameters, and I have nothing too small, nothing too
 large and nothing with special characters.

 If there are any ideas, please let me know, Ideally I would like to get this
 service installed and appear when I do:
 $net start= displays all services running


What version of Windows and what version of commons-daemon are you using?

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as a service question

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

J.V.,

On 10/1/12 7:58 PM, J.V. wrote:
 I am attempting to create a windows service using apache
 commons-daemon to create a service from a Java program I have
 written (a server).

Then you need to ask the commons-daemon folks (see below).

 I know that tomcat uses this lib and successfully, but I am having
 a number of problem completing the task.  I have posted on
 commons-daemon but no response, I believe that project is dead or
 not supported well.

commons-daemon is certainly not dead. You have posted several messages
in the past week and every one of them has been answered (with the
notable exception of Diego Rivera responding with an irritated plea to
other list members to ignore you). I've read your messages from that
list. They all have one problem: you are asking for help but not
giving any information. Asking for any examples for how to do X is
just as good as executing a Google search, except you have to wait for
someone else to do it for you. Do your own Google research.

When you have a specific question, ask on the Apache commons list.

The commons list isn't there to do your work for you, teach you how to
program Java, etc.

commons-daemon includes a service shim for Microsoft Windows: you can
use it to execute just about anything. You (and Tomcat) just happen to
be using it to launch Java Virtual Machine processes. The
commons-daemon list isn't a place to demand answers to questions about
Java. Your tone comes off as ignorant, impatient, angry, and petulant
(cf. Is this project dead?). Everyone on ASF mailing lists are
volunteers and will be happy to help on their own schedule. When you
post, give as much detail as possible, explain what you have tried so
far and where you are getting stuck. Post all error messages if you
have them. Details, details details. Writing a post that just says I
can't get your crappy software to work isn't likely to get you a
decent response.

My advice: check your attitude at the door, *ask* for help instead of
demanding it, and be patient: sometimes it takes a few days for
someone to read a post and reply to it.

Remember: all volunteers.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlBrKE4ACgkQ9CaO5/Lv0PBkHwCeN5V+snYg12uKsw21McM3atyg
+dEAnRtN4UwPEdiVl4sLbdHQLXRwb1mc
=Mpet
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat as a service question

[J.V.]

I am attempting to create a windows service using apache commons-daemon 
to create a service from a Java program I have written (a server).


I know that tomcat uses this lib and successfully, but I am having a 
number of problem completing the task.  I have posted on commons-daemon 
but no response, I believe that project is dead or not supported well.


I am asking for some help here or to be pointed to the tomcat code that 
creates and starts tomcat as a service as an example.


I can install and uninstall the service just OK, but I cannot start it 
either from the command line or through the service manager.


The error I am getting is:
  The data area passed to a system call is too small.

There are no messages in any log file anywhere, so I have nothing to go 
on.  I have checked all my parameters, and I have nothing too small, 
nothing too large and nothing with special characters.


If there are any ideas, please let me know, Ideally I would like to get 
this service installed and appear when I do:

$net start= displays all services running

Thanks


J.V.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as Windows service

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Zbynek,

On 3/7/2011 3:34 AM, Zbynek Vavros wrote:
 Ok I switched to 7.0.8.
 
 Installed using package from
 http://mirror.fubra.com/ftp.apache.org/tomcat/tomcat-7/v7.0.8/bin/apache-tomcat-7.0.8.exe.
 
 Started either directly in services (changed from auto to manual) or using
 that small GUI application(//MS//).
 Yes I had checked Allow service to interact with desktop, unchecked now,
 no console window is diplayed when I start Tomcat at all !
 If I uncheck this how will I get console window?

Wait... do you want the console window or not? First you complained that
the window was showing and now you are complaining that it is not showing.

Or are you complaining that it is showing with no content?

If you want to see some output, check the server logs:

 -Djava.util.logging.config.file=C:\Program Files
 \Apache Software Foundation\Tomcat 7.0\conf\logging.properties

That file will contain the logging configuration. Standard output and
error should be configured to go to a specific file -- check the
settings using tomcat7w.exe.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1+h9AACgkQ9CaO5/Lv0PCsrgCfWyv7F4yxDGHlWWdBwzVEXt/k
QjUAn26ruZE+3cVsroQzg05bc5nLmqnk
=FfWg
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat as Windows service

[Zbynek Vavros]

Hi,

Ok I switched to 7.0.8.

 Install
Installed using package from
http://mirror.fubra.com/ftp.apache.org/tomcat/tomcat-7/v7.0.8/bin/apache-tomcat-7.0.8.exe.

 Start service
Started either directly in services (changed from auto to manual) or using
that small GUI application(//MS//).
Yes I had checked Allow service to interact with desktop, unchecked now,
no console window is diplayed when I start Tomcat at all !
If I uncheck this how will I get console window?

 tomcat7w.exe and Java tab settings
Virtual machine pointing to jdk's jre : C:\Program Files\Java\jdk1.6.0_24
\jre\bin\server\jvm.dll
Java Classpath is at default : C:\Program Files\Apache Software Foundation
\Tomcat 7.0\bin\bootstrap.jar;C:\Program Files\Apache Software Foundation
\Tomcat 7.0\bin\tomcat-juli.jar
Java Options is at default :  -Dcatalina.home=C:\Program Files\Apache
Software Foundation\Tomcat 7.0
-Dcatalina.base=C:\Program Files\Apache Software
Foundation\Tomcat 7.0
-Djava.endorsed.dirs=C:\Program Files\Apache
Software Foundation\Tomcat 7.0\endorsed
-Djava.io.tmpdir=C:\Program Files\Apache Software
Foundation\Tomcat 7.0\temp

-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=C:\Program Files
\Apache Software Foundation\Tomcat 7.0\conf\logging.properties


I tried 6.0.32 with the same result.

Thanks a lot for help
Zbynek

   
 Kind Regards / Mit
 freundlichen Grüßen / 
 Üdvözlettel / S   
 pozdravem:
   
   
 Zbynek VAVROS (Embedded
 Development image moved
to file:
   pic32194.gif)
   
 Delivery Centre  616 00, Brno 
  Central Europe  Technicka 21 
Brno SITE Czech Republic   
   
 (Embedded image moved to  
   file: pic14574.gif)Phone: 420-53341- x6283  
  Mobile:  
  E-mail: zbynek_vav...@cz.ibm.com 
   
   
   
   
   IBM Global Services 
  Delivery Center Czech
 Republic, s.r.o.  
   Registered address: 
 Brno, Technicka 2995/21,  
 Zip code: 61600, Company  
   ID: 26244535
  Entered in the   
   Commercial Register 
maintained by the  
  Regional Court in Brno   
  (Part C, Entry 39922)
   
   IBM Global Services 
  Delivery Center Czech
 Republic, s.r.o.  
  Sídlo: Brno, Technická   
  2995/21, PSČ 61600 IČ:   
 26244535  
   Zapsaná v obchodním 
rejstříku, vedeném   
  Krajským soudem v Brně   
  oddíl C, vlozka 39922  
   





|
| From

Tomcat as Windows service

[Zbynek Vavros]

Hi,

Im starting to be desperate.
I installed Tomcat as service and when I start it console is displayed.
BUT the console is empty, not  a single letter is written and I can see in
logs
that there definitely is an output.
Using Tomcat 7.0.2 on Windows XP SP3 but experiencing same behavior on
Windows Server 2008.
I must have missed something or I dont know.

Thx
Zbynek


   
 Kind Regards / Mit
 freundlichen Grüßen / 
 Üdvözlettel / S   
 pozdravem:
   
   
 Zbynek VAVROS (Embedded
 Development image moved
to file:
   pic18602.gif)
   
 Delivery Centre  616 00, Brno 
  Central Europe  Technicka 21 
Brno SITE Czech Republic   
   
 (Embedded image moved to  
   file: pic20561.gif)Phone: 420-53341- x6283  
  Mobile:  
  E-mail: zbynek_vav...@cz.ibm.com 
   
   
   
   
   IBM Global Services 
  Delivery Center Czech
 Republic, s.r.o.  
   Registered address: 
 Brno, Technicka 2995/21,  
 Zip code: 61600, Company  
   ID: 26244535
  Entered in the   
   Commercial Register 
maintained by the  
  Regional Court in Brno   
  (Part C, Entry 39922)
   
   IBM Global Services 
  Delivery Center Czech
 Republic, s.r.o.  
  Sídlo: Brno, Technická   
  2995/21, PSČ 61600 IČ:   
 26244535  
   Zapsaná v obchodním 
rejstříku, vedeném   
  Krajským soudem v Brně   
  oddíl C, vlozka 39922  
   



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: Tomcat as Windows service

[Caldarale, Charles R]

 From: Zbynek Vavros [mailto:zbynek_vav...@cz.ibm.com] 
 Subject: Tomcat as Windows service

 I installed Tomcat as service

Be specific: exactly what did you do?

 when I start it console is displayed.

Be specific: exactly how are you starting it?

If you run tomcat7w.exe and look at the Logon tab, is Allow service to 
interact with desktop checked?  If so, clear it - it should never be set.

Also with tomcat7w.exe, what are the settings under the Java tab?

 Using Tomcat 7.0.2

Please update to a stable, rather than beta, version.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Tomcat as Windows service - I can't set more than 768 Mb of memory

[icarrara]

I manually installed Tomcat 6.0.29 on Windows Server 2003 R2 and all was
fine.

Then I use the service install Alfresco command to install Tomcat as
Windows service.

Using the tomcat6w //ES//Alfresco command I'll set up the
-XX:MaxPermSize=256m in the Java Options and 1024 in the Initial and
Maximum memory pool ... The problem is that I can't set more than 768 Mb of
memory because with values great than 768 the service don't starts. 

I get the error Could not reserve enough space for object heap.  I'm using
JDK 1.6.0_22u and the machine have 4 Gbyte of phisical RAM...

Please, could you help me ?

Thank you in advance!

Ivano
-- 
View this message in context: 
http://old.nabble.com/Tomcat-as-Windows-service---I-can%27t-set-more-than-768-Mb-of-memory-tp30164308p30164308.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: Tomcat as Windows service - I can't set more than 768 Mb of memory

[Rainer Jung]

On 08.11.2010 22:34, icarrara wrote:


I manually installed Tomcat 6.0.29 on Windows Server 2003 R2 and all was
fine.

Then I use the service install Alfresco command to install Tomcat as
Windows service.

Using the tomcat6w //ES//Alfresco command I'll set up the
-XX:MaxPermSize=256m in the Java Options and 1024 in the Initial and
Maximum memory pool ... The problem is that I can't set more than 768 Mb of
memory because with values great than 768 the service don't starts.

I get the error Could not reserve enough space for object heap.  I'm using
JDK 1.6.0_22u and the machine have 4 Gbyte of phisical RAM...


What other startup flags are configured? E.g. is there a stack size set? 
How do your connector configurations in server.xml look like?


Thread stacks, Java heap and perm and some other native memory parts all 
have to fit nto 2GB if it is 32Bits Windows/Java.


Regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org