Re: [OT] Re: Parallel deploy stopps picking up new wars

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 5/9/17 6:13 PM, André Warnier (tomcat) wrote:
> Before I opened this post, I thought it was some WH.gov press
> release..

Zing!

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

iQIcBAEBCAAGBQJZEk6nAAoJEBzwKT+lPKRYBqYP/30800yUzVdrlpWaD1Cs+Brw
rrLJfRmP5cmkb1z1kAZjkFcPFeKHEnbax8se0D9c6TbGTCJOCqoEz8SfJJINn2AI
3NxaCSlDWwPb8OvUUlVfqA9XdYjcmdq+rPHJ57alyjzi3f3MJZt6KYKq3VcS/C12
SYDcxit6iu0lcetlayzwN/pSLrznb4utkY2WBHInNF5js3k+v1jmoWzsouOsO04a
sW+FxISFthRlrUC4+dd4c5WIF23ETK5JM0a9avDpbZ/oGo9ikxndIHF1+E4LM8Ln
j2Ild0mhvRyQvFJNw3eoxakdmiE8sOOR/8dd6der5IgSKreKs9oeKbvJK4ahp9qw
S0I4psUrqUwjIo2RRRLdSwEu67LadN/XdkA1+ESEbQ1yA17XYzj+K8UK5tDwIJJu
wlw12cBZXhYt6Ef1xGy92eNlTmLPARxsRkwdM5Zw5Ub3aLUCAINQ4QgGL0rNBwHT
TgYwtS1UJRE4ro5FmMbBcSoceFgQZ9s/sw2BX3qrS62gA5MXt+3YAtyfXVImToAU
MbWLNeDWkfO3n6LKYs2+3HhSUdBEJhCk9CdytCvxiaRteNuKMlKbbIUJWmIDARXu
LqmwNh+r5LGd0ucAEfw08GSZ9bHmwYauPLkWzGjBJq0QUk+l7k/9+8DkgwWrLhsk
zx6dbjMLkX1Zn9/PZqZ7
=wabT
-END PGP SIGNATURE-

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

Re: Embedded tomcat does not find web-fragment in jars outside web-inf\lib

[Mark Thomas]

On 09/05/17 15:25, Michael Heinen wrote:
> Hi all,
> 
> I am currently mirgating an application from Tomcat 7.0.73 to 8.0.43.
> On development platforms we use an embedded tomcat.
> On of the jars on the classpath contains a web-fragment.xml in it's
> META-INF folder.
> This jar file is NOT located within the webApp but simply on the classpath.
> With Tomcat 7.0.73 the web-fragment is processed and the defined filter
> is instantiated.
> With Tomcat 8.0.43 the web-fragment is not processed at all.
> 
> Some lines of code:
> 
> final StandardContext ctx = ...
> ctx.setXmlBlockExternal(false);
> 
> final StandardJarScanner jarScanner = new StandardJarScanner();
> jarScanner.setScanAllDirectories(true);
> jarScanner.setScanAllFiles(true);
> jarScanner.setScanBootstrapClassPath(true);
> jarScanner.setScanClassPath(true);
> jarScanner.setScanManifest(false);
> ctx.setJarScanner(jarScanner);
> 
> Should this work with Tomcat 8 or is my expectation wrong?

It should work. I'd recommend putting a break-point in
StandardJarScanner and stepping through the Tomcat code to see what is
going wrong.

Mark


> 
> Note that the web-fragement is processed when I move the jar to the
> web-inf\lib folder.
> 
> Regards,
> 
> Michael
> 
> 
> 
> 
> -
> 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

[OT] Re: Parallel deploy stopps picking up new wars

[tomcat]

Before I opened this post, I thought it was some WH.gov press release..


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

Re: Parallel deploy stopps picking up new wars

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Chris,

On 5/9/17 4:31 PM, Chris Gamache wrote:
> This is tomcat 8.0.28
> 
> Background:
> 
> Tomcat will be running fine, we can deploy new versions of webapps
> via parallel deploy no problems. Then, after a few days, tomcat
> will stop picking up new versions of webapps. It's like tomcat has
> decided to stop watching for new files. It's very odd. I've tried
> things like touching the files to wake it up, but I've found
> nothing short of doing a full stop and restart to get parallel
> deployment going again.
> 
> I don't see anything in the changelogs that addresses a problem
> like this, so I'm not 100% sure an upgrade will help. Maybe someone
> knows better than I.
> 
> So I'm stumped. I need some ideas from you expert people. Stopping
> and starting the service is exactly the thing we started using
> parallel deployment to avoid!

Any chance of re-testing with 8.0.latest (currently 8.0.43)?

If not, I'd have a look at a thread dump to see if the
BackgroundProcessor is still running. If that stops, most background
tasks stop.

If the BackgroundProcessor stops, you'll probably get an exception and
stack trace in your catalina.out and/or other logs.

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

iQIcBAEBCAAGBQJZEip2AAoJEBzwKT+lPKRYW64QAIDFHCAD8KYrXhM0ok7nfwwK
qKWNqjZPtYIDTZyCzVKY6qd6dLIS+LXPYhrozZNU1xCMvt3XXDxNUktodfWASi0f
CfzQa5c0jMuJTT/y5RfeULv/VassH4WROfKlJVhgHDZ47e2MJS1S2btvpwGzb+qL
y7d89V9r9cSRG0wScqeYYAHZ2ezXmCqNjYUnDOpZqz4JqT+QGE/ifU9QEGywiGfX
fykT58WbGvhrCbCqadoLhhvmk4a4CrsV2iD3T4dlOJcw9kZ3e/VNTp+VO2YVDsvg
y+BiCPLWimCLfJoLCinUMXXxb1COuoAExakO1n2N0XUM68gCm3uOOMLrp7BqjZpL
yfbh2IuuUuia1Xs9lHsHhUlT4LbdPlum3rvQt+BV4D430ogRZmU4jd9cgyfMDt9e
Z0CBDBjPtZx2dhycKwBK4Ysgkxdkw0ryZa0W2krpEN6r0QbqYg8cVTlhRW5KqDcB
ywIxZSE8LvdINrBSjbZy1uo1aLttuUyZFLtRwswQwsv1FlyaPBI9LojiDK3yXGK/
kmZRcDNWSIWe2vHjC2cClsIriCVNWBxTi/XSacPWvkBdIgdgAEAkwxZUqkosyEY1
54gPein36K3ZdhosVygvywsFXdhqRAiyksv4+shDTxH9zt1vduLyS+zjmcBOSGhR
hWVKfj3DtNa+o1foBqrN
=lYUh
-END PGP SIGNATURE-

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

Parallel deploy stopps picking up new wars

[Chris Gamache]

This is tomcat 8.0.28

Background:

Tomcat will be running fine, we can deploy new versions of webapps via
parallel deploy no problems. Then, after a few days, tomcat will stop
picking up new versions of webapps. It's like tomcat has decided to stop
watching for new files. It's very odd. I've tried things like touching the
files to wake it up, but I've found nothing short of doing a full stop and
restart to get parallel deployment going again.

I don't see anything in the changelogs that addresses a problem like this,
so I'm not 100% sure an upgrade will help. Maybe someone knows better than
I.

So I'm stumped. I need some ideas from you expert people. Stopping and
starting the service is exactly the thing we started using parallel
deployment to avoid!

Embedded tomcat does not find web-fragment in jars outside web-inf\lib

[Michael Heinen]

Hi all,

I am currently mirgating an application from Tomcat 7.0.73 to 8.0.43.
On development platforms we use an embedded tomcat.
On of the jars on the classpath contains a web-fragment.xml in it's 
META-INF folder.

This jar file is NOT located within the webApp but simply on the classpath.
With Tomcat 7.0.73 the web-fragment is processed and the defined filter 
is instantiated.

With Tomcat 8.0.43 the web-fragment is not processed at all.

Some lines of code:

final StandardContext ctx = ...
ctx.setXmlBlockExternal(false);

final StandardJarScanner jarScanner = new StandardJarScanner();
jarScanner.setScanAllDirectories(true);
jarScanner.setScanAllFiles(true);
jarScanner.setScanBootstrapClassPath(true);
jarScanner.setScanClassPath(true);
jarScanner.setScanManifest(false);
ctx.setJarScanner(jarScanner);

Should this work with Tomcat 8 or is my expectation wrong?

Note that the web-fragement is processed when I move the jar to the 
web-inf\lib folder.


Regards,

Michael




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

Re: tomcat 8.5.14, gives 400 error when using a | in the request parameters

[Lulseged Zerfu]

Hi


Check the last line in the catalina.properties file to enable the pipe 
character in your URL.


BR

Lulseged



From: John Zanoni 
Sent: Monday, May 8, 2017 12:53 PM
To: users@tomcat.apache.org
Subject: tomcat 8.5.14, gives 400 error when using a | in the request parameters

Dear,

After upgrading tomcat to version 8.5.14 the webserver returns a 400 error when 
accessing any web page using a | (pipe) in one of the request parameters.

The | (pipe) is added when the URL is re-written using google analytics 
_getLinkerUrl(), see javascript function below.


var pageTracker = _gat._getTrackerByName();
var uri=pageTracker._getLinkerUrl(“http://shop.bakkerijhaasnoot.nl”);
alert(uri);


http://shop.bakkerijhaasnoot.nl?__utma=68893267.349269500.1493841017.1493841017.1493913856.2&__utmb=68893267.38.9.1493914656569&__utmc=68893267&__utmx=-&__utmz=68893267.1493841017.1.1.utmcsr=(direct)
 | utmccn=(direct) | utmcmd=(none)&_utmv=-&_utmk=59369258

Previous to tomcat 8.5.14 this was never an issue. It is possible to replace 
the | (pipe) for a %7C this prevents tomcat from returning a 400 error but how 
can we tell tomcat not to response with a 400 when a | (pipe) is used in the 
value of one of the parameters. We rolled back to an older version (tomcat 
8.5.4) to solve the issue but this is actually a temporary solution.

Thanks in advance!

John Zanoni




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