Re: [Proposal] Remove older of the two BIO AJP connectors
>> Ain't those used for 5.5? >> You can however just remove them from the build. >> Other option is to copy them to the 5.5 and not referencing >> the connectors for those set of classes. > > Sorry - should have been clear. I only meant in Tomcat 7. I didn't intend > changing 5.5.x or 6.0.x What's the state for Tomcat 7 ? I wonder if they're allready some discussions/plans about it. Not just technical/specs/RI plans but more generally what could/should Tomcat 7 be ? I could see that many projects (GWT/Eclipse), are now switching to Jetty (which is great container also). Did we miss something at some time ? May be being the Servlet/JSP RI didn't allow too much 'revolution'. Probably it didn't help/allow new peoples join the project and add some fresh air & ideas ? What's your opinion about it ? - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 46935] New: Problem with and Patch for Using the Correct Multicast Address in Tomcat 5.5.x
https://issues.apache.org/bugzilla/show_bug.cgi?id=46935
Summary: Problem with and Patch for Using the Correct Multicast
Address in Tomcat 5.5.x
Product: Tomcat 5
Version: 5.5.27
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Catalina:Cluster
AssignedTo: dev@tomcat.apache.org
ReportedBy: oli...@neofonie.de
Created an attachment (id=23425)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=23425)
Patch for binding the multicast socket to the correct address in 5.5.27
Hi,
when trying session replication using Apache Tomcat 5.5.27 and below, I came
across some problems, not unlike other people that tried to use the cluster
multicast membership service and TCP-based replication, as suggested in the
Clustering/Session Replication HOWTO
(http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html). I found numerous
reports from people having problems with clustering in 5.5, and although the
usual response to their inquiry for help was telling them to check their
configuration, I think there is a bug concerning clustering in 5.5 code which
has survived up to 5.5.27.
Although the 5.5.x Tomcat series is now somewhat obsolete, and this very
problem has been successfully addresses in 6.0.x (but obviously never been
backported to 5.5), I wanted to share what I found, because it might spare some
headache for users and might reconsile others with Tomcat session replication
altogether. :)
I am aware of the networking prerequisites for TCP Replication, most notably
caused by the Multicast Membership Service:
- multicast support both in the operating system's networking stack and the
network infrastructure altogether (like mentioned in The Clustering FAQ, see
http://wiki.apache.org/tomcat/FAQ/Clustering#Q9 , among many other web
locations)
- occassional problems with multicast routing on GNU/Linux (the OS of choice
for said setups)
- specific problems with GNU/Linux, Java, multicast and IPv6 support (as
discussed partially in
http://java.sun.com/j2se/1.5.0/docs/guide/net/ipv6_guide/index.html, although I
did not at all rely on IPv6 in my setup)
I tried several configurations in different network environments, always making
double-sure that multicast works (both using Java software and non-Java
software), and although the "Simple Cluster Configuration" from the Replication
HOWTO seemed to work for a while, more sophisticated setups regularly failed.
However, session replication in Tomcat 6.0.18 also worked in similar setups
that made 5.5.27 break. The usual symptoms where:
- multicast membership packages sent through the network (and also reaching the
network interfaces, although apparently not being received from the
application)
- no replicated sessions at all
- frequent exceptions in catalina.out like:
INFO Cluster-MembershipRecovery
org.apache.catalina.cluster.mcast.McastService - Membership recovery was
successful.
WARN Cluster-MembershipReceiver
org.apache.catalina.cluster.mcast.McastService - Error receiving mcast package
(errorCounter=10). Try Recovery!
java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at
java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
at
org.apache.catalina.cluster.mcast.McastServiceImpl.receive(McastServiceImpl.java:238)
at
org.apache.catalina.cluster.mcast.McastServiceImpl$ReceiverThread.run
(McastServiceImpl.java:330)
INFO Cluster-MembershipRecovery
org.apache.catalina.cluster.mcast.McastService - Cluster membership, running
recovery thread, multicasting is not functional.
WARN Cluster-MembershipSender
org.apache.catalina.cluster.mcast.McastService - Sender Thread ends with
errorCounter=0.
I finally compared the code snippets in Tomcat 6.0.18 and 5.5.27 that take care
of the membership service respectively and found this:
in org/apache/catalina/cluster/mcast/McastServiceImpl.java:167ff:
protected void setupSocket() throws IOException {
if (mcastBindAddress != null) socket = new MulticastSocket(new
java.net.
InetSocketAddress(mcastBindAddress, port));
else socket = new MulticastSocket(port);
socket.setLoopbackMode(false); //hint that we don't need loop back
messages
and in org/apache/catalina/tribes/membership/McastServiceImpl.java:185ff:
protected void setupSocket() throws IOException {
if (mcastBindAddress != null) {
try {
log.info("Attempting to bind the multicast socket to
"+address+":"+port);
socket = new MulticastSocket(new
InetSocketAddress(address,port));
} catch (BindException e) {
/*
* On
DO NOT REPLY [Bug 43641] Using the bind attribute for Membership tag causes Multicast to break
https://issues.apache.org/bugzilla/show_bug.cgi?id=43641 --- Comment #6 from Rainer Jung 2009-03-30 05:30:47 PST --- Proposed for backport to TC 5.5.x. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46935] Problem with and Patch for Using the Correct Multicast Address in Tomcat 5.5.x
https://issues.apache.org/bugzilla/show_bug.cgi?id=46935 Rainer Jung changed: What|Removed |Added Status|NEW |RESOLVED Resolution||DUPLICATE --- Comment #2 from Rainer Jung 2009-03-30 05:29:24 PST --- *** This bug has been marked as a duplicate of bug 43641 *** -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 43641] Using the bind attribute for Membership tag causes Multicast to break
https://issues.apache.org/bugzilla/show_bug.cgi?id=43641 Rainer Jung changed: What|Removed |Added CC||oli...@neofonie.de --- Comment #5 from Rainer Jung 2009-03-30 05:29:24 PST --- *** Bug 46935 has been marked as a duplicate of this bug. *** -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46935] Problem with and Patch for Using the Correct Multicast Address in Tomcat 5.5.x
https://issues.apache.org/bugzilla/show_bug.cgi?id=46935 --- Comment #1 from Rainer Jung 2009-03-30 05:29:03 PST --- Looks like I proposed the patch for backport 2 weeks ago :) Please have a look at http://svn.apache.org/viewvc?view=rev&revision=755351 http://svn.apache.org/viewvc?view=rev&revision=759692 http://svn.apache.org/viewvc?view=rev&revision=755310 http://svn.apache.org/viewvc?view=rev&revision=755312 The proposal needs one more vote for getting committed. If you think that this issue is not a duplicate of BZ43641, please comment. Grüße an die Neofonie ;) Rainer -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
Re: [Proposal] Remove older of the two BIO AJP connectors
Henri Gomez wrote: >>> Ain't those used for 5.5? >>> You can however just remove them from the build. >>> Other option is to copy them to the 5.5 and not referencing >>> the connectors for those set of classes. >> Sorry - should have been clear. I only meant in Tomcat 7. I didn't intend >> changing 5.5.x or 6.0.x > > What's the state for Tomcat 7 ? Development is happening in trunk. > I wonder if they're allready some discussions/plans about it. > > Not just technical/specs/RI plans but more generally what could/should > Tomcat 7 be ? /trunk/TOMCAT-7-RELEASE-PLAN.txt > I could see that many projects (GWT/Eclipse), are now switching to > Jetty (which is great container also). > > Did we miss something at some time ? Ease of embedding? Size? > May be being the Servlet/JSP RI didn't allow too much 'revolution'. Have you read the 3.0 spec draft? There is a fair amount of change. Whether it is good or not is a different question though. > Probably it didn't help/allow new peoples join the project and add > some fresh air & ideas ? We could probably be more responsive / encouraging. I am trying to get a couple of GSoC projects for Tomcat this year. Hopefully that will generate something. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
DO NOT REPLY [Bug 46939] New: SES url patterns cannot be defined in the servlet mappings
https://issues.apache.org/bugzilla/show_bug.cgi?id=46939 Summary: SES url patterns cannot be defined in the servlet mappings Product: Tomcat 6 Version: unspecified Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: lmaj...@gmail.com The majority of servlet containers let you define servlet-mappings that can reproduce SES (search engine safe) URL's. Example: http://myhost.com/index.jsp/myvar/value http://myhost.com/index.jsp/entry/hello--there This gives you the ability to create pretty ses url's without the need of an external rewrite tool like mod_rewrite or an ses valve. However, as I am aware of, only Tomcat does not allow these type of servlet mappings. jsp *.jsp/* The *.jsp/* is the one that chokes!! It cannot be defined and used. This to me is a bug as all servlet containers support this type of url-patterns. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46939] SES url patterns cannot be defined in the servlet mappings
https://issues.apache.org/bugzilla/show_bug.cgi?id=46939 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #1 from Mark Thomas 2009-03-30 10:14:53 PST --- The url pattern you quote is not supported by the servlet spec. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46939] SES url patterns cannot be defined in the servlet mappings
https://issues.apache.org/bugzilla/show_bug.cgi?id=46939 --- Comment #2 from Luis Majano 2009-03-30 10:16:44 PST --- So will it be supported in the future or it is something that will NEVER be supported? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46935] Problem with and Patch for Using the Correct Multicast Address in Tomcat 5.5.x
https://issues.apache.org/bugzilla/show_bug.cgi?id=46935 --- Comment #3 from Oliver Hillmann 2009-03-30 11:54:57 PST --- Too bad I have missed both the original Bug #43641, and your recent backport proposal. And although it is a pity I wasn't in first, I like seeing that this is (hopefully) getting into Tomcat 5.5.. ;) I don't want to get too much into nitpicking mode, but is this technically a duplicate? I see it has been addressed in 6.0, but this isn't really redundant, as long as it hasn't found its way into 5.5 - although I see it is basically the same issue. Looking forward to see the original backport included in 5.5.28. Regards - und viele Grüße zurück! :) Oliver -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46940] New: Console LOGOFF event signaled
https://issues.apache.org/bugzilla/show_bug.cgi?id=46940 Summary: Console LOGOFF event signaled Product: Tomcat 6 Version: 6.0.16 Platform: PC OS/Version: Windows Server 2003 Status: NEW Severity: critical Priority: P2 Component: Catalina AssignedTo: dev@tomcat.apache.org ReportedBy: amosl...@gmail.com Created an attachment (id=23428) --> (https://issues.apache.org/bugzilla/attachment.cgi?id=23428) this is the tomcat log My english is not good,thanks for read this. (1)Install a J2ee web application in windows server2003 as a serivice. (2)Start the service in windows. (3)After about two hours, tomcat write log "Console LOGOFF event signaled". (4)Then I find the server is "dead"(can not work normally). (5)But in windows, you can see the service is still display "started". (6)So,why tomcat wrote log "Console LOGOFF event signaled"? I think is abnormal. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
DO NOT REPLY [Bug 46940] Console LOGOFF event signaled
https://issues.apache.org/bugzilla/show_bug.cgi?id=46940 --- Comment #1 from amosl...@gmail.com 2009-03-30 20:39:37 PST --- I want to know, what can lead tomcat write "Console LOGOFF event signaled" in log? It looks like user didnot do anything afte start the service. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- 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
