[Bug 58187] Tomcat manager incorrect deployment status

2015-08-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58187

--- Comment #5 from remi.lebast...@flexcom.lu ---
Sorry the video can be read on Chrome (I just try now) by on Firefox it seems
to considered it corrupted!

The WAR doesn't matter: for the video I take the jenkins.war that can be found
here http://mirrors.jenkins-ci.org/war/latest/jenkins.war.

I called the URL
/manager/text/deploy?path=/jenkins&war=c:/jenkins.war&update=true on Tomcat
7.0.61 and on Tomcat 7.0.62.

On Tomcat 7.0.61: application is deployed and Tomcat manager send the response
after deployment.

On Tomcat 7.0.62: Tomcat send the reponse and the application is deployed after
the notification.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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



buildbot success in ASF Buildbot on tomcat-8-trunk

2015-08-14 Thread buildbot
The Buildbot has detected a restored build on builder tomcat-8-trunk while 
building ASF Buildbot. Full details are available at:
http://ci.apache.org/builders/tomcat-8-trunk/builds/62

Buildbot URL: http://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'on-tomcat-8-commit' 
triggered this build
Build Source Stamp: [branch tomcat/tc8.0.x/trunk] 1695825
Blamelist: markt

Build succeeded!

Sincerely,
 -The Buildbot




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



[Bug 58157] RecycleRequiredException and missing AsyncListener.onTimeout call

2015-08-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58157

--- Comment #15 from cg.throwa...@mailinator.com ---
Hi Mark, just thought I'd try out your latest update - still seeing the
exception (as you have stated above). Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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



[Bug 58244] New: two way SSL loses client certificate after a few requests

2015-08-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58244

Bug ID: 58244
   Summary: two way SSL loses client certificate after a few
requests
   Product: Tomcat Native
   Version: 1.1.33
  Hardware: PC
OS: All
Status: NEW
  Severity: normal
  Priority: P2
 Component: Library
  Assignee: dev@tomcat.apache.org
  Reporter: david.bala...@comtrade.com

When accessing a web application that uses client certificate authentication
run on Tomcat/APR (on Windows) with Firefox or Chrome, the client cert is
"lost" after a short while. To the app it appears the client certificate was
not sent.

Example code (JSP fragment, can be the only content of a JSP file):

User client cert data:
<%= ((java.security.cert.X509Certificate[])
request.getAttribute("javax.servlet.request.X509Certificate"))[0].
getSubjectX500Principal().toString()%>

After a few refreshes of the page (where it will show the client certificate
DN) the page will fail with a NullPointerException as request.getAttribute will
return null. It usually happens in less than a minute. To be more precise: when
reloading about once per second, the problem occurs almost every time after 30
seconds. After that each request will fail the same way, until I restart
tomcat.

This happens with Firefox (v39 and v40) and Chrome (v44), but not with IE v11.

It also occurs with different versions of tomcat and Java (and OS bitness) -
see below for a list.

A simple test case using latest versions is:

download and extract apache-tomcat-8.0.24-windows-x64.zip
in the webapps folder create a folder named cert, there create a file named
ccertA.jsp that contains the above code snippet

in server.xml add a line:



start tomcat by executing startup.bat
open the page https://localhost:8443/cert/ccertA.jsp and keep refreshing it
every few seconds
After about 30 seconds it will show a NPE exception error page.

If I don't use APR (by deleting the tcnative-1.dll file and adapting the
connector syntax for JSSE) the problem does not happen.

Tried versions, all having the issue:

apache-tomcat-8.0.24-windows-x64 (also 32 bit version) - has APR 1.5.1 and
TCN 1.1.33
apache-tomcat-6.0.44-windows-x64
Java 1.6.0 Updates 12 and 45
Java 1.8 Update 51
Windows 7 Pro SP1 64 bit
Windows 7 Pro SP1 32 bit
Window 8.1 Pro 64 bit
Windows 10 Home 64 bit
Firefox versions 39.0 39.0.3 and 44
Chrome v44
Ubuntu 14.04 LTS 64 bit / tomcat 7.0.52-1ubuntu0.3 / libapr1:amd64 1.5.0-1
/ libtcnative-1:amd64 1.1.29-1

A similar issue was discussed on the tomcat-users mailing list in 2010: "Client
certificate gone after 1 minute timeout (SSL, APR)" [1] but with no solution. I
posted there myself recently ( "Firefox SSL with APR - losing client
certificate" [2] has a bit more details), but it is basically just my
monologue.


Originally I tested with a server certificate issued by my private testing CA.
Now I also tried with a "real" certificate issued by trusted CA. (I used my
personal certificate. The browser complained about the hostname mitmatch which
I clicked away).


Can upload test CA, server-cert/key and client cert/key for test if requiered.

[1]
http://grokbase.com/t/tomcat/users/102pdv412y/client-certificate-gone-after-1-minute-timeout-ssl-apr
[2] http://www.mail-archive.com/users@tomcat.apache.org/msg118902.html

-- 
You are receiving this mail because:
You are the assignee for the bug.

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



[Bug 58157] RecycleRequiredException and missing AsyncListener.onTimeout call

2015-08-14 Thread bugzilla
https://bz.apache.org/bugzilla/show_bug.cgi?id=58157

--- Comment #16 from Mark Thomas  ---
A quick update before the weekend.

I have better grip on what is going wrong. The issue is that async dispatches
are being processed multiple times. Depending on the timing, this can go wrong.

The fix (for 7.0.x at least) is non-trivial. I've tried various small patches
but all introduce a different problem. At this point, I think a reafctoring of
the async dispatch handling will be required.

I haven't looked at 9.0.x or 8.0.x as yet. The refactoring that has already
taken place in those versions may have already addressed this. Or not.

I'll continue to look at this next week.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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