[Bug 56300] New: [Tribes] No useful examples, lack of documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=56300 Bug ID: 56300 Summary: [Tribes] No useful examples, lack of documentation Product: Tomcat 7 Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Documentation Assignee: dev@tomcat.apache.org Reporter: his.madnes...@gmail.com Created attachment 31422 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31422&action=edit Channel test according to documentation The only available documentation for tribes is http://tomcat.apache.org/tomcat-7.0-doc/tribes/introduction.html (where all sub pages are empty) The provided example 1) doesn't compile 2) produces Exception in thread "main" org.apache.catalina.tribes.ChannelException: No destination given; No faulty members identified. at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:202) at org.apache.catalina.tribes.group.GroupChannel.send(GroupChannel.java:182) at ChannelTest.main(ChannelTest.java:54) after making it compileable If one wants to use tribes in a cluster environment for custom message sharing, there are no usefull examples available in the documentation. It would be great to have some getting startet guides for common usage scenarios in using this (obviously very powerfull and performant, otherwise Tomcat would used it for internal clustering ;-) messaging framework. Of course you could checkout the sources from SVN and browse the tests and examples provided there, but a short and accurate documentation would definitely a better source for getting started with tribes. Regards Matthias -- 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 56300] [Tribes] No useful examples, lack of documentation
https://issues.apache.org/bugzilla/show_bug.cgi?id=56300 Matthias Müller changed: What|Removed |Added CC||his.madnes...@gmail.com -- 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
svn commit: r1580194 - /tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
Author: markt
Date: Sat Mar 22 11:12:53 2014
New Revision: 1580194
URL: http://svn.apache.org/r1580194
Log:
Make exception handling more robust - review by remm.
Modified:
tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
Modified: tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
URL:
http://svn.apache.org/viewvc/tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java?rev=1580194&r1=1580193&r2=1580194&view=diff
==
--- tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java (original)
+++ tomcat/trunk/java/org/apache/catalina/core/AsyncContextImpl.java Sat Mar 22
11:12:53 2014
@@ -112,11 +112,12 @@ public class AsyncContextImpl implements
// event.
try {
request.getResponse().finishResponse();
-} catch (IOException ioe) {
+} catch (Throwable t) {
+ExceptionUtils.handleThrowable(t);
// Catch this here and allow async context complete to continue
// normally so a dispatch takes place which ensures that the
// request and response objects are correctly recycled.
-log.debug(sm.getString("asyncContextImpl.finishResponseError"),
ioe);
+log.debug(sm.getString("asyncContextImpl.finishResponseError"), t);
}
}
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
svn commit: r1580195 - in /tomcat/tc7.0.x/trunk: ./ java/org/apache/catalina/core/AsyncContextImpl.java
Author: markt
Date: Sat Mar 22 11:13:58 2014
New Revision: 1580195
URL: http://svn.apache.org/r1580195
Log:
Make exception handling more robust - review by remm.
Modified:
tomcat/tc7.0.x/trunk/ (props changed)
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
Propchange: tomcat/tc7.0.x/trunk/
--
Merged /tomcat/trunk:r1580194
Modified:
tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
URL:
http://svn.apache.org/viewvc/tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/AsyncContextImpl.java?rev=1580195&r1=1580194&r2=1580195&view=diff
==
--- tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
(original)
+++ tomcat/tc7.0.x/trunk/java/org/apache/catalina/core/AsyncContextImpl.java
Sat Mar 22 11:13:58 2014
@@ -136,11 +136,12 @@ public class AsyncContextImpl implements
// event.
try {
request.getResponse().finishResponse();
-} catch (IOException ioe) {
+} catch (Throwable t) {
+ExceptionUtils.handleThrowable(t);
// Catch this here and allow async context complete to continue
// normally so a dispatch takes place which ensures that the
// request and response objects are correctly recycled.
-log.debug(sm.getString("asyncContextImpl.finishResponseError"),
ioe);
+log.debug(sm.getString("asyncContextImpl.finishResponseError"), t);
}
}
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
[Bug 56301] New: Websockets not working after this version
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 Bug ID: 56301 Summary: Websockets not working after this version Product: Tomcat 8 Version: 8.0.1 Hardware: PC Status: NEW Severity: blocker Priority: P2 Component: WebSocket Assignee: dev@tomcat.apache.org Reporter: cyril.aubur...@gmail.com Until 8.0.0-RC10 the classic hello-world websocket example (http://docs.oracle.com/javaee/7/tutorial/doc/websocket.htm) could 'work' (websocket fully connected). I use a basic example too in my project https://github.com/n11/mongo-cli-java, and noticed this issue when wanting to upgrade from 8.0.0-RC5 to 8.0.3 in pom.xml -- 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 56301] Websockets not working after this version
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 --- Comment #1 from n11 --- Created attachment 31423 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31423&action=edit screenshot websocket: not working, servlet: working -- 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 56301] Websockets not working after 8.0.0-RC10
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 n11 changed: What|Removed |Added Summary|Websockets not working |Websockets not working |after this version |after 8.0.0-RC10 OS||All -- 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 56301] Websockets not working after 8.0.0-RC10
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 --- Comment #2 from n11 --- note: I'm testing it from tomcat-embedded library, but I suppose this is not different when deploying on a tomcat 8.0.1 server -- 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 56301] Websockets not working after 8.0.0-RC10
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Mark Thomas --- This looks like a configuration problem. Bugzilla is not a support forum. Please use the Tomcat Users mailing list. -- 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 failure in ASF Buildbot on tomcat-trunk
The Buildbot has detected a new failure on builder tomcat-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tomcat-trunk/builds/5626 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-vm_ubuntu Build Reason: scheduler Build Source Stamp: [branch tomcat/trunk] 1580194 Blamelist: markt BUILD FAILED: failed compile_1 sincerely, -The Buildbot
[Bug 56301] Websockets not working after 8.0.0-RC10
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 --- Comment #4 from n11 --- Created attachment 31426 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31426&action=edit websocket tomcat 8.0.1 not working -- 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 56301] Websockets not working after 8.0.0-RC10
https://issues.apache.org/bugzilla/show_bug.cgi?id=56301 --- Comment #5 from n11 --- Created attachment 31427 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31427&action=edit websocket tomcat 8.0.0-RC10 -- 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 56304] New: WebSocket send locks and timeout does not occur after 20 seconds
https://issues.apache.org/bugzilla/show_bug.cgi?id=56304 Bug ID: 56304 Summary: WebSocket send locks and timeout does not occur after 20 seconds Product: Tomcat 7 Version: 7.0.52 Hardware: PC OS: Linux Status: NEW Severity: major Priority: P2 Component: Catalina Assignee: dev@tomcat.apache.org Reporter: rstoyanc...@yahoo.com Created attachment 31429 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31429&action=edit Extract from thread dump Start a WebSocket server on one computer. Connect from aonther using a browser. Starts sending messages from server to client periodically. Turn off wifi or unplug network cable on client side. Initially Tomcat appears to be sending messages but eventually one of the sends hangs indefinitely. The 20 second timeout as documented on the WebSocket FAQ does not occur and attempts to close the WebSocket session from another thread also locks that thread as well. If you now turn the wifi back on or plug the network cable, at last the two threads that are stuck are released and the WebSocket handler gets a notification of the session closing. In the attachment, the first two stack traces are of (1) the thread trying to send and (2) the thread that attempted to close. The 3rd stack trace is of another hung thread. NOTE that this does not occur on Tomcat 8 where the timout does occur and also attempts to close a session do succeed. Also I am told that the timeout does occur on Windows but I haven't verified it myself. I am using Linux. -- 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
