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

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 Statu

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

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|

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 #

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=re

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

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

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|

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 -

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)

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:

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: