[Bug 58624] Websocket send blocks indefinitely in FutureToSendHandler

https://bz.apache.org/bugzilla/show_bug.cgi?id=58624 Barry Coughlan changed: What|Removed |Added OS||All ---

[Bug 58624] Websocket send blocks indefinitely in FutureToSendHandler

https://bz.apache.org/bugzilla/show_bug.cgi?id=58624 --- Comment #2 from Barry Coughlan --- Sorry for all the noise. If I understand correctly, the flow of sending messages goes like this: WsRemoteEndpointImplBase.startMessage -> messaged dispatched to

[Bug 57773] performance problems when using scopeless optional attributes

https://bz.apache.org/bugzilla/show_bug.cgi?id=57773 --- Comment #5 from Woonsan Ko --- Hi @markt and @donnchadh, How about introducing a whitelist filter attribute in context configuration? e.g, elStaticAccessFilter="^[a-z].*$". Like containerSciFilter attribute, it can be

[Bug 57773] performance problems when using scopeless optional attributes

https://bz.apache.org/bugzilla/show_bug.cgi?id=57773 --- Comment #6 from Woonsan Ko --- It should be a "filter", not "whitelist" above. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 58624] Websocket send blocks indefinitely in FutureToSendHandler

https://bz.apache.org/bugzilla/show_bug.cgi?id=58624 --- Comment #3 from Christopher Schultz --- (In reply to Barry Coughlan from comment #2) > My current working theory for what's happening is as follows: > - Server starts sending a message > - The client closes

[Bug 58623] New: WebSocket client should handle 302 redirect

https://bz.apache.org/bugzilla/show_bug.cgi?id=58623 Bug ID: 58623 Summary: WebSocket client should handle 302 redirect Product: Tomcat 7 Version: unspecified Hardware: All OS: All Status: NEW Severity:

[Bug 58624] New: Websocket send blocks indefinitely in FutureToSendHandler

https://bz.apache.org/bugzilla/show_bug.cgi?id=58624 Bug ID: 58624 Summary: Websocket send blocks indefinitely in FutureToSendHandler Product: Tomcat 8 Version: 8.0.24 Hardware: PC Status: NEW

[Bug 58230] Incorrect input from ServletInputStream in ReadListener

https://bz.apache.org/bugzilla/show_bug.cgi?id=58230 --- Comment #5 from Remy Maucherat --- That was actually caused by what broke the NIO2 connector in bug 57799, available() had a side effect that it would cause an IO read. The fix was to remove the available() call, but is

[Bug 58623] WebSocket client should handle 302 redirect

https://bz.apache.org/bugzilla/show_bug.cgi?id=58623 --- Comment #1 from Remy Maucherat --- That's included in 57767 (for trunk). I looked a bit at Tyrus, and it is a fairly standard HTTP client (with a lot of proprietary config for all its features), while the websockets

[Bug 57011] Exception when writing HTTP response in the AsyncListener onTimeout method (servlet 3 HTTP-NIO)

https://bz.apache.org/bugzilla/show_bug.cgi?id=57011 --- Comment #8 from melon --- I upgrade to tomcat8.0.28，hope that it will be ok -- You are receiving this mail because: You are the assignee for the bug.

svn commit: r1715008 - /tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml

Author: markt Date: Wed Nov 18 15:05:52 2015 New Revision: 1715008 URL: http://svn.apache.org/viewvc?rev=1715008=rev Log: Whitespace police Modified: tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml Modified: tomcat/tc8.0.x/trunk/webapps/docs/changelog.xml URL:

[GUMP@vmgump]: Project tomcat-tc8.0.x-validate (in module tomcat-8.0.x) failed

/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/checkstyle/target/checkstyle-6.13-SNAPSHOT.jar:/srv/gump/packages/antlr/antlr-3.1.3.jar:/srv/gump/public/workspace/apache-commons/beanutils/dist/commons-beanutils-20151118.jar:/srv

[Bug 58625] Failed to detect war change

https://bz.apache.org/bugzilla/show_bug.cgi?id=58625 loic.ou...@gmail.com changed: What|Removed |Added OS||All CC|

[Bug 58625] New: Failed to detect war change

https://bz.apache.org/bugzilla/show_bug.cgi?id=58625 Bug ID: 58625 Summary: Failed to detect war change Product: Tomcat 8 Version: 8.0.28 Hardware: PC Status: NEW Severity: normal Priority: P2

[Bug 58625] Failed to detect war change

https://bz.apache.org/bugzilla/show_bug.cgi?id=58625 --- Comment #1 from loic.ou...@gmail.com --- there is duplicate code in org.apache.catalina.startup.HostConfig : if (xml.exists() && unpackWARs && (!warTracker.exists() || warTracker.lastModified() ==

svn commit: r1715006 - in /tomcat/trunk/java/org/apache/catalina/mapper: Mapper.java MapperListener.java

Author: markt Date: Wed Nov 18 14:46:47 2015 New Revision: 1715006 URL: http://svn.apache.org/viewvc?rev=1715006=rev Log: Javadoc for mapper package Modified: tomcat/trunk/java/org/apache/catalina/mapper/Mapper.java tomcat/trunk/java/org/apache/catalina/mapper/MapperListener.java

[GUMP@vmgump]: Project tomcat-tc8.0.x-test-nio (in module tomcat-8.0.x) failed

To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project tomcat-tc8.0.x-test-nio has an issue affecting its community

[Bug 58624] Websocket send blocks indefinitely in FutureToSendHandler

https://bz.apache.org/bugzilla/show_bug.cgi?id=58624 --- Comment #4 from Barry Coughlan --- (In reply to Christopher Schultz from comment #3) > (In reply to Barry Coughlan from comment #2) > > My current working theory for what's happening is as follows: > > - Server