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
> 
> >
> >
> 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.
>

+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
> 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: 

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: Accessing the manager application in a new Tomcat 8.5 install

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Joel,

On 1/7/19 17:07, Joel Saunders wrote:
> What exactly does that mean?   I’m sorry but I really don’t know

John Larson, in another reply to this thread, suggested that you
change your webapps/manager/META-INF/context.xml file to remove the
IP-based restriction on who can connect to the manager.

I'm suggesting that you undo any changes that you might have made
unless you really understand the security implications.

Hope that helps,
- -chris

>> On Jan 7, 2019, at 5:06 PM, Christopher Schultz
>>  wrote:
>> 
> Joel,
> 
 On 1/7/19 14:47, Joel Saunders wrote: Did that this AM and
 thought that I had it.. until I didn't...
> 
> Don't forget to re-instate your RemoteIPValve constraints.
> 
> -chris
> 
 -Original Message- From: Mark Thomas 
 [mailto:ma...@apache.org] Sent: Monday, January 07, 2019 2:45
 PM To: users@tomcat.apache.org Subject: Re: Accessing the
 manager application in a new Tomcat 8.5 install
 
> On 07/01/2019 19:24, Joel Saunders wrote: I've spent about
> 2 weeks on and off (I have other projects) and still cant
> log in to the Tomcat 8.5 manager app.
> 
> I get the signon box, enter my credentials from the 
> tomcat-users.xml file and the signon box is promptly
> returned.
> 
> 
> 
> I read the docs regarding the required roles, and the valve
> that restricts access other than from localhost, restarted
> each time with no success.   I haven't figured out how to
> set debug on to hopefully give me more info on why it's
> failing.
> 
> 
> 
> Does anyone have specific steps that would need to be
> followed in order to allow a user to access the manager app
> after a new install?
> 
> 
> 
> We don't use this that much so it's very frustrating to say
> the least. Once I get the manager access handled, then I'll
> be able to deploy the application that tomcat8 was required
> for (I know that you can use commands vs the gui to do
> that, but we're used to using the gui so that's why we need
> it to work.
> 
> 
> 
> Any comments/suggestions would be greatly appreciated as
> I've already wasted way too much time trying to address
> such a simple request.
 
 Have you removed the XMl comment markers in
 tomcat-users.xml?
 
 Mark
 
 
> 
> 
> 
> Thanks.
> 
> 
> 
> Joel
> 
> 
> 
> *JOEL SAUNDERS*
> 
> * *
> 
> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
> 
> W: 518-652-4089| C: 518-265-0771 joel.saund...@zones.com 
>  | zones.com 
> __
> 
> 
> 
> 
> 
> 
> 
m_nfrastructure_=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI&
> r=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGEO5
Xm
>
> 
2kuSWU7iDCF1DkfrJQ4=wMauS01ow4RKUwKZgpvwPTItFe-ZT6kRS0lq19Zlz6Q=> tps://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_co
mp
>
> 
any_nfrastructure_=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvCl
> I=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGE
O5
>
> 
Xm2kuSWU7iDCF1DkfrJQ4=TzL8ew5LSoyz0u4kti1Le0PTI8QKleWhxwTsWJMhJ8M=>
> 
> 
astructure=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI=WG-p
> l0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGEO5Xm2kuS
WU
>
> 
7iDCF1DkfrJQ4=FBn5U3iNIQZ7Gu4PgUqw-d0Y0bD-skBPyrxeNbLUqYE=>
> 
> 
_user_nfrastructure1992=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KN
> xwvClI=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZx
Iu
>
> 
eGEO5Xm2kuSWU7iDCF1DkfrJQ4=V9E9P0OdLMR6zx59BCy9KkW9PhUczyPhFTGmPBS7xdE
> =>
> 
> 
> 
> 
 
 
 ---
- --


>
 
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
 
>> 
>> -
>>
>> 
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 

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

Re: Accessing the manager application in a new Tomcat 8.5 install

[Joel Saunders]

What exactly does that mean?   I’m sorry but I really don’t know

Sent from my iPhone

> On Jan 7, 2019, at 5:06 PM, Christopher Schultz 
>  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Joel,
> 
>> On 1/7/19 14:47, Joel Saunders wrote:
>> Did that this AM and thought that I had it.. until I didn't...
> 
> Don't forget to re-instate your RemoteIPValve constraints.
> 
> - -chris
> 
>> -Original Message- From: Mark Thomas
>> [mailto:ma...@apache.org] Sent: Monday, January 07, 2019 2:45 PM 
>> To: users@tomcat.apache.org Subject: Re: Accessing the manager
>> application in a new Tomcat 8.5 install
>> 
>>> On 07/01/2019 19:24, Joel Saunders wrote:
>>> I've spent about 2 weeks on and off (I have other projects) and
>>> still cant log in to the Tomcat 8.5 manager app.
>>> 
>>> I get the signon box, enter my credentials from the
>>> tomcat-users.xml file and the signon box is promptly returned.
>>> 
>>> 
>>> 
>>> I read the docs regarding the required roles, and the valve that 
>>> restricts access other than from localhost, restarted each time
>>> with no success.   I haven't figured out how to set debug on to
>>> hopefully give me more info on why it's failing.
>>> 
>>> 
>>> 
>>> Does anyone have specific steps that would need to be followed in
>>> order to allow a user to access the manager app after a new
>>> install?
>>> 
>>> 
>>> 
>>> We don't use this that much so it's very frustrating to say the
>>> least. Once I get the manager access handled, then I'll be able
>>> to deploy the application that tomcat8 was required for (I know
>>> that you can use commands vs the gui to do that, but we're used
>>> to using the gui so that's why we need it to work.
>>> 
>>> 
>>> 
>>> Any comments/suggestions would be greatly appreciated as I've
>>> already wasted way too much time trying to address such a simple
>>> request.
>> 
>> Have you removed the XMl comment markers in tomcat-users.xml?
>> 
>> Mark
>> 
>> 
>>> 
>>> 
>>> 
>>> Thanks.
>>> 
>>> 
>>> 
>>> Joel
>>> 
>>> 
>>> 
>>> *JOEL SAUNDERS*
>>> 
>>> * *
>>> 
>>> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
>>> 
>>> W: 518-652-4089| C: 518-265-0771 joel.saund...@zones.com
>>>  | zones.com 
>>> __
>>> 
>>> 
>>> 
>>> 
>>> 
>>>  m_nfrastructure_=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI&
> r=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGEO5Xm
> 2kuSWU7iDCF1DkfrJQ4=wMauS01ow4RKUwKZgpvwPTItFe-ZT6kRS0lq19Zlz6Q=> tps://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_comp
> any_nfrastructure_=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvCl
> I=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGEO5
> Xm2kuSWU7iDCF1DkfrJQ4=TzL8ew5LSoyz0u4kti1Le0PTI8QKleWhxwTsWJMhJ8M=>
>>>  astructure=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KNxwvClI=WG-p
> l0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIueGEO5Xm2kuSWU
> 7iDCF1DkfrJQ4=FBn5U3iNIQZ7Gu4PgUqw-d0Y0bD-skBPyrxeNbLUqYE=>
>>>  _user_nfrastructure1992=DwID-g=bFSfV3JDZVFjkVdrOg1Bnsgwku-x_EGNRi2KN
> xwvClI=WG-pl0WpwyPk-r6oNnUhsoAUBdVNpC8ryokTG8RkffA=jr4yxkk-QhRZeZxIu
> eGEO5Xm2kuSWU7iDCF1DkfrJQ4=V9E9P0OdLMR6zx59BCy9KkW9PhUczyPhFTGmPBS7xdE
> =>
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>> -
>> 
>> 
> 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/
> 
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwzzUAACgkQHPApP6U8
> pFgA7g/8CsO5Koy7AbldrK0m3nTsf1yWVHGXh2VXpRG8sDsmfn7xynofc8NHg/yA
> b2aW17XaP13W2SAYFOBWr6Yp78DQgs/FdHvRvbHzmm4Kz5jKl6UdjkNg3KfFGIgP
> 2d17dacYjeqxwr90IfZOwK9HAvOyEP5ExrI/yhTMVIW76ebVLJXUEWxIvE+Uy6rT
> S2K/IJ2dzQUhCftJOrefEzn9b6HF/dNbhAEAfStIzWsDKZUyW/yk2WzSn6AQY93H
> 94ZuvR42L2okXgWffK2yKB/Po+4agIdwagpHYp9YtLHtmLhFNsjq/Y9CG1G74gXz
> zgmoNOGvfBdMXcweovRgNOkgdcsxTrYthSTCKxzerzr22aJF0qAh2a/fFzAgaMP6
> NRo0ONUXdn/hGq45byiW0GguW7mwxyqm0tWUomNsX1yEIIVCAn7nQFPSGqOYQqat
> vL55L/Nzz4H7RDBdSMhk95IevWCC3Le1XL++EEJSLzY0DGK1sCdlnMaabZLIxy+G
> WIMq2qnb7bI5jUyp+nH+1pUlfTPaQoO5nlC08YeAGl5j4IPy9SfKjA0PCnnQJDpF
> zwKcCimQlSK66g3mCweUZCzW04N6uFTHdgcH+TUIDyumAwya34M/I5zbhz45AFgo
> 2KI+xTPmwQWwmnTjvZpjz3VtaTL2oDZL8z1WLl5E/OPJTDio0mQ=
> =Rzsv
> -END PGP SIGNATURE-
> 
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For 

Re: Accessing the manager application in a new Tomcat 8.5 install

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Joel,

On 1/7/19 14:47, Joel Saunders wrote:
> Did that this AM and thought that I had it.. until I didn't...

Don't forget to re-instate your RemoteIPValve constraints.

- -chris

> -Original Message- From: Mark Thomas
> [mailto:ma...@apache.org] Sent: Monday, January 07, 2019 2:45 PM 
> To: users@tomcat.apache.org Subject: Re: Accessing the manager
> application in a new Tomcat 8.5 install
> 
> On 07/01/2019 19:24, Joel Saunders wrote:
>> I've spent about 2 weeks on and off (I have other projects) and
>> still cant log in to the Tomcat 8.5 manager app.
>> 
>> I get the signon box, enter my credentials from the
>> tomcat-users.xml file and the signon box is promptly returned.
>> 
>> 
>> 
>> I read the docs regarding the required roles, and the valve that 
>> restricts access other than from localhost, restarted each time
>> with no success.   I haven't figured out how to set debug on to
>> hopefully give me more info on why it's failing.
>> 
>> 
>> 
>> Does anyone have specific steps that would need to be followed in
>> order to allow a user to access the manager app after a new
>> install?
>> 
>> 
>> 
>> We don't use this that much so it's very frustrating to say the
>> least. Once I get the manager access handled, then I'll be able
>> to deploy the application that tomcat8 was required for (I know
>> that you can use commands vs the gui to do that, but we're used
>> to using the gui so that's why we need it to work.
>> 
>> 
>> 
>> Any comments/suggestions would be greatly appreciated as I've
>> already wasted way too much time trying to address such a simple
>> request.
> 
> Have you removed the XMl comment markers in tomcat-users.xml?
> 
> Mark
> 
> 
>> 
>> 
>> 
>> Thanks.
>> 
>> 
>> 
>> Joel
>> 
>> 
>> 
>> *JOEL SAUNDERS*
>> 
>> * *
>> 
>> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
>> 
>> W: 518-652-4089| C: 518-265-0771 joel.saund...@zones.com
>>  | zones.com 
>> __
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
> 
> 
> -
>
> 
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/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwzzUAACgkQHPApP6U8
pFgA7g/8CsO5Koy7AbldrK0m3nTsf1yWVHGXh2VXpRG8sDsmfn7xynofc8NHg/yA
b2aW17XaP13W2SAYFOBWr6Yp78DQgs/FdHvRvbHzmm4Kz5jKl6UdjkNg3KfFGIgP
2d17dacYjeqxwr90IfZOwK9HAvOyEP5ExrI/yhTMVIW76ebVLJXUEWxIvE+Uy6rT
S2K/IJ2dzQUhCftJOrefEzn9b6HF/dNbhAEAfStIzWsDKZUyW/yk2WzSn6AQY93H
94ZuvR42L2okXgWffK2yKB/Po+4agIdwagpHYp9YtLHtmLhFNsjq/Y9CG1G74gXz
zgmoNOGvfBdMXcweovRgNOkgdcsxTrYthSTCKxzerzr22aJF0qAh2a/fFzAgaMP6
NRo0ONUXdn/hGq45byiW0GguW7mwxyqm0tWUomNsX1yEIIVCAn7nQFPSGqOYQqat
vL55L/Nzz4H7RDBdSMhk95IevWCC3Le1XL++EEJSLzY0DGK1sCdlnMaabZLIxy+G
WIMq2qnb7bI5jUyp+nH+1pUlfTPaQoO5nlC08YeAGl5j4IPy9SfKjA0PCnnQJDpF
zwKcCimQlSK66g3mCweUZCzW04N6uFTHdgcH+TUIDyumAwya34M/I5zbhz45AFgo
2KI+xTPmwQWwmnTjvZpjz3VtaTL2oDZL8z1WLl5E/OPJTDio0mQ=
=Rzsv
-END PGP SIGNATURE-

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

Re: Parsing of multi part content

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Saurav,

On 1/7/19 13:13, Saurav Sarkar wrote:
> Thanks a lot Chris for the reply.
> 
> I think even if i parse the request myself i have to always load 
> the content in memory/disk.
> 
> Because in order to extract the file uploaded from the request , i
>  have to go through the whole request stream and trim down the 
> boundaries.

Exactly. Neither you *nor Tomcat* really have many options, here.

- -chris


> On Thu, Jan 3, 2019 at 3:20 AM Christopher Schultz < 
> ch...@christopherschultz.net> wrote:
> 
> Saurav,
> 
> On 1/2/19 12:20, Saurav Sarkar wrote:
 Hi All,
 
 This is regarding the reading of multi part content in java 
 server side.
 
 ServletRequest has an API getParts() API for reading the 
 parts of a multi part request 
 https://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServlet
Req
>

 
uest.html#getParts()
> 


>
>
> 
.
 
 It has part.getInputStream which can be used to read the 
 content of a specific part.
 
 Tomcat also provides an implementation for this API.
 
 But this API  parses the multi part content and keeps it in 
 memory. If the size increase then the content can be 
 offloaded to disk.
 
 Why does the getPart API or any multi part parsing need to 
 load the content in memory ? Why can't direct streaming of 
 content happen ? Loading the content in memory and 
 reading/writing to disk brings extra cost. This will be 
 specially costly when large files are getting uploaded.
> 
> True. You can always limit the part-size or request-size, but you 
> can't stream huge uploads if you want to use getParts().
> 
 Is there no way where at least the file content loading
 could be avoided ?
> 
> Yes, there is a way.
> 
> Instead of calling HttpServletRequest.getParameter* or 
> HttpServletRequest.getPart*, you can call 
> HttpServletRequest.getInputStream and parse everything yourself.
> 
 It may be not be a very specific question for tomcat but more
 applicable to any servlet container.
> 
> Correct, this is applicable to any servlet container.
> 
> The multipart code in Tomcat parses everything to memory/disk at 
> once because servlet code needs to be able to call 
> HttpServletRequest.getParameter(String) in any order regardless of
>  what how the request data is actually ordered. Also, getParts must
>  return before the calling code can actually do anything with the 
> data. There is no "register a stream handler for a multipart 
> request part called 'foo'" or anything like that.
> 
> If you want those semantics, you'll have to parse the request 
> yourself.
> 
> -chris
>> 
>> -
>>
>>
>> 
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/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwzzNUACgkQHPApP6U8
pFgNJg//VoweS5Ve1jgMYi4e2yekWL4lexpAkm1Apu+mwOku93c7oQ28RW1x/h54
ShuQbh+smt5DWPoM3Qu9F/PvKEiNcLyRxLyhmf5c/SRSRoLrBrZt66Oq+SKmekrb
wugGyLOP6ZrhULXJOlNqIa/oh5pBA/GU7cEGTjcLdCzz3i58c+0H/XyO7EG5QjvS
rX6umdKNp86bMgSjw9wL/KNCB7KbLguhPxIo93S6AjRNtbXWxThuZGlLb6x6fjpK
J+nsnuwhv8nxrpCawdq+hKABMFL9PsIq28Yf5MZ7gLzgCr/iYibDXDJpF9puBe5r
xKOhAvhTy7yK84C44QzkRCBzqTp2+d/0xL1rQCyMU7wq4fDZm8ZKd8QsPOzNd0QG
Sfb+/HMu00UlZTcOhNmIdPMrGwuDT2cwRlgWZGBJAnA7gJNzoJ1ZY/F+62UJPin7
UrFH5IMP0Gw3cJ5PEHH/pi3nTTb+FCtMobb3AogPvfXE+jDVb3vC1Shg52UdvX2h
I63h8+l/UHhcy+ldP+9ov2EeoBgUfn+7feUKTbuyefmPjsKZdj8xeRC4CoWG6UT3
xDEMSdZ/EhkGRmPhzBcPPlPHR9vBjyY26V7Sk0AapqLSVRxBbG4s4HeGRJxdNHj8
r1vyaawX66/6ACzL3pp7XqHdshTRoxR8nZuBuBSq3a7LQDjO1Ps=
=IapN
-END PGP SIGNATURE-

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

Re: Tomcat SSL - unsupported protocol or cipher suit error

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Sameer,

On 1/7/19 14:27, Sameer Umbrajkar wrote:
> Dear Chris,
> 
> Could you help me out with the connector sample with sslhostconfig.
> I have mentioned the connector details in my previous email.

Try looking at the documentation reference I put into my last post and
trying to build your own. If it does not work or causes an error, post
back here for help.

- -chris

> On Mon 7 Jan, 2019, 12:22 AM Christopher Schultz < 
> ch...@christopherschultz.net wrote:
> 
> Sameer,
> 
> On 1/6/19 13:40, Sameer Umbrajkar wrote:
 Dear John & Raj,
 
 *My JVM version is 8.1.015 and Tomcat version is 8.5.13*
 Please see the version details below - 
 ===
===
>
 

 
 
> E:\BOE\tomcat\bin>version
 Using CATALINA_BASE:   "E:\BOE\tomcat" Using CATALINA_HOME: 
 "E:\BOE\tomcat" Using CATALINA_TMPDIR: "E:\BOE\tomcat\temp"
 Using JRE_HOME:"E:\BOE\SAP BusinessObjects Enterprise
 XI 4.0\win64_x64\sapjvm\" Using CLASSPATH: 
 "E:\BOE\tomcat\bin\bootstrap.jar;E:\BOE\tomcat\bin\tomcat-juli.jar"


>
 
Server version: Apache Tomcat/8.5.13
 Server built:   Mar 27 2017 14:25:04 UTC Server number:
 8.5.13.0 OS Name:Windows NT (unknown) OS Version:
 10.0 Architecture:   amd64 JVM Version:8.1.015 JVM
 Vendor: SAP AG E:\BOE\tomcat\bin> 
 ===
===
>
 
=
 
 As suggested I added below parameters in Java Option of
 Tomcat configuration still facing the same error related to
 TLS protocol and ciphers 
 ===
===
>
 
=
 
 
> -Dhttps.protocols=TLSv1.2
 -Dhttps.cipherSuites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 
 ===
===
>
 
=
 
 
> As requested, please find the HTTPS connector details below from
> server. xml
 ===
===
>
 
=
 
 
> >>> port="8443" maxThreads="200" scheme="https" secure="true" 
 SSLEnabled="true" keystoreFile="E:\SSL\.keystore" 
 keystorePass="Am1@k123" clientAuth="false"
 sslProtocol="TLS"/>
> 
> It would be better to use the more modern configuration which
> includes  elements within your 
> elements.
> 
> http://tomcat.apache.org/tomcat-8.5-doc/config/http.html#SSL_Support
>
>  -chris
>> 
>> -
>>
>> 
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/

iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwzzJQACgkQHPApP6U8
pFjmTQ/8DpcJ4/a+MIWCn4g13ynXk/jyA9Y25fwUOOLNSppH2bzJtu2fQSQ7CTdf
y79AqpGxSMayDKoASHX3+lafKC2bcsQhD+nm55UmJGfe+OmlCoNUGkseDcars6SW
iZuUdDqnuOUFqO9LagNxP7bfzThx+LwuwNo3EsNZ7tsV5SuKzRHxJPo1nPUJZXTX
4akzIemc+KyPASF5FJrbVyvajczy2sQjRll6Mts3N5pxpMY7zSihxxYN8zb8m2pT
iUKisipS3vfJaZI6cndCirXhHak8J+oGFdYeL8eNLWf04GhRfnc3pqay8uIjQ20z
a0H29WNxyx9qXEvxOk5lI2mjEMHMzdSZd1DBYPj7/4SA74jAr4+4RBEmm4rt4xQA
fPBcpTO2/K9juSPAXYfFG72YvAyYQMb8K8GB+MNZ/uWZidIB+T27tRf/d46IOvdK
LKMtGs4wJ2/RQmxkOcIjwPUry4N/gv9osRmWtXRvSozQrq6xNSGByzGeAKtRX9Sd
3s6h5abBwtxb+X5DGGss28F/dugQTVoFJxgUUzVak2P3kzlbE/zT9fq4C6slGTbZ
lCg4uqdrEQetlpd7hIa4dKetjhvIfbGdykfzWZkYD0KjKqwH6bEidMrO5dvrYxdj
WrAdz4vSmwMCHq9/SfNlWGTHDutmClnCcxlqZN18epZMfkGrrbg=
=rY0N
-END PGP SIGNATURE-

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

RE: Accessing the manager application in a new Tomcat 8.5 install

[Joel Saunders]

Did that this AM and thought that I had it.. until I didn't...

Thanks...


-Original Message-
From: Mark Thomas [mailto:ma...@apache.org] 
Sent: Monday, January 07, 2019 2:45 PM
To: users@tomcat.apache.org
Subject: Re: Accessing the manager application in a new Tomcat 8.5 install

On 07/01/2019 19:24, Joel Saunders wrote:
> I've spent about 2 weeks on and off (I have other projects) and still
> cant log in to the Tomcat 8.5 manager app.
> 
> I get the signon box, enter my credentials from the tomcat-users.xml
> file and the signon box is promptly returned.
> 
>  
> 
> I read the docs regarding the required roles, and the valve that
> restricts access other than from localhost, restarted each time with no
> success.   I haven't figured out how to set debug on to hopefully give
> me more info on why it's failing.
> 
>  
> 
> Does anyone have specific steps that would need to be followed in order
> to allow a user to access the manager app after a new install?
> 
>  
> 
> We don't use this that much so it's very frustrating to say the least.  
> Once I get the manager access handled, then I'll be able to deploy the
> application that tomcat8 was required for (I know that you can use
> commands vs the gui to do that, but we're used to using the gui so
> that's why we need it to work.
> 
>  
> 
> Any comments/suggestions would be greatly appreciated as I've already
> wasted way too much time trying to address such a simple request.

Have you removed the XMl comment markers in tomcat-users.xml?

Mark


> 
>  
> 
> Thanks.
> 
>  
> 
> Joel
> 
>  
> 
> *JOEL SAUNDERS*
> 
> * *
> 
> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
> 
> W: 518-652-4089| C: 518-265-0771
> joel.saund...@zones.com  | zones.com
> __
> 
> 
> 
>  
> 
> 
>  
> 
>  
> 
>  
> 
>  
> 


-
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: Accessing the manager application in a new Tomcat 8.5 install

[Mark Thomas]

On 07/01/2019 19:24, Joel Saunders wrote:
> I’ve spent about 2 weeks on and off (I have other projects) and still
> cant log in to the Tomcat 8.5 manager app.
> 
> I get the signon box, enter my credentials from the tomcat-users.xml
> file and the signon box is promptly returned.
> 
>  
> 
> I read the docs regarding the required roles, and the valve that
> restricts access other than from localhost, restarted each time with no
> success.   I haven’t figured out how to set debug on to hopefully give
> me more info on why it’s failing.
> 
>  
> 
> Does anyone have specific steps that would need to be followed in order
> to allow a user to access the manager app after a new install?
> 
>  
> 
> We don’t use this that much so it’s very frustrating to say the least.  
> Once I get the manager access handled, then I’ll be able to deploy the
> application that tomcat8 was required for (I know that you can use
> commands vs the gui to do that, but we’re used to using the gui so
> that’s why we need it to work.
> 
>  
> 
> Any comments/suggestions would be greatly appreciated as I’ve already
> wasted way too much time trying to address such a simple request.

Have you removed the XMl comment markers in tomcat-users.xml?

Mark


> 
>  
> 
> Thanks…
> 
>  
> 
> Joel
> 
>  
> 
> *JOEL SAUNDERS*
> 
> * *
> 
> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
> 
> W: 518-652-4089| C: 518-265-0771
> joel.saund...@zones.com  | zones.com
> __
> 
> 
> 
>  
> 
> 
>   
>  
> 
>  
> 


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

RE: Accessing the manager application in a new Tomcat 8.5 install

[Joel Saunders]

Thanks... let me try that... At least that will knock that out of the realm of 
things that could be causing it.

I'll post after I test.


-Original Message-
From: John Larsen [mailto:john.lar...@javapipe.com] 
Sent: Monday, January 07, 2019 2:42 PM
To: Tomcat Users List
Subject: Re: Accessing the manager application in a new Tomcat 8.5 install

You need to allow access in your webapps/manager/META-INF/context.xml file

replace

allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"

with

allow=".*"


Or set it to more restrictive if needed.
Restart tomcat and you should be able to access.

John


On Mon, Jan 7, 2019 at 12:25 PM Joel Saunders 
wrote:

> I’ve spent about 2 weeks on and off (I have other projects) and still cant
> log in to the Tomcat 8.5 manager app.
>
> I get the signon box, enter my credentials from the tomcat-users.xml file
> and the signon box is promptly returned.
>
>
>
> I read the docs regarding the required roles, and the valve that restricts
> access other than from localhost, restarted each time with no success.   I
> haven’t figured out how to set debug on to hopefully give me more info on
> why it’s failing.
>
>
>
> Does anyone have specific steps that would need to be followed in order to
> allow a user to access the manager app after a new install?
>
>
>
> We don’t use this that much so it’s very frustrating to say the least.
> Once I get the manager access handled, then I’ll be able to deploy the
> application that tomcat8 was required for (I know that you can use commands
> vs the gui to do that, but we’re used to using the gui so that’s why we
> need it to work.
>
>
>
> Any comments/suggestions would be greatly appreciated as I’ve already
> wasted way too much time trying to address such a simple request.
>
>
>
> Thanks…
>
>
>
> Joel
>
>
>
> *JOEL SAUNDERS*
>
>
>
> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
>
> W: 518-652-4089| C: 518-265-0771
> joel.saund...@zones.com | zones.com 
>
> 
>
>
>
> 
> 
> 
> 
>
>
>

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

Re: Accessing the manager application in a new Tomcat 8.5 install

[John Larsen]

You need to allow access in your webapps/manager/META-INF/context.xml file

replace

allow="127\.\d+\.\d+\.\d+|::1|0:0:0:0:0:0:0:1"

with

allow=".*"


Or set it to more restrictive if needed.
Restart tomcat and you should be able to access.

John


On Mon, Jan 7, 2019 at 12:25 PM Joel Saunders 
wrote:

> I’ve spent about 2 weeks on and off (I have other projects) and still cant
> log in to the Tomcat 8.5 manager app.
>
> I get the signon box, enter my credentials from the tomcat-users.xml file
> and the signon box is promptly returned.
>
>
>
> I read the docs regarding the required roles, and the valve that restricts
> access other than from localhost, restarted each time with no success.   I
> haven’t figured out how to set debug on to hopefully give me more info on
> why it’s failing.
>
>
>
> Does anyone have specific steps that would need to be followed in order to
> allow a user to access the manager app after a new install?
>
>
>
> We don’t use this that much so it’s very frustrating to say the least.
> Once I get the manager access handled, then I’ll be able to deploy the
> application that tomcat8 was required for (I know that you can use commands
> vs the gui to do that, but we’re used to using the gui so that’s why we
> need it to work.
>
>
>
> Any comments/suggestions would be greatly appreciated as I’ve already
> wasted way too much time trying to address such a simple request.
>
>
>
> Thanks…
>
>
>
> Joel
>
>
>
> *JOEL SAUNDERS*
>
>
>
> SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
>
> W: 518-652-4089| C: 518-265-0771
> joel.saund...@zones.com | zones.com 
>
> 
>
>
>
> 
> 
> 
> 
>
>
>

Re: Tomcat SSL - unsupported protocol or cipher suit error

[Sameer Umbrajkar]

Dear Chris,

Could you help me out with the connector sample with sslhostconfig. I have
mentioned the connector details in my previous email.

On Mon 7 Jan, 2019, 12:22 AM Christopher Schultz <
ch...@christopherschultz.net wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Sameer,
>
> On 1/6/19 13:40, Sameer Umbrajkar wrote:
> > Dear John & Raj,
> >
> > *My JVM version is 8.1.015 and Tomcat version is 8.5.13* Please see
> > the version details below -
> > ==
> 
> >
> >
> E:\BOE\tomcat\bin>version
> > Using CATALINA_BASE:   "E:\BOE\tomcat" Using CATALINA_HOME:
> > "E:\BOE\tomcat" Using CATALINA_TMPDIR: "E:\BOE\tomcat\temp" Using
> > JRE_HOME:"E:\BOE\SAP BusinessObjects Enterprise XI
> > 4.0\win64_x64\sapjvm\" Using CLASSPATH:
> > "E:\BOE\tomcat\bin\bootstrap.jar;E:\BOE\tomcat\bin\tomcat-juli.jar"
> >
> >
> Server version: Apache Tomcat/8.5.13
> > Server built:   Mar 27 2017 14:25:04 UTC Server number:  8.5.13.0
> > OS Name:Windows NT (unknown) OS Version: 10.0
> > Architecture:   amd64 JVM Version:8.1.015 JVM Vendor: SAP
> > AG E:\BOE\tomcat\bin>
> > ==
> =
> >
> >  As suggested I added below parameters in Java Option of Tomcat
> > configuration still facing the same error related to TLS protocol
> > and ciphers
> > ==
> =
> >
> >
> - -Dhttps.protocols=TLSv1.2
> > -Dhttps.cipherSuites=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
> > ==
> =
> >
> >
> As requested, please find the HTTPS connector details below from server.
> xml
> > ==
> =
> >
> >
>  > port="8443" maxThreads="200" scheme="https" secure="true"
> > SSLEnabled="true" keystoreFile="E:\SSL\.keystore"
> > keystorePass="Am1@k123" clientAuth="false" sslProtocol="TLS"/>
>
> It would be better to use the more modern configuration which includes
>  elements within your  elements.
>
> http://tomcat.apache.org/tomcat-8.5-doc/config/http.html#SSL_Support
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwycYkACgkQHPApP6U8
> pFi+tw//ajl4qF4/leS0vP7GTZmxom3WtVbbxYQHRIL1+GDD922etcS60kgsD4cE
> dcQlmzPuChA0HOOn7MXgL8NH2edxRc6rssoQx2TuQcNotD2QfAQhRaLuV5usKG6h
> 1sv4tz2BuBVbAtEWSjwI3qtqv6feaJCtR1AU2kIlQilnbcKS2yEy/7jtW58UcmvZ
> SxjQ6Bxedm0LGcu7rwRVVKkYzKkJhhz+W1Bv8fFEp5KeY+sLPupsntlsVrC2cXL5
> c44XMBKHnRudiIk0p+d2gQPwYGTH4UtRMIX8W74Vfen60YweI9TpfuNSf9wC5TEP
> kLUk2+++hPTMxDW8BliZIMxJW7V+m9BpaGffGygGPbmMaVAWFg0v7yefmPVaiGz0
> QLLRstMpySoHDg51mptQpj49YHTZtuYtKlwQbSVIBxy+BAGUzAFnGRIAG9MYRyLG
> 4HpwDzYplyCRev/C+btjogMUWv+czxbqig5tcNtmMtX/Ycsiu24rq5EQbgqxzFTC
> IiSXqEz8zguJJZfgv676CJzzuWskSFZHLWeShiDN5H1EMj/NOzkwGESvFkuwrhVd
> RRQNNpS9+Z9754dd9iy8QwCR0avtE3Gxcfa6ID2JeuRpLSKpOg9JMcp/WkSjNMyc
> futM588UHDPm8Mv2+9pPirPSc9EOFeAXJ3cb7oxc/ef65SGnFxE=
> =Y8ni
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Accessing the manager application in a new Tomcat 8.5 install

[Joel Saunders]

I've spent about 2 weeks on and off (I have other projects) and still cant log 
in to the Tomcat 8.5 manager app.
I get the signon box, enter my credentials from the tomcat-users.xml file and 
the signon box is promptly returned.

I read the docs regarding the required roles, and the valve that restricts 
access other than from localhost, restarted each time with no success.   I 
haven't figured out how to set debug on to hopefully give me more info on why 
it's failing.

Does anyone have specific steps that would need to be followed in order to 
allow a user to access the manager app after a new install?

We don't use this that much so it's very frustrating to say the least.   Once I 
get the manager access handled, then I'll be able to deploy the application 
that tomcat8 was required for (I know that you can use commands vs the gui to 
do that, but we're used to using the gui so that's why we need it to work.

Any comments/suggestions would be greatly appreciated as I've already wasted 
way too much time trying to address such a simple request.

Thanks...

Joel

JOEL SAUNDERS

SR. DBA/ARCHITECT, MANAGED SERVICES | Zones, Inc.
W: 518-652-4089| C: 518-265-0771
joel.saund...@zones.com | 
zones.com
[cid:image001.jpg@01D4A694.C404DA50]

[cid:image002.jpg@01D4A694.C404DA50][cid:image003.jpg@01D4A694.C404DA50]
 [cid:image004.jpg@01D4A694.C404DA50]   
[cid:image005.jpg@01D4A694.C404DA50] 

Re: Parsing of multi part content

[Saurav Sarkar]

Thanks a lot Chris for the reply.

i think even if i parse the request myself i have to always load the
content in memory/disk.
Because in order to extract the file uploaded from the request , i have to
go through
the whole request stream and trim down the boundaries.

Best Regards,
Saurav

On Thu, Jan 3, 2019 at 3:20 AM Christopher Schultz <
ch...@christopherschultz.net> wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Saurav,
>
> On 1/2/19 12:20, Saurav Sarkar wrote:
> > Hi All,
> >
> > This is regarding the reading of multi part content in java server
> > side.
> >
> > ServletRequest has an API getParts() API for reading the parts of a
> > multi part request
> > https://docs.oracle.com/javaee/6/api/javax/servlet/http/HttpServletReq
> uest.html#getParts()
> 
> >
> >
> .
> >
> > It has part.getInputStream which can be used to read the content of
> > a specific part.
> >
> > Tomcat also provides an implementation for this API.
> >
> > But this API  parses the multi part content and keeps it in memory.
> > If the size increase then the content can be offloaded to disk.
> >
> > Why does the getPart API or any multi part parsing need to load the
> > content in memory ? Why can't direct streaming of content happen ?
> > Loading the content in memory and reading/writing to disk brings
> > extra cost. This will be specially costly when large files are
> > getting uploaded.
>
> True. You can always limit the part-size or request-size, but you
> can't stream huge uploads if you want to use getParts().
>
> > Is there no way where at least the file content loading could be
> > avoided ?
>
> Yes, there is a way.
>
> Instead of calling HttpServletRequest.getParameter* or
> HttpServletRequest.getPart*, you can call
> HttpServletRequest.getInputStream and parse everything yourself.
>
> > It may be not be a very specific question for tomcat but more
> > applicable to any servlet container.
>
> Correct, this is applicable to any servlet container.
>
> The multipart code in Tomcat parses everything to memory/disk at once
> because servlet code needs to be able to call
> HttpServletRequest.getParameter(String) in any order regardless of
> what how the request data is actually ordered. Also, getParts must
> return before the calling code can actually do anything with the data.
> There is no "register a stream handler for a multipart request part
> called 'foo'" or anything like that.
>
> If you want those semantics, you'll have to parse the request yourself.
>
> - -chris
> -BEGIN PGP SIGNATURE-
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwtMjkACgkQHPApP6U8
> pFgtJA//eRy6nI9gSj10Ok1PYRSYNGJHcblGieiK8aicWqq0xV/RQgMVarq6PK8i
> OHaBt3e/plA9Z5fr7tNs0jyT6dEhrVONYgkLJmyNxLC/EBtYXFD4M2q2R+YnIZbO
> GZBjse/O5xzJAK3jJbWVe9w+rJfz6FCp6mPn/0AUNMUVhOgzC5/1oeKvMkyooEHY
> 598ULLioK0ZvHWHeVJNe/hNdggjwm9jNuDrxuvrNLX6fY44ed/jlfzUh3G0tAw8B
> Ik1Ug8AJi1EQU0sVPfik5Fos7D740DI0KiRcQWsjvEqvelJhWfNTQkkY9GWUmPzW
> EMvCJH1T+ehGYo8HD1w+I74SsFlfTRyI/muzzlT5Gy2hCzN56JN4QU+oUQhGfS1E
> njF0SAmB47XYdMq2fKSaaqmi+zfsvr1AgaPBE/TyfXhCRUYe7K34ThXBpbqon0dd
> UdphHvka7gyBp/dqrufyhr/EjfnCi6MWUoLSWEIhrMvfeEFsrKshRlql3B+aE9Vk
> iuwb0p2TT7vu79oCeHr+eANdIurM8vrBx5+PYWJ8AbMqarHeCyvyR0tfgAzokI9w
> 2rVlg2NuiVN3ByuK9ytDGp94m5BwxdQ1jC8zeJUgCpKesXxzrB4c1IhaY6CRTEFa
> S3K6IfGtc1zSKGMaN/gz8Mqq5ljm2P8GfkwrzxoDLETjjgVjxKE=
> =DKX3
> -END PGP SIGNATURE-
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

RE: log4j app logging

[Lemke, Michael ST/HZA-ZIC2]

On Thursday, December 27, 2018 5:35 PM, Mark H. Wood wrote:
>On Wed, Dec 19, 2018 at 06:52:20PM +, Lemke, Michael  ST/HZA-ZIC2 wrote:
>> On December 19, 2018 6:54 PM Lemke, Michael wrote:
>> >On December 18, 2018 8:52 PM Christopher Schultz wrote:
>> >>On 12/18/18 12:42, Lemke, Michael  ST/HZA-ZIC2 wrote:
>> >>> I have an old webapp that uses log4j 1.2 and which I am trying to 
>> >>> deploy on tomcat. For the heck of it I can't get tomcat to use the 
>> >>> log4.properties file. What am I doing wrong?
>> >>
>> >>
...
>> >I guess I have a terrible mess of all sorts of loggers in my libraries. I am
>> >not good at all the different Java loggers. The log4j.properties I want 
>> >to use is for log4j-1.2.27 so not quite bleeding edge ??. Then there are 
>> >other libs that pull in slf4j-api-1.7.25.jar, there is a 
>> >jcl-over-slf4j-1.7.25.jar, 
>> >logback-classic-1.2.3.jar, logback-core-1.2.3.jar.
>> >
>
>If this happens to be a project built with Maven then 'mvn
>dependency:tree' should tell you which artifacts are pulling in
>SLF4J.  You may need to run this more than once as you comb out
>transitive dependencies one by one.
>
>But it's possible to use multiple logging frameworks in one webapp. if
>you include/exclude the right artifacts.  See
>https://www.slf4j.org/legacy.html if you need to do this with SLF4J
>and Log4J v1.

Thank you very much, Mark, this was very helpful. With it I could clean up the 
mess. 
Most important part was to get rid of logback-* and switch everything to slf4j
with the help of slf4j-log4j12. Now everything seems to be working.

Thanks again,
Michael

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