Author: markt
Date: Sat Nov 27 10:41:26 2010
New Revision: 1039648
URL: http://svn.apache.org/viewvc?rev=1039648view=rev
Log:
Using SecureRandom makes digesting the ID unnecessary. Dropping the digest
gives ~20% performance gain on ID generation.
Modified:
Author: markt
Date: Sat Nov 27 11:41:10 2010
New Revision: 1039657
URL: http://svn.apache.org/viewvc?rev=1039657view=rev
Log:
Drop the entropy attribute. SecureRandom has a sufficiently secure self-seeding
mechanism.
Modified:
tomcat/trunk/java/org/apache/catalina/session/ManagerBase.java
Author: markt
Date: Sat Nov 27 13:47:03 2010
New Revision: 1039680
URL: http://svn.apache.org/viewvc?rev=1039680view=rev
Log:
Remove attributes from PersistentManager too
Modified:
tomcat/trunk/webapps/docs/config/manager.xml
Modified: tomcat/trunk/webapps/docs/config/manager.xml
URL:
Author: markt
Date: Sat Nov 27 13:52:13 2010
New Revision: 1039683
URL: http://svn.apache.org/viewvc?rev=1039683view=rev
Log:
Update so this will run
Modified:
tomcat/trunk/test/org/apache/catalina/session/Threading.java
Modified: tomcat/trunk/test/org/apache/catalina/session/Threading.java
Author: markt
Date: Sat Nov 27 14:50:37 2010
New Revision: 1039692
URL: http://svn.apache.org/viewvc?rev=1039692view=rev
Log:
Add a /dev/urandom vs SecureRandom benchmark
Modified:
tomcat/trunk/test/org/apache/catalina/session/Benchmarks.java
Modified:
With this change to createRandom it is not clear to me what the value of the
reseeding is when the SecureRandom is not user-supplied. Maybe a crypto
expert can comment. It would speed up initialization in the default case if
the reseeding was only done for user-defined generators.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50351
Summary: javax.naming.NamingException: No set method found for
property: singleton
Product: Tomcat 7
Version: trunk
Platform: PC
Status: NEW
Severity:
https://issues.apache.org/bugzilla/show_bug.cgi?id=50352
Summary: AsyncListener.onComplete is not called after
AsyncContext.complete() is called
Product: Tomcat 7
Version: 7.0.4
Platform: All
OS/Version: All
https://issues.apache.org/bugzilla/show_bug.cgi?id=50353
Summary: Calling asyncContext.getResponse() returns null after
async timeout
Product: Tomcat 7
Version: trunk
Platform: All
OS/Version: All
Status: NEW
https://issues.apache.org/bugzilla/show_bug.cgi?id=50353
--- Comment #1 from Sylvain Laurent sylvain.laur...@gmail.com 2010-11-27
18:04:53 EST ---
Same behavior with getRequest() : it returns null.
This leads to a NPE if asyncContext.dispatch() is called after the timeout :
10 matches
Mail list logo