2013/10/20 Christopher Schultz :
> Edoardo,
>
> On 10/18/13 6:03 PM, Edoardo Panfili wrote:
>> Il 17/10/13 18:45, Edoardo Panfili ha scritto:
>
> I'll bet the problem is that Tomcat doesn't like applications
> declaring themselves to be privileged="true". The first time Tomcat is
> started, META-IN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
On 10/20/13 2:44 PM, Christopher Schultz wrote:
> Edoardo,
>
> On 10/18/13 6:03 PM, Edoardo Panfili wrote:
>> Il 17/10/13 18:45, Edoardo Panfili ha scritto:
>>> My Tomcat (7.0.42) is listening on port 7080 and I have this
>>> conf/tomcat-user
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 6:03 PM, Edoardo Panfili wrote:
> Il 17/10/13 18:45, Edoardo Panfili ha scritto:
>> My Tomcat (7.0.42) is listening on port 7080 and I have this
>> conf/tomcat-users.xml in (production server)
>>
>> --- > username="mynam
Il 19/10/13 15:34, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/t
Il 19/10/13 19:53, André Warnier ha scritto:
Ognjen Blagojevic wrote:
Mark,
On 19.10.2013 17:51, Mark Eggers wrote:
On 10/19/2013 7:44 AM, Ognjen Blagojevic wrote:
If you want to keep parameter deployXML set to false, I believe you
need
to copy webapps/manager/META-INF/context.xml to
conf/Cat
Il 19/10/13 16:44, Ognjen Blagojevic ha scritto:
Edoardo,
On 19.10.2013 0:03, Edoardo Panfili wrote:
4- second modify to server.xml
becomes
It is great that you took effort to pin-point the source of the problem.
Often users are not willing to do that.
thanks to so many people ready to hel
Il 19/10/13 16:19, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 19/10/13 14:21, Martin Gainty ha scritto:
Date: Sat, 19 Oct 2013 10:23:11 +0200
From: edoa...@aspix.it
To: users@tomcat.apache.org
Subject: Re: can't connect to manager application
Il 19/10/13 00:24, Mark Egge
Ognjen Blagojevic wrote:
Mark,
On 19.10.2013 17:51, Mark Eggers wrote:
On 10/19/2013 7:44 AM, Ognjen Blagojevic wrote:
If you want to keep parameter deployXML set to false, I believe you need
to copy webapps/manager/META-INF/context.xml to
conf/Catalina/localhost/manager.xml.
Yep, reproducib
Mark,
On 19.10.2013 17:51, Mark Eggers wrote:
On 10/19/2013 7:44 AM, Ognjen Blagojevic wrote:
If you want to keep parameter deployXML set to false, I believe you need
to copy webapps/manager/META-INF/context.xml to
conf/Catalina/localhost/manager.xml.
Yep, reproducible on Windows 7.
Thanks
On 10/19/2013 7:44 AM, Ognjen Blagojevic wrote:
Edoardo,
On 19.10.2013 0:03, Edoardo Panfili wrote:
4- second modify to server.xml
becomes
It is great that you took effort to pin-point the source of the problem.
Often users are not willing to do that.
Now, deployXML=false instructs Tomcat
Edoardo,
On 19.10.2013 0:03, Edoardo Panfili wrote:
4- second modify to server.xml
becomes
It is great that you took effort to pin-point the source of the problem.
Often users are not willing to do that.
Now, deployXML=false instructs Tomcat to ignore context descriptors in
directory web
Edoardo Panfili wrote:
Il 19/10/13 14:21, Martin Gainty ha scritto:
Date: Sat, 19 Oct 2013 10:23:11 +0200
From: edoa...@aspix.it
To: users@tomcat.apache.org
Subject: Re: can't connect to manager application
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Wa
Il 19/10/13 14:21, Martin Gainty ha scritto:
Date: Sat, 19 Oct 2013 10:23:11 +0200
From: edoa...@aspix.it
To: users@tomcat.apache.org
Subject: Re: can't connect to manager application
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Pa
Edoardo Panfili wrote:
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
--
> Date: Sat, 19 Oct 2013 10:23:11 +0200
> From: edoa...@aspix.it
> To: users@tomcat.apache.org
> Subject: Re: can't connect to manager application
>
> Il 19/10/13 00:24, Mark Eggers ha scritto:
> > On 10/18/2013 3:18 PM, André Warnier wrote:
> >> Edoar
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I
Il 19/10/13 00:24, Mark Eggers ha scritto:
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I
Il 19/10/13 00:18, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I use
curl -u myname:pwd
http://localhost:70
On 10/18/2013 3:18 PM, André Warnier wrote:
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I use
curl -u myname:pwd
http://localhost:708
Edoardo Panfili wrote:
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I use
curl -u myname:pwd
http://localhost:7080/manager/text/reload?path=/myApplication
th
Il 17/10/13 18:45, Edoardo Panfili ha scritto:
My Tomcat (7.0.42) is listening on port 7080 and I have this
conf/tomcat-users.xml in (production server)
---
--
if I use
curl -u myname:pwd
http://localhost:7080/manager/text/reload?path=/myApplication
the response is---
MESSAGE- Hash: SHA256
Edoardo,
On 10/18/13 12:38 PM, Edoardo Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
can't connect to manager application
Il 18/10/13 16:40, André Wa
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: Re: can't connect to manager application
> And about Martin's remarks being right : I don't know why, but my fingers
> have this
> automatic reflex of hitting the delete button whenever my eyes see one of
12:38 PM, Edoardo Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
can't connect to manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il
> From: Konstantin Kolinko [mailto:knst.koli...@gmail.com]
> Subject: Re: can't connect to manager application
> As Martin Gainty noted, it seems that there is quite a number of
> errors in how OP's web applications are deployed. All allowed
> attributes are documented
2013/10/18 Edoardo Panfili :
>
> I didn't touch the manager application (at least not voluntarily!).
>
>
>
>> That may also explain why the latest logfile did not show any problem.
>> It was probably copied before the first real call to the Manager happened.
>
>
>> Right now though, there is probab
Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
can't connect to manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, O
Hash: SHA256
Edoardo,
On 10/18/13 12:38 PM, Edoardo Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From: edoa...@aspix.it
To: users@tomcat.apache.org Subject: Re: can't connect to
manager application
Il 18/10/13 16:40, André Warnier ha scritto
scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
can't connect to manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Ed
Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
can't connect to manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, O
fili wrote:
>>> Il 18/10/13 18:29, Martin Gainty ha scritto:
>>>>
>>>>> Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
>>>>> edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
>>>>> can't connect to manager application
>&g
l 18/10/13 18:29, Martin Gainty ha scritto:
>>>>> Date: Fri, 18 Oct 2013 18:04:19 +0200 From:
>>>>> edoa...@aspix.it To: users@tomcat.apache.org Subject: Re:
>>>>> can't connect to manager application
>>>>>
>>>>> Il 18/10
Subject: Re: can't connect to
manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to
reproduce the problem on clean T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:38 PM, Edoardo Panfili wrote:
> Il 18/10/13 18:29, Martin Gainty ha scritto:
>>
>>> Date: Fri, 18 Oct 2013 18:04:19 +0200 From: edoa...@aspix.it
>>> To: users@tomcat.apache.org Subject: Re: c
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:38 PM, Edoardo Panfili wrote:
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200 From: edoa...@aspix.it
To: users@tomcat.apache.org Subject: Re: can't conne
Il 18/10/13 18:38, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 18:17, Christopher Schultz ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:04 PM, Edoardo Panfili wrote:
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
I
Edoardo Panfili wrote:
Il 18/10/13 18:17, Christopher Schultz ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:04 PM, Edoardo Panfili wrote:
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto
Il 18/10/13 18:29, Martin Gainty ha scritto:
Date: Fri, 18 Oct 2013 18:04:19 +0200
From: edoa...@aspix.it
To: users@tomcat.apache.org
Subject: Re: can't connect to manager application
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojev
Il 18/10/13 18:25, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 18:16, Caldarale, Charles R ha scritto:
From: Edoardo Panfili [mailto:edoa...@aspix.it]
Subject: Re: can't connect to manager application
seem that the solution is to add privileged="true"
> Date: Fri, 18 Oct 2013 18:04:19 +0200
> From: edoa...@aspix.it
> To: users@tomcat.apache.org
> Subject: Re: can't connect to manager application
>
> Il 18/10/13 16:40, André Warnier ha scritto:
> > Edoardo Panfili wrote:
> >> Il 18/10/13 08:43,
Il 18/10/13 18:17, Christopher Schultz ha scritto:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:04 PM, Edoardo Panfili wrote:
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, E
Edoardo Panfili wrote:
Il 18/10/13 18:16, Caldarale, Charles R ha scritto:
From: Edoardo Panfili [mailto:edoa...@aspix.it]
Subject: Re: can't connect to manager application
seem that the solution is to add privileged="true" at
$tomcat/conf/context.xml... and the "reoloa
> From: Edoardo Panfili [mailto:edoa...@aspix.it]
> Subject: Re: can't connect to manager application
> seem that the solution is to add privileged="true" at
> $tomcat/conf/context.xml... and the "reoload" command now works.
You really, really, really must
Il 18/10/13 18:16, Caldarale, Charles R ha scritto:
From: Edoardo Panfili [mailto:edoa...@aspix.it]
Subject: Re: can't connect to manager application
seem that the solution is to add privileged="true" at
$tomcat/conf/context.xml... and the "reoload" command now wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Edoardo,
On 10/18/13 12:04 PM, Edoardo Panfili wrote:
> Il 18/10/13 16:40, André Warnier ha scritto:
>> Edoardo Panfili wrote:
>>> Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
>> To rule out fa
Il 18/10/13 18:03, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the
probl
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the problem was surely present wit
Edoardo Panfili wrote:
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the proble
Il 18/10/13 16:40, André Warnier ha scritto:
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the problem was surely present wit
Edoardo Panfili wrote:
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the problem was surely present with 7.0.39, the 7.0.42 is a fresh
installation f
Il 18/10/13 08:43, Ognjen Blagojevic ha scritto:
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the problem was surely present with 7.0.39, the 7.0.42 is a fresh
installation for me.
Could you pleas
On 18.10.2013 7:34, Edoardo Panfili wrote:
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 install?
the problem was surely present with 7.0.39, the 7.0.42 is a fresh
installation for me.
Could you please clarify: does the problem exists on 7.0.42, 7.0.
Il 17/10/13 22:43, Ognjen Blagojevic ha scritto:
Edoardo,
On 17.10.2013 18:45, Edoardo Panfili wrote:
Some release ago (tomcat 7.0.x sorry, I can't be more precise) all was
well also on production server. Maybe i did something wrong during an
update.
To rule out faulty upgrade, could you try
Il 17/10/13 20:58, Martin Gainty ha scritto:
http://localhost:8080/manager/text/reload?path=/examples
Signal an existing application to shut itself down and reload. This can
be useful when the web application context IS NOT RELOADABLE
and you have updated classes or property files in the
Edoardo,
On 17.10.2013 18:45, Edoardo Panfili wrote:
Some release ago (tomcat 7.0.x sorry, I can't be more precise) all was
well also on production server. Maybe i did something wrong during an
update.
To rule out faulty upgrade, could you try to reproduce the problem on
clean Tomcat 7.0.42 i
http://localhost:8080/manager/text/reload?path=/examples
Signal an existing application to shut itself down and reload. This can
be useful when the web application context IS NOT RELOADABLE
and you have updated classes or property files in the
/WEB-INF/classes
directory or when you have a
56 matches
Mail list logo
