[Bug 56484] "null" in URI of unmounted path is sent to jboss

https://issues.apache.org/bugzilla/show_bug.cgi?id=56484 dkk changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 56491] attribute references do not resolve to their values

https://issues.apache.org/bugzilla/show_bug.cgi?id=56491 --- Comment #8 from Konstantin Kolinko --- (In reply to Christopher Schultz from comment #7) Reading jsp-2_2-mrel-spec.pdf 1) Chapter JSP.1.10.1 - page #51 (89 of 594) (in description of "isELIgnored" attribute of @page directive): [quot

[Bug 56492] Avoid eclipse debugger pausing on uncaught exceptions when tomcat renews its threads

https://issues.apache.org/bugzilla/show_bug.cgi?id=56492 --- Comment #3 from Sylvain Laurent --- (In reply to Christopher Schultz from comment #2) > My question would be why there is an exception thrown here to handle this > case at all. Instead, why not check to see if we should die cleanly, the

[Bug 56494] Changing AJP Connector properties (e.g. maxthreads) during runtime using JMX had no effect

https://issues.apache.org/bugzilla/show_bug.cgi?id=56494 --- Comment #2 from kiran --- Created attachment 31598 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31598&action=edit patch in diff -u format -- You are receiving this mail because: You are the assignee for the bug. ---

[Bug 56494] Changing AJP Connector properties (e.g. maxthreads) during runtime using JMX had no effect

https://issues.apache.org/bugzilla/show_bug.cgi?id=56494 --- Comment #1 from kiran --- Created attachment 31597 --> https://issues.apache.org/bugzilla/attachment.cgi?id=31597&action=edit Fixed ServiceMBean java file -- You are receiving this mail because: You are the assignee for the bug. --

[Bug 56494] New: Changing AJP Connector properties (e.g. maxthreads) during runtime using JMX had no effect

https://issues.apache.org/bugzilla/show_bug.cgi?id=56494 Bug ID: 56494 Summary: Changing AJP Connector properties (e.g. maxthreads) during runtime using JMX had no effect Product: Tomcat 7 Version: trunk Hardware: All

[Bug 56492] Avoid eclipse debugger pausing on uncaught exceptions when tomcat renews its threads

https://issues.apache.org/bugzilla/show_bug.cgi?id=56492 --- Comment #2 from Christopher Schultz --- My question would be why there is an exception thrown here to handle this case at all. Instead, why not check to see if we should die cleanly, then emit the recycling message to the log and simply

[Bug 56491] attribute references do not resolve to their values

https://issues.apache.org/bugzilla/show_bug.cgi?id=56491 --- Comment #7 from Christopher Schultz --- (In reply to Konstantin Kolinko from comment #4) > The " > If I remove that Doctype declaration, it starts working. > > This is expected, as Servlet 2.3 applications have no support for Expressi

Proposed patch for JDTCompiler

All, Konstantin Kolinko pointed out that some code in the JDTCompiler was particularly ugly, so I took a shot at improving it. Unfortunately, I don't have much experience with that component so I didn't want to commit anything. Can I get a review on this patch? I'm basically just replacing strin

[Bug 47323] Name clash: o.a.c.Manager class vs. o.a.c.manager package when compiling JSP

https://issues.apache.org/bugzilla/show_bug.cgi?id=47323 --- Comment #7 from Christopher Schultz --- (In reply to Konstantin Kolinko from comment #6) > > request the resource as a URI > > classLoader.getResource(packageName) > > I suspect that it can break compilation for JARs that contain only

[Bug 56451] JNDI lookups under java:comp/Resources do not access resources

https://issues.apache.org/bugzilla/show_bug.cgi?id=56451 --- Comment #4 from Mark Thomas --- I'm looking at this now. It appears that directory listings aren't handled correctly for aliases either (and don't appear to have been correct before r1592052 either. -- You are receiving this mail beca