id
int64 1
6.5k
| bug_id
int64 2.03k
426k
| summary
stringlengths 9
251
| description
stringlengths 1
32.8k
⌀ | report_time
stringlengths 19
19
| report_timestamp
int64 1B
1.39B
| status
stringclasses 6
values | commit
stringlengths 7
9
| commit_timestamp
int64 1B
1.39B
| files
stringlengths 25
32.8k
| project_name
stringclasses 6
values |
|---|---|---|---|---|---|---|---|---|---|---|
410 | 51,614 | Bug 51614 PersistentManager loads session from Store and calls session.expire() twice. | To check whether session is loaded into memory, StoreBase#processExpires calls findSession(id). ===== ... if (manager.findSession(keys[i]) != null) { isLoaded = true; } ... ===== However, PersistentManager#findSession(id) loads session from Store when there is no session in memory. Because session loaded from Store is an invalid session PersistentManager logs errorlog, calls session.expire(), and deletes session from Store. As a result, findSession(id) returns null, and isLoaded becomes false. And, session.expire() is called again, and the session is deleted from Store. If manager is PersistentManager, it is necessary to call PersistentManagerBase#isLoaded(id). However, to avoid regression of r1033024, other managers call findSession(id). Best regards. | 2011-08-04 11:19:47 | 1,312,470,000 | resolved fixed | 29e9966 | 1,312,460,000 | java/org/apache/catalina/session/StoreBase.java | Tomcat |
411 | 51,588 | Bug 51588 Change access modifiers in AccessLogValve to make it easier to extend | I'm adding some fields to a subclass of org.apache.catalina.valves.AccessLogValve but createLogElements() is the closest extension point available. Rather than reimplement the functionality there it would be preferable if both of the createAccessLogElement() methods were protected rather than private then it's a simple method of matching the char you want to use and falling back to super.createAccessLogElement(). | 2011-07-30 02:33:45 | 1,312,010,000 | resolved fixed | 77213bb | 1,312,130,000 | java/org/apache/catalina/valves/AccessLogValve.java | Tomcat |
412 | 51,586 | Bug 51586 ContextConfig.checkHandlesTypes() doesn't check for VerifyError when loading class | I've recently upgraded to Tomcat 7 and used to run with metadata-complete="true" in my web.xml. With Servlet 3 I decided I'd try some of the annotation features. When I turned off metadata-complete I got a VerifyError trying to load one of my classes. This class is meant to only work on Tomcat 6 so the fact Tomcat 7 cannot load this class is expected. What is not expected is that Tomcat 7 doesn't just ignore the error and continue scanning for annotations. Looking in ContextConfig.checkHandlesTypes() I checks for virtually every type of loading failure except VerifyError. Perhaps VerifyError should be added to this list? java.lang.VerifyError: class org.lds.stack.tomcat.decrypt.DecryptingStandardContext overrides final method start.()V at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1665) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1523) at org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2006) at org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:1969) at org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1858) at org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1826) at org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1812) at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1306) at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:896) at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:322) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89) at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5103) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:812) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:787) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:607) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:633) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:558) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:468) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1322) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:89) at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:379) at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:324) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1041) at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:774) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1033) at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:291) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.StandardService.startInternal(StandardService.java:443) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:727) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145) at org.apache.catalina.startup.Catalina.start(Catalina.java:621) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:450) | 2011-07-29 19:25:49 | 1,311,980,000 | resolved fixed | 0b340ac | 1,312,130,000 | java/org/apache/catalina/startup/ContextConfig.java | Tomcat |
413 | 51,557 | Bug 51557 Newline during a http header field name obscures next value | null | 2011-07-26 06:12:43 | 1,311,680,000 | resolved fixed | 6200dd9 | 1,311,760,000 | java/org/apache/coyote/http11/AbstractInputBuffer.java java/org/apache/coyote/http11/InternalAprInputBuffer.java java/org/apache/coyote/http11/InternalInputBuffer.java java/org/apache/coyote/http11/InternalNioInputBuffer.java test/org/apache/coyote/http11/TestInternalInputBuffer.java | Tomcat |
414 | 51,545 | Bug 51545 make threadname available in ExtendedAccessLogValve | null | 2011-07-23 09:07:02 | 1,311,430,000 | resolved fixed | 00a1fdf | 1,311,670,000 | java/org/apache/catalina/valves/ExtendedAccessLogValve.java | Tomcat |
415 | 51,555 | Bug 51555 An invalid Lifecycle transition ([before_stop]) for component in state [INITIALIZED]: MapperListener | null | 2011-07-25 21:40:38 | 1,311,640,000 | resolved fixed | 95d67fe | 1,311,670,000 | java/org/apache/catalina/Lifecycle.java java/org/apache/catalina/util/LifecycleBase.java | Tomcat |
416 | 41,709 | Bug 41709 When calling the API that relates to the buffer after the response is committed, ISE with no messages is thrown. | After the response is committed, following API throws IllegalStateException. It's O.K. but the message of the exception is not set. - HttpServletResponse#resetBuffer - HttpServletResponse#sendError - HttpServletResponse#sendRedirect - HttpServletResponse#setBufferSize To understand the bug of the application, it is hoped that the message is set like other exceptions. | 2007-02-26 17:43:51 | 1,172,530,000 | resolved fixed | 8baaa98 | 1,311,360,000 | java/org/apache/catalina/connector/ResponseFacade.java | Tomcat |
417 | 51,056 | Bug 51056 Disable / drop support for SSLv2 | null | 2011-04-13 14:12:26 | 1,302,720,000 | resolved fixed | 4d9fcc0 | 1,311,240,000 | java/org/apache/tomcat/jni/SSL.java | Tomcat |
418 | 51,532 | Bug 51532 Performance Issue when retriving JAR files during TLD file parsing. | null | 2011-07-19 21:47:15 | 1,311,130,000 | resolved fixed | bcee77d | 1,311,190,000 | java/org/apache/jasper/compiler/Compiler.java | Tomcat |
419 | 51,509 | Bug 51509 Csrf Prevention Filter's LruCache is not thread save | The LruCache (org.apache.catalina.filters.CsrfPreventionFilter$LruCache) use by Csrf Prevention Filter is base on LinkedHashMap. From the LinkedHashMap Java Doc: Note that this implementation is not synchronized. If multiple threads access a linked hash map concurrently, and at least one of the threads modifies the map structurally, it must be synchronized externally. ... But the LruCache implementation does not synchronize the access to the map. | 2011-07-14 14:54:22 | 1,310,670,000 | resolved fixed | 400745e | 1,311,100,000 | java/org/apache/catalina/filters/CsrfPreventionFilter.java test/org/apache/catalina/filters/TestCsrfPreventionFilter2.java | Tomcat |
420 | 51,518 | Bug 51518 "/absolute-ordering/name/others" should not include "name" element | method: org.apache.catalina.startup.WebRuleSet.addRuleInstances(Digester digester) code: ==================================================== digester.addCallMethod(fullPrefix + "/absolute-ordering/name/others", "addAbsoluteOrderingOthers"); ==================================================== web-common_3_0.xsd ==================================================== <xsd:complexType name="absoluteOrderingType"> <xsd:annotation> <xsd:documentation> Please see section 8.2.2 of the specification for details. </xsd:documentation> </xsd:annotation> <xsd:choice minOccurs="0" maxOccurs="unbounded"> <xsd:element name="name" type="javaee:java-identifierType" minOccurs="0" maxOccurs="unbounded"/> <xsd:element name="others" type="javaee:ordering-othersType" minOccurs="0" maxOccurs="1"/> </xsd:choice> </xsd:complexType> ==================================================== | 2011-07-17 01:22:30 | 1,310,880,000 | resolved fixed | 5de2739 | 1,311,080,000 | java/org/apache/catalina/startup/WebRuleSet.java | Tomcat |
421 | 49,595 | Bug 49595 Tomcat crashes in tcnative-1.dll frequently | null | 2010-07-15 06:34:41 | 1,279,190,000 | resolved fixed | a3f3379 | 1,311,060,000 | java/org/apache/coyote/ajp/AjpAprProcessor.java | Tomcat |
422 | 51,503 | Bug 51503 Additional error checking required for connector port attribute (e.g. for port="") | With 7.0.18 packaged as a candidate for release and finally unreleased, when I stop the Tomcat service (only 1 war deployed), the service takes a lot of time to stop and finally was killed by system. Having a look into the stderr log, I see it paused right after the folowing line : INFO: Stopping ProtocolHandler [http-apr-0] Then went into a slow loop and fill the log with these lines : 13 juil. 2011 14:30:30 org.apache.tomcat.util.net.AprEndpoint stopInternal ATTENTION: Acceptor thread [http-apr-0-Acceptor-0] failed to unlock. Forcing hard socket shutdown. 13 juil. 2011 14:30:31 org.apache.tomcat.util.net.AprEndpoint stopInternal ATTENTION: Acceptor thread [http-apr-0-Acceptor-0] failed to unlock. Forcing hard socket shutdown. 13 juil. 2011 14:30:32 org.apache.tomcat.util.net.AprEndpoint stopInternal ATTENTION: Acceptor thread [http-apr-0-Acceptor-0] failed to unlock. Forcing hard socket shutdown. etc. (about 30 times before it was killed) I think there was no such issue with 7.0.16. | 2011-07-13 12:40:11 | 1,310,580,000 | resolved fixed | 1e79993 | 1,311,010,000 | java/org/apache/catalina/connector/Connector.java | Tomcat |
423 | 51,477 | Bug 51477 Support all protocol combinations in SSLProtocol of APR Connector | null | 2011-07-05 16:53:25 | 1,309,900,000 | resolved fixed | 6ee5a22 | 1,310,400,000 | java/org/apache/tomcat/jni/Library.java java/org/apache/tomcat/util/net/AprEndpoint.java | Tomcat |
424 | 46,252 | Bug 46252 Tomcat access log doesn't support Unicode | AccessLogValve, which is responsible for handling the access log uses FileWriter (that doesn't support Unicode). I guess that instantiating the writer like this would solve the case: writer = new PrintWriter(new OutputStreamWriter(new FileOutputStream(pathname), "UTF-8"), true); | 2008-11-20 11:18:55 | 1,227,200,000 | resolved fixed | 871dabd | 1,310,400,000 | java/org/apache/catalina/valves/AccessLogValve.java | Tomcat |
425 | 51,494 | Bug 51494 NPE in StandardContextValve.invoke() when a webapp is redeployed while a request is still being processed | null | 2011-07-10 01:56:23 | 1,310,280,000 | resolved fixed | 3a95db4 | 1,310,390,000 | java/org/apache/catalina/core/StandardContextValve.java | Tomcat |
426 | 51,475 | Bug 51475 GzipInterceptor#decompress is not completly implemented | null | 2011-07-05 09:58:12 | 1,309,870,000 | resolved fixed | acc5619 | 1,309,880,000 | java/org/apache/catalina/tribes/group/interceptors/GzipInterceptor.java test/org/apache/catalina/tribes/group/interceptors/TestGzipInterceptor.java | Tomcat |
427 | 51,473 | Bug 51473 SecurityConfig,set "package.definition" security property to "nullsun.,java.,..." | null | 2011-07-05 05:37:09 | 1,309,860,000 | resolved fixed | ec00abf | 1,309,850,000 | java/org/apache/catalina/security/SecurityConfig.java | Tomcat |
428 | 51,467 | Bug 51467 usage of method run instead of start to start a thread | In StandardContext method Thread#run is used. This is most probably a mistake, since a few lines below Thread#join is called to wait for the completion of the thread. So we could either remove the join and get rid of the thread by using just a runnable, or start the thread. | 2011-07-03 10:19:46 | 1,309,700,000 | resolved fixed | eb98373 | 1,309,780,000 | java/org/apache/catalina/core/StandardContext.java | Tomcat |
429 | 51,466 | Bug 51466 typos in comments of HostManagerServlet | null | 2011-07-02 14:09:02 | 1,309,630,000 | resolved fixed | 6020bf6 | 1,309,780,000 | java/org/apache/catalina/manager/host/HostManagerServlet.java | Tomcat |
430 | 51,453 | Bug 51453 Requests to open URL that include an Authorization header do not reach servlet | In Tomcat 7, I've noticed that a request to a URL that does not require authentication will get forwarded to the login page if the request contains an "Authorization" header. Our application expects these requests to be processed by the servlet. The servlet parses the Authorization header and takes appropriate action (possibly redirecting to the login page or allowing the request if the headers contain an acceptible token). This has worked in older versions of Tomcat. The relevant part of our web.xml looks like: <security-constraint> <web-resource-collection> <web-resource-name>open</web-resource-name> <url-pattern>/*</url-pattern> <!-- several other url patterns --> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> <!-- Notice no auth-constraint element --> </security-constraint> I observed the behavior of org.apache.catalina.authenticator.AuthenticatorBase.invoke(), here's what I saw: The constraints variable contains a single constraint that matches the security constraint from our web.xml above. On line 520, authRequired is set to true because of the presence of the Authorization header. The authenticate() call on line 535 fails and redirects to the login page. | 2011-06-30 14:10:50 | 1,309,460,000 | resolved fixed | df9bc17 | 1,309,450,000 | java/org/apache/catalina/authenticator/AuthenticatorBase.java | Tomcat |
431 | 51,088 | Bug 51088 ArrayIndexOutOfBoundsException from org.apache.el.parser.JJTELParserState | I found the following ArrayIndexOutOfBoundsException in my logfile. It occurred directly after login into my webApp without any further user interaction. Unfortunately it is not reproducible at all. I am not sure whether Jasper is the right component. However the class JJTELParserState is in the jasper-el.jar. Environment: Tomcat 6.0.32 Facelets 1.1.14 Myfaces 1.2.9 SCHWERWIEGEND: Error Rendering View[/facelets/myview.xhtml] java.lang.ArrayIndexOutOfBoundsException: -1 at java.util.ArrayList.remove(ArrayList.java:390) at org.apache.el.parser.JJTELParserState.closeNodeScope(JJTELParserState.java:108) at org.apache.el.parser.ELParser.CompositeExpression(ELParser.java:74) at org.apache.el.lang.ExpressionBuilder.createNodeInternal(ExpressionBuilder.java:115) at org.apache.el.lang.ExpressionBuilder.build(ExpressionBuilder.java:172) at org.apache.el.lang.ExpressionBuilder.createValueExpression(ExpressionBuilder.java:216) at org.apache.el.ExpressionFactoryImpl.createValueExpression(ExpressionFactoryImpl.java:68) at com.sun.facelets.el.ELText$ELTextVariable.apply(ELText.java:161) at com.sun.facelets.compiler.AttributeInstruction.apply(AttributeInstruction.java:60) at com.sun.facelets.compiler.UIInstructionHandler.apply(UIInstructionHandler.java:95) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jstl.core.IfHandler.apply(IfHandler.java:54) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:360) at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:190) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:360) at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:190) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:360) at org.apache.myfaces.custom.aliasbean.AliasBeansScopeTagHandler.applyNextHandler(AliasBeansScopeTagHandler.java:52) at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:190) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:124) at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:39) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140) at com.sun.facelets.tag.ui.IncludeHandler.apply(IncludeHandler.java:66) at com.sun.facelets.tag.ui.DefineHandler.applyDefinition(DefineHandler.java:64) at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:136) at com.sun.facelets.impl.DefaultFaceletContext$TemplateManager.apply(DefaultFaceletContext.java:337) at com.sun.facelets.impl.DefaultFaceletContext.includeDefinition(DefaultFaceletContext.java:307) at com.sun.facelets.tag.ui.InsertHandler.apply(InsertHandler.java:68) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:360) at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:190) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.jsf.ComponentHandler.applyNextHandler(ComponentHandler.java:360) at com.sun.facelets.tag.jsf.ComponentHandler.apply(ComponentHandler.java:190) at com.sun.facelets.tag.CompositeFaceletHandler.apply(CompositeFaceletHandler.java:47) at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:124) at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:39) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:248) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:294) at com.sun.facelets.impl.DefaultFacelet.include(DefaultFacelet.java:273) at com.sun.facelets.impl.DefaultFaceletContext.includeFacelet(DefaultFaceletContext.java:140) at com.sun.facelets.tag.ui.CompositionHandler.apply(CompositionHandler.java:116) at com.sun.facelets.compiler.NamespaceHandler.apply(NamespaceHandler.java:49) at com.sun.facelets.compiler.EncodingHandler.apply(EncodingHandler.java:39) at com.sun.facelets.impl.DefaultFacelet.apply(DefaultFacelet.java:95) at com.sun.facelets.FaceletViewHandler.buildView(FaceletViewHandler.java:596) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.java:651) at org.ajax4jsf.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:100) at org.ajax4jsf.application.AjaxViewHandler.renderView(AjaxViewHandler.java:176) at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:41) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:140) at org.apache.myfaces.custom.ppr.PPRLifecycleWrapper.render(PPRLifecycleWrapper.java:84) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:187) at com.foo..client.web.servlets.FacesServletWrapper.service(FacesServletWrapper.java:125) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:206) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:392) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.foo..client.web.filters.LoginFilter.doFilter(LoginFilter.java:219) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.foo..client.web.filters.CacheFilter.doFilter(CacheFilter.java:110) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.foo..client.web.filters.EncodingFilter.doFilter(EncodingFilter.java:54) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.foo..client.web.filters.TimerFilter.doFilter(TimerFilter.java:80) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:662) | 2011-04-20 05:42:42 | 1,303,290,000 | resolved wontfix | 92af111 | 1,309,360,000 | java/org/apache/el/lang/ExpressionBuilder.java | Tomcat |
432 | 51,436 | Bug 51436 ServletRequestListener fails to access request parameters when an Expect-Header is sent | null | 2011-06-27 09:56:45 | 1,309,180,000 | resolved fixed | 6dffc54 | 1,309,280,000 | java/org/apache/catalina/core/StandardContextValve.java java/org/apache/catalina/core/StandardWrapperValve.java | Tomcat |
433 | 50,353 | Bug 50353 Calling asyncContext.getResponse() returns null after async timeout | If the async thread calls asyncContext.getResponse() after the async timeout, it gets a null reference. In the following example, it leads to a NPE. The servlet spec is not very clear on the behavior to adopt after a timeout, but I don't think null should be returned. Maybe an IllegalStateException instead ? It seems to be the case if complete() is called after the timeout. package test; import java.io.IOException; import java.io.PrintWriter; import javax.servlet.AsyncContext; import javax.servlet.AsyncEvent; import javax.servlet.AsyncListener; import javax.servlet.ServletException; import javax.servlet.ServletResponse; import javax.servlet.annotation.WebServlet; import javax.servlet.http.HttpServlet; import javax.servlet.http.HttpServletRequest; import javax.servlet.http.HttpServletResponse; /** * Servlet implementation class MyServlet */ @WebServlet(value = "/MyServlet", asyncSupported = true) public class MyServlet extends HttpServlet implements AsyncListener { private static final long serialVersionUID = 1L; protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { final AsyncContext asyncContext = request.startAsync(request, response); asyncContext.addListener(this); asyncContext.setTimeout(10*1000); asyncContext.start(new Runnable() { @Override public void run() { System.out.println("Entering async thread"); try { Thread.sleep(20 * 1000); System.out.println("<Asyncthread> about to write response"); ServletResponse response2 = asyncContext.getResponse(); PrintWriter writer = response2.getWriter(); writer.write("Hello world"); System.out.println("<Asyncthread> about to complete"); asyncContext.complete(); } catch (Exception e) { e.printStackTrace(); } } }); } @Override public void onComplete(AsyncEvent evt) throws IOException { System.out.println("onComplete " + evt); } @Override public void onError(AsyncEvent evt) throws IOException { System.out.println("onError " + evt); } @Override public void onStartAsync(AsyncEvent evt) throws IOException { System.out.println("onStartAsync " + evt); } @Override public void onTimeout(AsyncEvent evt) throws IOException { System.out.println("onTimeout " + evt); evt.getAsyncContext().getResponse().getWriter().write("Timed out"); evt.getAsyncContext().complete(); } } | 2010-11-27 17:45:41 | 1,290,900,000 | resolved fixed | d36c5d9 | 1,309,280,000 | java/org/apache/catalina/core/AsyncContextImpl.java | Tomcat |
434 | 51,447 | Bug 51447 Session type changes from Backup to Primary | null | 2011-06-28 11:15:18 | 1,309,270,000 | resolved fixed | 3d85a85 | 1,309,280,000 | java/org/apache/catalina/manager/HTMLManagerServlet.java | Tomcat |
435 | 51,418 | Bug 51418 Allow more flexibility in adding webapps to org.apache.catalina.startup.Tomcat | null | 2011-06-22 15:54:00 | 1,308,770,000 | resolved fixed | f83c07e | 1,308,770,000 | java/org/apache/catalina/startup/Tomcat.java | Tomcat |
436 | 51,403 | Bug 51403 Avoid NullPointerException in JULI FileHandler if formatter is misconfigured | If formatter assigned to org.apache.juli.FileHandler in logging.properties is misconfigured and fails to load, the FileHandler starts without formatter and fails with an NPE later. To reproduce: assign some bogus value to 1catalina.org.apache.juli.FileHandler.formatter When Tomcat starts, the following will be printed at the console: java.util.logging.ErrorManager: 4 java.lang.NullPointerException at org.apache.juli.FileHandler.openWriter(FileHandler.java:377) at org.apache.juli.FileHandler.<init>(FileHandler.java:99) at org.apache.juli.FileHandler.<init>(FileHandler.java:90) I think we can be more tolerant to this configuration error and fall back to the default formatter. I will commit a fix shortly. | 2011-06-21 13:13:00 | 1,308,680,000 | resolved fixed | f2dd57b | 1,308,660,000 | java/org/apache/juli/FileHandler.java | Tomcat |
437 | 51,401 | Bug 51401 java.lang.IllegalArgumentException: <session-config> element is limited to 1 occurrence | null | 2011-06-21 01:36:08 | 1,308,630,000 | resolved fixed | 7c274bb | 1,308,650,000 | java/org/apache/catalina/startup/WebRuleSet.java | Tomcat |
438 | 51,396 | Bug 51396 Embedding class cannot launch a webapp with a jsp servlet | null | 2011-06-20 17:02:09 | 1,308,600,000 | resolved fixed | f75418b | 1,308,610,000 | java/org/apache/catalina/startup/ContextConfig.java test/org/apache/catalina/startup/TestContextConfig.java | Tomcat |
439 | 49,165 | Bug 49165 Enhancement - Allow %{TIME_FORMAT}t As Configuration for AccessLogValve | AccessLogValve.DateAndTimeElement() can currently be configured only with %t which output the date/time in Common Log Format. By adding the capability to configure with %{TIME_FORMAT}, one could override (at least) the timeFormatter property of the class ... or it could go further and allow overriding of all the [day, month, year, time]Formatter properties. Justification for enhancement: The log currenlty provide the ability to log processing time in millis (via %T), but an accurate log of the order in which requests are received cannot be determined without the capabilities of logging a a format with milliseconds using the %t element. | 2010-04-21 14:20:08 | 1,271,870,000 | resolved fixed | 7d6c439 | 1,308,480,000 | java/org/apache/catalina/valves/AccessLogValve.java | Tomcat |
440 | 51,386 | Bug 51386 @HandlingType not correctly handled at server startup leads to incorrect classes set passed to initializers | null | 2011-06-16 14:12:27 | 1,308,250,000 | resolved fixed | 9f8b983 | 1,308,240,000 | java/org/apache/catalina/startup/ContextConfig.java test/org/apache/catalina/startup/TestContextConfigAnnotation.java | Tomcat |
441 | 48,956 | Bug 48956 SSI regular expressions not working | null | 2010-03-22 11:48:29 | 1,269,270,000 | resolved fixed | 874048a | 1,308,180,000 | java/org/apache/catalina/ssi/ExpressionParseTree.java | Tomcat |
442 | 43,538 | Bug 43538 [patch] Show the hostname and IP address in the manager webapp | We have an environment with a couple of load-balanced Tomcats fronted by httpd. If someone accesses the manager application through the load-balancer, they will not know which of the load-balanced Tomcats they end up at. In these situations, and others as well, it would be nice if the manager could tell the hostname and IP address of the machine it is running on. | 2007-10-02 14:42:39 | 1,191,350,000 | resolved fixed | 2b8e6cf | 1,308,180,000 | java/org/apache/catalina/manager/Constants.java java/org/apache/catalina/manager/HTMLManagerServlet.java java/org/apache/catalina/manager/StatusManagerServlet.java | Tomcat |
443 | 51,306 | Bug 51306 NPE in DeltaRequest.writeExternal(DeltaRequest.java:267) when handling remote session expiration | Occasionally we got errors like following: ====== 2011-05-30 03:40:17,697 ERROR [pool-1-thread-2] (org.apache.catalina.ha.session.DeltaManager) Manager [localhost#]: Unable to receive message through TCP channel java.lang.NullPointerException at java.io.ObjectOutputStream$BlockDataOutputStream.getUTFLength(ObjectOutputStream.java:2106) at java.io.ObjectOutputStream$BlockDataOutputStream.writeUTF(ObjectOutputStream.java:1977) at java.io.ObjectOutputStream.writeUTF(ObjectOutputStream.java:849) at org.apache.catalina.ha.session.DeltaRequest.writeExternal(DeltaRequest.java:267) at org.apache.catalina.ha.session.DeltaRequest.serialize(DeltaRequest.java:287) at org.apache.catalina.ha.session.DeltaManager.serializeDeltaRequest(DeltaManager.java:716) at org.apache.catalina.ha.session.DeltaManager.requestCompleted(DeltaManager.java:1224) at org.apache.catalina.ha.session.DeltaSession.expire(DeltaSession.java:403) at org.apache.catalina.ha.session.DeltaManager.handleSESSION_EXPIRED(DeltaManager.java:1546) at org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager.java:1452) at org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaManager.java:1173) at org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(ClusterSessionListener.java:92) at org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:901) at org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:882) at org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChannel.java:269) at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79) at org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:110) at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79) at org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79) at org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:241) at org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:225) at org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:188) at org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:91) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) It looks like the functionality of Tomcat is not affected by this. The NPE comes from trying to write null sessionId, but why does Tomcat try to send something from handling received authoritative SESSION_EXPIRED message? | 2011-06-01 12:21:28 | 1,306,950,000 | resolved fixed | 4e5571f | 1,307,960,000 | java/org/apache/catalina/ha/session/DeltaManager.java java/org/apache/catalina/ha/session/DeltaSession.java | Tomcat |
444 | 51,348 | Bug 51348 Potential NullPointerException in org.apache.catalina.servlets.WebdavServlet at line 1336 | A WebDAV LOCK_REFRESH request may cause a NullPointerException because of an (IMHO) wrong check at line 1332 in WebdavServlet.java 1056763 2011-01-08 18:56:57Z markt. I suggest line 1332 should be: ... if (toRenew != null) { ... | 2011-06-09 08:53:41 | 1,307,620,000 | resolved fixed | 71b18c8 | 1,307,650,000 | java/org/apache/catalina/servlets/WebdavServlet.java | Tomcat |
445 | 51,344 | Bug 51344 org.apache.catalina.startup.Embedded overrides Lifecycle incorrectly? | Not sure if this is a bug or just my mis-coding... I've been using the Embedded component in Tomcat 6.0.29 for integration testing. Something like this: server = new EmbeddedTomcat("/test", 7890, "JVM-1"); PeerToPeerCacheLifecycleListener p2pListener = new PeerToPeerCacheLifecycleListener(); p2pListener.setProperty("mcast-port", "19991"); server.getEmbedded().addLifecycleListener(p2pListener); sessionManager = new DeltaSessionManager(); server.getRootContext().setManager(sessionManager); Here the EmbeddedTomcat class is simply a wrapper for Embedded - I'm passing in the context, port and 'JVM route' - nothing special. Then I add a listener which should be the programmatic equivalent of having the following server.xml snippet: <Server> <Listener className="PeerToPeerCacheLifecycleListener"/> </Server> DeltaSessionManager performs custom session management and thus extends ManagerBase and implements Lifecycle and SessionManager. During the start of DeltaSessionManager I initialize the listener by doing this.lifecycle.fireLifecycleEvent(START_EVENT, null); The listener picks up this event and starts. All works nicely under Tomcat 6, but breaks under Tomcat 7.0.12. My initial investigation shows that the LifecycleEvent, being fired, is not reaching the Embedded component which is where the listener is registered. Removing the overridden Lifecycle methods from Embedded (so that the Lifecyle processing happens in LifecycleBase) seems to work as the triggered event then reaches my listener. | 2011-06-08 21:35:55 | 1,307,580,000 | resolved fixed | 4892b57 | 1,307,650,000 | java/org/apache/catalina/startup/Embedded.java | Tomcat |
446 | 51,340 | Bug 51340 Intermittent java.lang.IllegalArgumentException: <session-config> element is limited to 1 occurrence | null | 2011-06-08 13:37:25 | 1,307,550,000 | resolved fixed | 1fe28a6 | 1,307,550,000 | java/org/apache/catalina/startup/ContextConfig.java | Tomcat |
447 | 51,324 | Bug 51324 When OutputBuffer.doFlush gets Exception, doFlush gets stuck to true | null | 2011-06-05 05:17:12 | 1,307,270,000 | resolved fixed | 1bbbdb2 | 1,307,460,000 | java/org/apache/catalina/connector/OutputBuffer.java | Tomcat |
448 | 51,251 | Bug 51251 Patch to add version parameter to ant task | null | 2011-05-24 01:28:35 | 1,306,210,000 | resolved fixed | d19daf5 | 1,307,140,000 | java/org/apache/catalina/ant/AbstractCatalinaCommandTask.java java/org/apache/catalina/ant/ReloadTask.java java/org/apache/catalina/ant/SessionsTask.java java/org/apache/catalina/ant/StartTask.java java/org/apache/catalina/ant/StopTask.java java/org/apache/catalina/ant/UndeployTask.java | Tomcat |
449 | 51,276 | Bug 51276 Startup time is too high if there are few JARs in "lib/" and a few webapps. | Startup time in tomcat 7.0.14 is 10x higher than 7.0.12, if there are a few shared JARs in tomcat/lib and a few webapps. The issue is very simple to reproduce, simply add 10 empty directories in tomcat/webapps and (for example) the Metro webservices jars in tomcat/lib. On my machine the startup time increase from 0.5 secs (default installation) to 35.2 secs. When using tomcat 7.0.12 the startup time is about 3 secs on my machine in this test case. | 2011-05-27 11:09:03 | 1,306,510,000 | resolved fixed | 5109678 | 1,307,010,000 | java/org/apache/catalina/startup/ContextConfig.java java/org/apache/catalina/startup/TldConfig.java java/org/apache/jasper/compiler/TldLocationsCache.java java/org/apache/tomcat/util/scan/FileUrlJar.java java/org/apache/tomcat/util/scan/Jar.java java/org/apache/tomcat/util/scan/JarFactory.java java/org/apache/tomcat/util/scan/UrlJar.java | Tomcat |
450 | 51,277 | Bug 51277 NPE during the form authentication when form-login-config is missed | null | 2011-05-27 12:04:07 | 1,306,510,000 | resolved fixed | 5b0919c | 1,306,850,000 | java/org/apache/catalina/authenticator/FormAuthenticator.java | Tomcat |
451 | 51,240 | Bug 51240 maxConnections not honors config when acceptorThreadCount > 1 | null | 2011-05-22 19:22:26 | 1,306,110,000 | resolved fixed | 73f9592 | 1,306,420,000 | java/org/apache/tomcat/util/net/AbstractEndpoint.java java/org/apache/tomcat/util/net/AprEndpoint.java java/org/apache/tomcat/util/net/JIoEndpoint.java java/org/apache/tomcat/util/net/NioEndpoint.java java/org/apache/tomcat/util/threads/CounterLatch.java java/org/apache/tomcat/util/threads/LimitLatch.java test/org/apache/tomcat/util/threads/TestCounterLatch.java test/org/apache/tomcat/util/threads/TestLimitLatch.java | Tomcat |
452 | 51,226 | Bug 51226 [Patch] to add FindLeaks ant task | There is no ant task for FindLeaks. | 2011-05-19 06:26:15 | 1,305,800,000 | resolved fixed | 1cd5e7b | 1,306,250,000 | java/org/apache/catalina/ant/FindLeaksTask.java java/org/apache/catalina/manager/HTMLManagerServlet.java java/org/apache/catalina/manager/ManagerServlet.java | Tomcat |
453 | 27,122 | Bug 27122 IE plugins cannot access components through Tomcat 5 over SSL | SSL seems to be failing when the Content-Type header is set to "image/svg+xml". I've only seen this failure when SSL was running on a Solaris machine. (uname -a: SunOS [hostname removed] 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-60) When attempted on Windows, we were unable to duplicate the error. This reliably fails when attempted on this specific Solaris machine. If I get a chance, I'll try to create a test-case and see if I can reproduce this on other Solaris machines. Unfortunately, this was a show-stopper for a release that's being made today so I'm pressed for time. Basically, what happens is that we're using a JSP page to create an SVG file. Because of this, we have to set the Content-Type header to "image/svg+xml". When the MIME type is set to this value, the page fails to load in Internet Explorer 6 (SP1) with a message of "connection failed" or something similar. When an attempt was made in Opera, Opera responded by crashing. Mozilla successfully downloaded the file, though. However, when resetting the MIME type in the page to "text/plain" all three browsers can access the page without failure. By back-revving Tomcat to version 4.1.29, we were able to resolve this issue and access the page in all three browsers. I'll try and create a test-case later today and verify that it isn't just our SVG JSP that's failing but any that creates SVG but I'm currently pressed for time - sorry. | 2004-02-20 21:09:17 | 1,077,330,000 | resolved fixed | 4161179 | 1,306,100,000 | java/org/apache/catalina/authenticator/AuthenticatorBase.java | Tomcat |
454 | 51,185 | Bug 51185 Performance : DataSourceProxy#createPool should use more fine grained synchronisation | null | 2011-05-11 10:21:44 | 1,305,120,000 | resolved fixed | 4bdd8d0 | 1,305,930,000 | modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/DataSourceProxy.java | Tomcat |
455 | 35,054 | Bug 35054 warn if appBase is not existing as a File or directory | otherwise, it may very hard to find what is wrong | 2005-05-25 10:03:08 | 1,117,030,000 | resolved fixed | 9bb6e4f | 1,305,920,000 | java/org/apache/catalina/startup/HostConfig.java | Tomcat |
456 | 51,220 | Bug 51220 Add system property that makes it possible for jsp pages with the extends page directive to take advantage of tag pooling | null | 2011-05-18 15:42:54 | 1,305,750,000 | resolved fixed | c46e56c | 1,305,800,000 | java/org/apache/jasper/compiler/Generator.java | Tomcat |
457 | 51,229 | Bug 51229 Some async examples are not work correctly | null | 2011-05-19 06:55:54 | 1,305,800,000 | resolved fixed | 55d8b72 | 1,305,800,000 | webapps/examples/WEB-INF/classes/async/Async0.java | Tomcat |
458 | 51,212 | Bug 51212 QueryStats has synchornisation issues | null | 2011-05-17 16:25:52 | 1,305,660,000 | resolved fixed | b24b17c | 1,305,740,000 | modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/interceptor/SlowQueryReport.java | Tomcat |
459 | 51,208 | Bug 51208 SVN TRUNK : JDBC interceptor options are not taken into account | null | 2011-05-17 09:14:29 | 1,305,640,000 | resolved fixed | 2bb247a | 1,305,640,000 | modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/PoolProperties.java | Tomcat |
460 | 51,156 | Bug 51156 "Expire sessions" button not visible for context configured in server.xml | If app is configured in server.xml like this: {code} <Host name="www.myapp.pl" appBase="/usr/lib/tomcat/webapps" unpackWARs="false" autoDeploy="false" xmlValidation="false" xmlNamespaceAware="false" > <Context docBase="/var/www/myapp" path="" cacheMaxSize="5120" cacheTTL="60000" cachingAllowed="true" > </Context> <Context path="/manager" privileged="true" docBase="/usr/lib/tomcat/webapps/manager"> </Context> </Host> {code} In Tomcat Manager, on the application list, there is a button "Expire sessions" available only for "/manager" application. There is no button "Expire sessions" for "/" path. I think bug is in HTMLManagerServlet.java in this part: {code} if (context.getPath().equals(this.context.getPath())) { writer.print(MessageFormat.format( MANAGER_APP_ROW_BUTTON_SECTION, args)); } else if (context.getAvailable() && isDeployed) { writer.print(MessageFormat.format( STARTED_DEPLOYED_APPS_ROW_BUTTON_SECTION, args)); } else if (context.getAvailable() && !isDeployed) { writer.print(MessageFormat.format( STARTED_NONDEPLOYED_APPS_ROW_BUTTON_SECTION, args)); } else if (!context.getAvailable() && isDeployed) { writer.print(MessageFormat.format( STOPPED_DEPLOYED_APPS_ROW_BUTTON_SECTION, args)); } else { writer.print(MessageFormat.format( STOPPED_NONDEPLOYED_APPS_ROW_BUTTON_SECTION, args)); } {code} | 2011-05-06 00:30:54 | 1,304,660,000 | resolved fixed | de7f0e1 | 1,304,670,000 | java/org/apache/catalina/manager/HTMLManagerServlet.java | Tomcat |
461 | 51,155 | Bug 51155 Missing @deprecated comments | null | 2011-05-05 19:36:28 | 1,304,640,000 | resolved fixed | f477068 | 1,304,670,000 | java/javax/servlet/jsp/el/ELException.java java/javax/servlet/jsp/el/ELParseException.java java/javax/servlet/jsp/el/Expression.java java/javax/servlet/jsp/el/ExpressionEvaluator.java java/javax/servlet/jsp/el/FunctionMapper.java java/javax/servlet/jsp/el/VariableResolver.java | Tomcat |
462 | 51,154 | Bug 51154 Spurious @deprecated tags in ServletContext | null | 2011-05-05 19:33:18 | 1,304,640,000 | resolved fixed | 01e1850 | 1,304,670,000 | java/javax/servlet/ServletContext.java | Tomcat |
463 | 50,950 | Bug 50950 NotSerializableException: org.apache.catalina.realm.GenericPrincipal | null | 2011-03-20 13:28:18 | 1,300,640,000 | resolved fixed | 0559491 | 1,304,600,000 | java/org/apache/catalina/ha/session/DeltaSession.java | Tomcat |
464 | 51,099 | Bug 51099 SPNEGO loginConfigName does not work | As reported by fhanik on the dev list: 2. com.sun.security.jgss.krb5.accept is not configurable While the authenticator has the attribute loginConfigName, there seems to be a place in the code where it omits this entry. renaming this entry in jaas.conf and setting the loginConfigName will fail to validate a ticket The problem code is here: gssContext = manager.createContext(manager.createCredential(null, GSSCredential.DEFAULT_LIFETIME, new Oid("1.3.6.1.5.5.2"), GSSCredential.ACCEPT_ONLY)); should look like final GSSManager manager = GSSManager.getInstance(); final PrivilegedExceptionAction<GSSCredential> action = new PrivilegedExceptionAction<GSSCredential>() { public GSSCredential run() throws GSSException { return manager.createCredential(null, GSSCredential.DEFAULT_LIFETIME, new Oid("1.3.6.1.5.5.2"), GSSCredential.ACCEPT_ONLY); } }; gssContext = manager.createContext(Subject.doAs(lc.getSubject(), action));|| best Filip | 2011-04-21 05:11:31 | 1,303,380,000 | resolved fixed | 343a609 | 1,304,550,000 | java/org/apache/catalina/authenticator/SpnegoAuthenticator.java | Tomcat |
465 | 51,119 | Bug 51119 extras - JmxRemoteLifecycleListener does not support JAAS based authentication and authorisation | (Also true in Tomcat 7) The JmxRemoteLifecycleListener does not support JAAS based authentication. That is, when authentication is required, it only supports file based authentication. | 2011-04-26 05:29:40 | 1,303,810,000 | resolved fixed | 2ffa0f7 | 1,304,540,000 | java/org/apache/catalina/mbeans/JmxRemoteLifecycleListener.java | Tomcat |
466 | 51,124 | Bug 51124 ArrayIndexOutOfBoundsException after setting org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true | First of all, I know that there has been a bug regarding a similar problem before and that it was fixed. But currently this bugs occurs even with tomcat version 6.0.32. We have a problem with the tomcat runnign with the parameter org.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true. After the tomcat has just started, everything is fine but after one or two days a lot of ArrayIndexOutOfBoundsException occur on random pages of the application. Tomcats started without this parameter don't seem to have that problem. Unfortunately we weren't able reproduce the bug locally, It appears only on our production system. Could there be a concurrency problem, that only shows if a lot it going on on the platform? I can provide two small stackstraces that can show the classes where the problem occurs: 1. Caused by: java.lang.ArrayIndexOutOfBoundsException at org.apache.jasper.runtime.BodyContentImpl.write(Unknown Source) at java.io.PrintWriter.write(PrintWriter.java:382) at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(Unknown Source) at org.apache.jasper.runtime.PageContextImpl.release(Unknown Source) at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(Unknown Source) at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(Unknown Source) at org.apache.jsp.members.lists.short_.incomingShortList_jsp._jspService(incomingShortList_jsp.java:796) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(Unknown Source) 2. Caused by: java.lang.ArrayIndexOutOfBoundsException at java.lang.String.getChars(String.java:854) at org.apache.jasper.runtime.BodyContentImpl.write(Unknown Source) at org.apache.jasper.runtime.BodyContentImpl.write(Unknown Source) at org.apache.jasper.runtime.BodyContentImpl.print(Unknown Source) at org.apache.taglibs.standard.tag.common.fmt.MessageSupport.doEndTag(MessageSupport.java:203) at org.apache.jsp.members.profiles.profile_jsp._jspx_meth_fmt_005fmessage_005f2(profile_jsp.java:4897) at org.apache.jsp.members.profiles.profile_jsp._jspService(profile_jsp.java:481) at org.apache.jasper.runtime.HttpJspBase.service(Unknown Source) at javax.servlet.http.HttpServlet.service(Unknown Source) | 2011-04-27 06:31:47 | 1,303,900,000 | resolved fixed | 2cdbcd5 | 1,304,540,000 | java/org/apache/jasper/runtime/BodyContentImpl.java | Tomcat |
467 | 51,136 | Bug 51136 Allow to set the context name through Tomcat's embeded class before adding it to the host | org.apache.catalina.startup.Tomcat creates contexts and add them to the host directly. It would be nice if we could set the name of the context before adding it to the host. I'm including a patch that overloads the methods "addWebapp" and "addContext" to take that name as a parameter. | 2011-04-29 16:18:31 | 1,304,110,000 | resolved fixed | 2dc54c4 | 1,304,500,000 | java/org/apache/catalina/startup/Tomcat.java | Tomcat |
468 | 51,095 | Bug 51095 NPE in AprEndpoint.java | null | 2011-04-20 12:51:05 | 1,303,320,000 | resolved fixed | 75d28d4 | 1,303,600,000 | java/org/apache/tomcat/util/net/AprEndpoint.java | Tomcat |
469 | 50,173 | Bug 50173 JDBCSampler discards ResultSet from a PreparedStatement. | Hi, I am using JMeter with a Test Plan that uses a JDBC Request with a PreparedStatement query type. When running this I am getting the following error in the jmeter.log file 2010/10/28 11:30:31 INFO - jmeter.threads.JMeterThread: Thread started: JDBC Users 1-1 2010/10/28 12:13:38 ERROR - jmeter.threads.JMeterThread: Error while processing sampler 'PREPARED SELECT Customer JDBC Request' : java.lang.NullPointerException at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.getStringFromResultSet(JDBCSampler.java:415) at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.resultSetsToString(JDBCSampler.java:268) at org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(JDBCSampler.java:208) at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:348) at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243) at java.lang.Thread.run(Thread.java:619) The query (below) can be expected to return a number of records SELECT * FROM Customer WHERE ID=?; the param is set to 1 If I use instead a SelectStatement results are returned so the query itself is not at fault. I have retrieved the code for the v2_4 tag to identify the root cause for the NPE and create a patch. This bug report includes a patch against trunk as the issue is also in trunk. The root cause is due to: org.apache.jmeter.protocol.jdbc.sampler.JDBCSampler.sample(Entry e) The code path for PreparedStatements types starting on line 204 has in it a call to org.hsqldb.jdbc.JDBCPreparedStatement.executeUpdate() which returns a ResultSet. The side effect of the call is to set the JDBCPreparedStatement.currentResultSet field member to null. JDBCSampler does not keep the ResultSet reference. Instead it is discarded. The call on the next line (208) String sb = resultSetsToString(pstmt,true,null) again tries to get the ResultSet on line 267. This causes a NullPointerException because the JDBCPreparedStatement.currentResultSet field was set to null earlier. Looking at the code path for a CALLABLE statement type (line 190) shows better handling for queries that return ResultSet. The two lines 207,208 replaced with boolean hasResultSet = pstmt.execute(); String sb = resultSetsToString(pstmt,hasResultSet,null); fixes the defect. Regards, Jeremy Whiting Red Hat | 2010-10-28 10:14:39 | 1,288,280,000 | resolved fixed | 3a847c7 | 1,303,000,000 | java/org/apache/tomcat/util/net/AprEndpoint.java | Tomcat |
470 | 51,042 | Bug 51042 HttpSessionListener.sessionCreated() is called a second time when user is authenticated with no matching sessionDestroyed() call. | When my web application has a HttpSessionListener configured in its web.xml, then that classes sessionCreated() is called when a user is assigned a new session. However, that method is *also* called when that user authenticates itself and the session is assigned a new ID (whether or not this is actually a "new session" can be disputed, but that's not the point of this bug). When the session is removed (due to a timeout, for example), then a single sessionDestroyed() call is executed. When the HttpSessionListener manages some kind of external resource, this behaviour leads to a resource leak, because sessionCreated() is called twice, while sessionRemoved() is only called once! I'm aware of the reason for changing the session ID and (somehow) understand why sessionCreated() is called again (after all there's a new session ID), but there must be *some* way for the SessionListener to be notified that the "old session" no longer exists. The same behaviour is seen in Tomcat 6.0 (and probably 5.5 as well, but I didn't test that). | 2011-04-08 05:54:06 | 1,302,260,000 | resolved fixed | dc3758e | 1,302,990,000 | java/org/apache/catalina/Session.java java/org/apache/catalina/ha/session/DeltaManager.java java/org/apache/catalina/ha/session/DeltaSession.java java/org/apache/catalina/ha/session/JvmRouteBinderValve.java java/org/apache/catalina/manager/DummyProxySession.java java/org/apache/catalina/session/ManagerBase.java java/org/apache/catalina/session/StandardSession.java | Tomcat |
471 | 51,038 | Bug 51038 No access logs for Servlet 3.0 async requests | Access logs written by org.apache.catalina.valves.AccessLogValve are not being written for servlet 3.0 async requests. To reproduce: - Handle a request asynchronously by marking the servlet with @WebServlet(asyncSupported=true) - Send some traffic and notice that nothing is being written to the access logs. AccessLogValve.log() is called by org.apache.catalina.Context.logAccess(). From the source for version 7.0.11, in org.apache.catalina.connector.CoyoteAdapter.java, line 416: AsyncContextImpl asyncConImpl = (AsyncContextImpl)request.getAsyncContext(); if (asyncConImpl != null) { async = true; } else if (!comet) { response.finishResponse(); if (postParseSuccess) { // Log only if processing was invoked. // If postParseRequest() failed, it has already logged it. ((Context) request.getMappingData().context).logAccess( request, response, System.currentTimeMillis() - req.getStartTime(), false); } req.action(ActionCode.POST_REQUEST , null); } In the async case logAccess() isn't called here. I've searched through the code and don't see logAccess() being called anywhere else, except in error cases. So, it looks like the async case is missing a call to logAccess() somewhere. | 2011-04-07 11:18:30 | 1,302,190,000 | resolved fixed | dc3dff4 | 1,302,990,000 | java/org/apache/catalina/connector/CoyoteAdapter.java test/org/apache/catalina/core/TestAsyncContextImpl.java test/org/apache/catalina/valves/TesterAccessLogValve.java | Tomcat |
472 | 50,997 | Bug 50997 StandardJarScanner ignores web-fragment.xml files in unpacked jars if they are not ending with ".jar" | null | 2011-03-30 11:57:49 | 1,301,500,000 | resolved fixed | 62ddb9e | 1,301,520,000 | java/org/apache/catalina/startup/ContextConfig.java java/org/apache/tomcat/util/scan/StandardJarScanner.java | Tomcat |
473 | 50,927 | Bug 50927 [patch] More specific error message for missing SSLCertificateFile | null | 2011-03-14 08:59:04 | 1,300,110,000 | resolved fixed | e34f848 | 1,300,270,000 | java/org/apache/tomcat/util/net/AprEndpoint.java | Tomcat |
474 | 50,929 | Bug 50929 [patch] Ensure rethrown exceptions retain the original cause | null | 2011-03-14 11:08:56 | 1,300,120,000 | resolved fixed | 0c96676 | 1,300,230,000 | java/javax/servlet/http/HttpUtils.java java/org/apache/catalina/connector/CoyoteInputStream.java java/org/apache/catalina/realm/JDBCRealm.java java/org/apache/catalina/valves/JDBCAccessLogValve.java java/org/apache/naming/resources/WARDirContext.java java/org/apache/tomcat/util/digester/NodeCreateRule.java | Tomcat |
475 | 50,903 | Bug 50903 Current keep-alive request processed after connector.stop() | When the connector is stopped, if a connection is in a keep-alive state the next request received by that connection will be processed and then the connection will be closed. When the request is received, it should be rejected. Outstanding questions: - What return code (if any) should be sent back to the client? - If the reading of a request starts before the connector is stopped, should that request be allowed to complete or should it be rejected? | 2011-03-09 14:34:53 | 1,299,700,000 | resolved fixed | c8ea62e | 1,300,210,000 | java/org/apache/coyote/ajp/AjpProcessor.java java/org/apache/coyote/http11/Http11AprProcessor.java java/org/apache/coyote/http11/Http11NioProcessor.java java/org/apache/coyote/http11/Http11Processor.java test/org/apache/catalina/connector/TestConnector.java test/org/apache/catalina/startup/TesterServlet.java test/org/apache/catalina/startup/TomcatBaseTest.java | Tomcat |
476 | 50,887 | Bug 50887 Enhancement to set security-provider within AjpAprProcessor | null | 2011-03-08 04:49:48 | 1,299,580,000 | resolved fixed | 552c4b7 | 1,300,020,000 | java/org/apache/catalina/valves/SSLValve.java java/org/apache/coyote/AbstractProtocolHandler.java java/org/apache/coyote/ajp/AbstractAjpProcessor.java java/org/apache/coyote/ajp/AjpAprProtocol.java java/org/apache/coyote/ajp/AjpProtocol.java java/org/apache/coyote/http11/Http11AprProcessor.java java/org/apache/coyote/http11/Http11AprProtocol.java | Tomcat |
477 | 50,895 | Bug 50895 JSP compiler initializes classes during compile which can result in failures | null | 2011-03-08 15:27:00 | 1,299,620,000 | resolved fixed | 5d61212 | 1,299,680,000 | java/org/apache/jasper/compiler/ELFunctionMapper.java | Tomcat |
478 | 25,060 | Bug 25060 Reloading context orphans currently open jndi datasource connections | I fiddled around with this a while and have determined to the best of my ability that this is a real bug. I have a jndi datasource connected to a postgresql server. I have two jndi resources (a reader and writer) so that later I can implement a system with replication etc and deal with writes and reads to different connections. To summarize, after using the system, there are two connections to postgres that get reused -- one reader and writer. Under load, this number increases and will slowly go back down. I usually end up with two idle connections (one reader and one writer) left under no load. If you reload the context where the datasource is at (it's a context specific datasource), the number of connections will jump by two when used. Each reload produces 2 more connections min until I restart the server. It appears that after a reload, the 'persisted connections' get abandoned / orphaned. Eventually, I hit my max connections and cannot aquire any more and the system fails. I have tried the abandond collection parameters and have added debug logging to my code to ensure that I am indeed calling close on the connections I checkout, even on exceptions and error cases. Under normal useage without reloads, no connection leakage happens. This is on a solaris 8 machine with the 4.1.27-hotfix-22096.tar.gz applied. Let me know if more information is required. I have this in a development environment and can let somone attach in jdb and hammer on the thing since it's not a production system -- if that will help in getting a repro. Wayne | 2003-11-27 21:15:10 | 1,069,990,000 | resolved fixed | 1211dbe | 1,299,620,000 | java/org/apache/catalina/core/StandardContext.java java/org/apache/catalina/deploy/NamingResources.java | Tomcat |
479 | 26,701 | Bug 26701 Enabling web applications to register their own stream handlers | A stream handler factory can be registered once per VM and tomcat registers the DirContextStreamHandlerFactory for the jndi protocol. However if there are web applications running inside that want to register handlers for custom scheme currently it is not possible. Can the DirContextStreamHandlerFactory be enhanced to allow applications to register stream handler for custom schemes they might have. Or better can this be a made a property in the context.xml file ? Is this already there - or can this enhanced in the future? | 2004-02-05 21:30:18 | 1,076,030,000 | resolved fixed | f622e3a | 1,299,450,000 | java/org/apache/catalina/loader/WebappLoader.java java/org/apache/naming/resources/Constants.java java/org/apache/naming/resources/DirContextURLStreamHandlerFactory.java test/org/apache/naming/resources/TestDirContextURLStreamHandlerFactory.java | Tomcat |
480 | 50,855 | Bug 50855 NullPointerException thrown in AuthenticatorBase.register method for null principal | null | 2011-03-02 11:19:27 | 1,299,080,000 | resolved fixed | b24b0c0 | 1,299,400,000 | java/org/apache/catalina/authenticator/AuthenticatorBase.java | Tomcat |
481 | 50,857 | Bug 50857 Test failures on Windows 7, 24 thread system | testPoolThreads20Connections10FairAsync [junit] java.sql.SQLException: [tomcat-pool-10] NoWait: Pool empty. Unable to fetch a connection, none available[10 in use]. [junit] at org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ConnectionPool.java:615) [junit] at org.apache.tomcat.jdbc.pool.ConnectionPool.getConnectionAsync(ConnectionPool.java:143) [junit] at org.apache.tomcat.jdbc.pool.DataSourceProxy.getConnectionAsync(DataSourceProxy.java:122) [junit] at org.apache.tomcat.jdbc.test.FairnessTest$TestThread.run(FairnessTest.java:231) | 2011-03-02 15:50:18 | 1,299,100,000 | resolved fixed | ef547fb | 1,299,100,000 | modules/jdbc-pool/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java | Tomcat |
482 | 27,988 | Bug 27988 Unhelpful FileNotFoundException raised | org.apache.naming.resources.DirContextURLConnection raises FileNotFoundException on lines 311, 344, 382 and 396. It would be more helpful if these provided a message string. For example, change line 344 to throw new FileNotFoundException(getURL().getFile()); This would make it easier to diagnose mistakes in server configurations. | 2004-03-26 17:01:25 | 1,080,340,000 | resolved fixed | 4a4d86e | 1,299,070,000 | java/org/apache/naming/resources/DirContextURLConnection.java | Tomcat |
483 | 28,852 | Bug 28852 failonerror attribute on Ant tasks | failonerror boolean attribute on manager Ant tasks would be a nice have to allow for more flexible operation within Ant build files. I will attach a patch next week that also fixes unecessary CRs during response read/print and missing url encoding in some tasks. | 2004-05-08 20:23:38 | 1,084,060,000 | resolved fixed | e1bf740 | 1,298,920,000 | java/org/apache/catalina/ant/JMXGetTask.java java/org/apache/catalina/ant/JMXQueryTask.java java/org/apache/catalina/ant/JMXSetTask.java java/org/apache/catalina/ant/ResourcesTask.java java/org/apache/catalina/ant/UndeployTask.java | Tomcat |
484 | 31,027 | Bug 31027 major error from minor whitespace error in properties file | A developer accidentally placed a tab character after the port number in the properties file for a tomcat instance. This prevented tomcat from listening on that port, but it was difficult to track down whether tomcat was running. Seems like the properties-file reader could easily trim excess whitespace before trying to use entries. | 2004-09-02 22:36:52 | 1,094,180,000 | resolved wontfix | 4b4ef0c | 1,298,810,000 | java/org/apache/catalina/startup/CatalinaProperties.java | Tomcat |
485 | 50,836 | Bug 50836 LifecycleState#isAvailable() to be more restrictive | I think some of the values returned by LifecycleState#isAvailable() are wrong. 1. I am certain that MUST_DESTROY should return false, because it is a state that is later than stopped. 2. I think that STOPPING_PREP should return false, because we can get there from the FAILED state. 3. I think that STARTING should return false, because it is too early to return true there. As a result, the following is the complete list of states are to return true in #isAvailable(): STARTED, MUST_STOP | 2011-02-26 14:05:18 | 1,298,750,000 | resolved fixed | 92ff888 | 1,298,800,000 | java/org/apache/catalina/Lifecycle.java java/org/apache/catalina/LifecycleListener.java java/org/apache/catalina/LifecycleState.java java/org/apache/catalina/util/LifecycleBase.java | Tomcat |
486 | 49,284 | Bug 49284 Implement SSL renegotiation for the NIO connector | Summary says it all. Entered as a reminder that it would be good to do this. | 2010-05-12 19:06:24 | 1,273,710,000 | resolved fixed | dcda15d | 1,298,660,000 | java/org/apache/coyote/http11/Http11NioProcessor.java java/org/apache/tomcat/util/net/NioChannel.java java/org/apache/tomcat/util/net/SecureNioChannel.java | Tomcat |
487 | 50,826 | Bug 50826 (Embedded) Tomcat.destroy() throws java.lang.IllegalArgumentException | Embedded Tomcat sometimes throws this exception when calling destroy() method: java.lang.IllegalArgumentException: null source at java.util.EventObject.<init>(EventObject.java:56) at javax.management.Notification.<init>(Notification.java:184) at org.apache.catalina.core.StandardContext.destroyInternal(StandardContext.java:5433) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:285) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:969) at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1108) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:285) at org.apache.catalina.core.ContainerBase.removeChild(ContainerBase.java:969) at org.apache.catalina.core.ContainerBase.destroyInternal(ContainerBase.java:1108) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:285) at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:593) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:285) at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:786) at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:285) at org.apache.catalina.startup.Tomcat.destroy(Tomcat.java:323) at su.msk.jet.nioproxy.rule.config.EmbeddedWebserver.stop(EmbeddedWebserver.java:26) I think that StandardContext.destroyInternal() misses check that this.getObjectName()!=null | 2011-02-24 08:47:47 | 1,298,560,000 | resolved fixed | 9d542ed | 1,298,570,000 | java/org/apache/catalina/core/StandardContext.java test/org/apache/catalina/startup/TestTomcat.java | Tomcat |
488 | 21,669 | Bug 21669 JNDIRealm roleBase pattern enahncement | Currently the roleBase attribute must be a fxed location in the directory. A simple change would allow the role base to be specified relative to the user DN. My enhancement suggestion would change the roleBase definition as follows: roleBase - the base entry for the role search. If not specified, the search base is the top level directory context. If specified it may optionally include pattern replacements "{0}".."{n}" corrosponding to the name parts of the user's distinguished name (as returned by javax.naming.Name.get()). For example, in the <Realm> defintion in server.xml you could specify the roleBase as: roleBase="ou=Groups,{1},{0}" The majority of the code to accomplish this would be in JNDIRealm.getRoles() and could look like this: String base = null; if ( roleBaseFormat != null ) { NameParser np = context.getNameParser(""); Name name = np.parse(dn); String nameParts[] = new String[name.size()]; for ( int idx = 0 ; idx < name.size() ; idx++ ) nameParts[idx] = name.get(idx); base = roleBaseFormat.format(nameParts); } // Perform the configured search and process the results if (debug >= 3) { log(" Searching role base '" + base + "' for attribute '" + roleName + "'"); log(" With filter expression '" + filter + "'"); } NamingEnumeration results = context.search(base, filter, controls); Thank You, Art | 2003-07-16 22:59:24 | 1,058,410,000 | resolved fixed | f22600c | 1,298,380,000 | java/org/apache/catalina/realm/JNDIRealm.java | Tomcat |
489 | 19,444 | Bug 19444 JNDI Authentication roles must be anonymous accessible | It appears that for the JNDIRealm to be able to locate roles, they must be anonymous accessible. I believe that for security purposes this should not be necessary if we are validating the user by binding to the directory. In that case the roles could be accessible to any bound user or that particular user. I discussed this very briefly on the Tomcat user list. It sounds like this had been discussed previously and for whatever reason, the idea rejected. Anyhow I submit that there is a bug, either in the code - which requires the roles to be anonymous, or in the documentation which does not make it clear that this is the case (at least in "Tomcat 4 Servlet/JSP Container - Realm Configuration HOW- TO). It seems reasonable to me that if we are binding to the directory to authenticate, we would have that user's access to roles. Perhaps the documentation should more explicetly state that this is not the case. In the hope that it would be accepted as an enhancement, I am going to attempt to attach a modified JNDIRealm that uses the authenticated connection to obtain the roles. Thank You, Art | 2003-04-29 21:58:13 | 1,051,670,000 | resolved fixed | a085c4a | 1,298,370,000 | java/org/apache/catalina/realm/JNDIRealm.java | Tomcat |
490 | 50,189 | Bug 50189 AJP connector sends GET BODY CHUNK when reading after response closed | If a servlet (probably incorrectly) closes the writer/outputstream of a response, and then attempts to read from the request, the AJP connector sends GET BODY CHUNK to the mod_jk worker. This then starts a series of very confusing communication between the worker and tomcat. The worker doesn't read it until it makes its next request. After making its next request, it reads it, and then sends a response with 0 length. At the same time, Tomcat responds to the request made by the worker with another GET BODY CHUNK, which the worker also responds with a message of 0 length. Then the really weird thing happens, Tomcat replays the first request made by that worker. At this point, based on what I'm looking at with tcpdump, I get too confused to work out exactly what is happening. | 2010-10-31 23:27:02 | 1,288,580,000 | resolved fixed | 514e713 | 1,298,050,000 | java/org/apache/catalina/connector/OutputBuffer.java | Tomcat |
491 | 50,802 | Bug 50802 Deviation from servlet3 spec concerning resource lookup from META-INF/resources | null | 2011-02-17 13:20:33 | 1,297,970,000 | resolved fixed | a9c3193 | 1,297,980,000 | java/org/apache/naming/resources/BaseDirContext.java java/org/apache/naming/resources/FileDirContext.java java/org/apache/naming/resources/VirtualDirContext.java java/org/apache/naming/resources/WARDirContext.java | Tomcat |
492 | 50,780 | Bug 50780 AjpConnectionHandler keeps many connections causing memory leak | Hi, Sorry for my english. I use Tomcat 7.0.6 with APR 1.1.20. I noticed (from heap dump) many org.apache.tomcat.util.net.SocketWrapper objects, which are kept by "connections" atribute in org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler object. I don't understand, why there are so many objects representing old connections which are not active. In my example it was 300000 objects created, after 7 days of Tomcat work. Has someone forgotten to clean this HashMap from time to time? best regards Sergiusz Brzezinski | 2011-02-15 04:51:49 | 1,297,760,000 | resolved fixed | b56bf50 | 1,297,960,000 | java/org/apache/coyote/ajp/AjpAprProtocol.java | Tomcat |
493 | 50,789 | Bug 50789 custom error pages and CDI/weld problem | null | 2011-02-15 12:09:28 | 1,297,790,000 | resolved fixed | 3810b04 | 1,297,940,000 | java/org/apache/catalina/Context.java java/org/apache/catalina/core/ApplicationDispatcher.java java/org/apache/catalina/core/StandardContext.java | Tomcat |
494 | 50,790 | Bug 50790 EL parser needs to be more dynamic | String.containes(CharSequence) is not being resolved correctly in the following situation: <span class="#{(facesContext.externalContext.request.requestURI.contains(item.url)) ? 'activepage' : ''}">#{template[item.labelKey]}</span> Exception: javax.el.ELException: /faces/template/mainLayout.xhtml: java.lang.NoSuchMethodException: java.lang.String.contains(java.lang.String) at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:87) at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:75) at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:285) at com.sun.faces.renderkit.html_basic.OutputLinkRenderer.encodeChildren(OutputLinkRenderer.java:125) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:848) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1613) at com.sun.faces.facelets.component.RepeatRenderer.encodeChildren(RepeatRenderer.java:97) at com.sun.faces.facelets.component.UIRepeat.process(UIRepeat.java:496) at com.sun.faces.facelets.component.UIRepeat.encodeChildren(UIRepeat.java:926) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1613) at javax.faces.render.Renderer.encodeChildren(Renderer.java:168) at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:848) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1613) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1616) at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:380) at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:126) at com.ocpsoft.pretty.faces.application.PrettyViewHandler.renderView(PrettyViewHandler.java:157) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:127) at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:313) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.reardeninc.tigris.ui.facesutil.FacesFilter.doFilter(FacesFilter.java:86) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.primefaces.webapp.filter.FileUploadFilter.doFilter(FileUploadFilter.java:79) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.ocpsoft.pretty.PrettyFilter.doFilter(PrettyFilter.java:100) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:496) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:541) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:383) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:243) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:188) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:288) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NoSuchMethodException: java.lang.String.contains(java.lang.String) at java.lang.Class.getMethod(Class.java:1605) at javax.el.BeanELResolver.invoke(BeanELResolver.java:405) at javax.el.CompositeELResolver.invoke(CompositeELResolver.java:161) at org.apache.el.parser.AstValue.getValue(AstValue.java:159) at org.apache.el.parser.AstChoice.getValue(AstChoice.java:45) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:189) at com.sun.faces.facelets.el.ELText$ELTextVariable.toString(ELText.java:207) at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:82) ... 46 more | 2011-02-15 15:04:47 | 1,297,800,000 | resolved fixed | cfab791 | 1,297,940,000 | java/javax/el/BeanELResolver.java java/org/apache/el/parser/AstValue.java test/org/apache/el/TestMethodExpressionImpl.java | Tomcat |
495 | 50,793 | Bug 50793 Invalid DispatchType in ServletRequestListener on async dispatch | If a ServletRequestListener is defined, when is invoked after a call to AsyncContext#dispatch() the DispatcherType returned from the ServletRequest is REQUEST rather than ASYNC. When the actual servlet is invoked, the type is correctly set to ASYNC. If the listener is intended to be invoked for each dispatch, then the DispatcherType should match the value returned in the filter/servlet. | 2011-02-15 22:47:30 | 1,297,830,000 | closed fixed | 72418ba | 1,297,880,000 | java/org/apache/catalina/connector/CoyoteAdapter.java java/org/apache/catalina/core/StandardContext.java java/org/apache/catalina/core/StandardContextValve.java test/org/apache/catalina/core/TestAsyncContextImpl.java | Tomcat |
496 | 50,713 | Bug 50713 The "roles" command doesn't work | null | 2011-02-03 02:38:46 | 1,296,720,000 | resolved fixed | 4b21973 | 1,297,860,000 | java/org/apache/catalina/ant/RolesTask.java java/org/apache/catalina/manager/ManagerServlet.java | Tomcat |
497 | 50,700 | Bug 50700 Context parameters are being overridden with parameters from the web application deployment descriptor | Context parameters are being overridden with parameters from the web application deployment descriptor even through "override" attribute is set to "false" For example: lines from context file <Context path="/path" docBase="/path/to/docbase" cookies="true"> <Parameter name="parameter_name" value="test1" override="false"/> .... </Context> lines from web.xml <context-param> <description>default value for parameter_name</description> <param-name>parameter_name</param-name> <param-value>test2</param-value> </context-param> Now servletContext.getInitParameter("parameter_name") returns "test2" | 2011-02-01 13:04:17 | 1,296,580,000 | resolved fixed | a073ac8 | 1,297,710,000 | java/org/apache/catalina/core/StandardContext.java | Tomcat |
498 | 50,771 | Bug 50771 HttpServletRequest#getAuthType() returns null though the request is authenticated. | null | 2011-02-14 03:30:02 | 1,297,670,000 | resolved fixed | 877a3df | 1,297,670,000 | java/org/apache/catalina/ha/session/DeltaRequest.java java/org/apache/catalina/ha/session/DeltaSession.java | Tomcat |
499 | 50,726 | Bug 50726 Jasper can generate uncompilable source code if genStringAsCharArray is turned on | Our jsp pages are compiled at build time. If I turn on genStringAsCharArray optimization switch, in some cases there will be longer lines in the generated java code than the javac compiler can process. It provides the following error message: [javac] Compiling 1609 source files to d:\...\jspc\classes [javac] d:\...\jspc\src\org\apache\jsp\WEB_002dINF\..._005fAPP\pages\termsconditions\TermsAndConditions_005fms_005fMY_jsp.java:96: constant string too long | 2011-02-07 08:14:03 | 1,297,080,000 | resolved fixed | d0f3899 | 1,297,540,000 | java/org/apache/jasper/compiler/Generator.java | Tomcat |
500 | 50,759 | Bug 50759 ValidatorClassName Validation fails to set lastValidated timestamp | null | 2011-02-10 19:12:21 | 1,297,380,000 | resolved fixed | 50f16fe | 1,297,440,000 | modules/jdbc-pool/java/org/apache/tomcat/jdbc/pool/PooledConnection.java | Tomcat |
501 | 50,751 | Bug 50751 JNDIRealm invokes getAttributes with no attribute ids. Prevents using DOMAIN\{0} to login. | null | 2011-02-10 12:11:43 | 1,297,360,000 | resolved fixed | 0313ded | 1,297,440,000 | java/org/apache/catalina/realm/JNDIRealm.java | Tomcat |
502 | 50,752 | Bug 50752 Typo in Embedded.java log message | There's a debug log message in Embedded.java with a typo in it: "INITIAL_CONTEXT_FACTORY alread set " Attached is a patch against the 6_0_29 tag, but the issue exists in tc6.0.x/trunk | 2011-02-10 12:17:31 | 1,297,360,000 | resolved fixed | 272e30c | 1,297,430,000 | java/org/apache/catalina/startup/Embedded.java | Tomcat |
503 | 50,720 | Bug 50720 When using jsp mapped as servlet in web.xml, cyrillic characters are not allowed in web.xml | null | 2011-02-04 09:07:57 | 1,296,830,000 | resolved fixed | e4bc803 | 1,297,360,000 | java/org/apache/jasper/compiler/WebXml.java | Tomcat |
504 | 50,721 | Bug 50721 RequestUtil.URLDecode() throws IllegalArgumentException for URLs with %xx-Code as last character | null | 2011-02-04 20:42:49 | 1,296,870,000 | resolved fixed | 5c9e352 | 1,297,290,000 | java/org/apache/catalina/util/RequestUtil.java test/org/apache/catalina/util/TestRequestUtil.java | Tomcat |
505 | 50,709 | Bug 50709 Make class org.apache.catalina.core.ApplicationContextFacade non-final | Please make class org.apache.catalina.core.ApplicationContextFacade non-final so it can be subclassed. Need to extend ApplicationContextFacade so Mobicents Sip Servlet, working on top of Tomcat 7, to integrate with Weld. Thanks George | 2011-02-02 13:11:45 | 1,296,670,000 | resolved fixed | 9f41c91 | 1,296,820,000 | java/org/apache/catalina/core/ApplicationContextFacade.java | Tomcat |
506 | 50,673 | Bug 50673 Error when stopping Tomcat using services.msc | When stopping Tomcat using services.msc, an error message is displayed: "Windows could not stop the Apache Tomcat 7 service on Local Computer. Error 109: The pipe has been ended." Despite this error, Tomcat appears to stop normally. No such problem was encountered in 6.0.29. | 2011-01-27 10:09:50 | 1,296,140,000 | resolved fixed | 6ac4a27 | 1,296,610,000 | java/org/apache/catalina/core/StandardServer.java java/org/apache/catalina/startup/Catalina.java | Tomcat |
507 | 50,631 | Bug 50631 InternalNioInputBuffer should honor maxHttpHeadSize | InternalNioInputBuffer automatically expands its buffer while reading in request line, effectively ignoring the maxHttpHeaderSize setting. | 2011-01-21 13:23:52 | 1,295,630,000 | resolved fixed | 0084470 | 1,296,550,000 | java/org/apache/coyote/http11/InternalNioInputBuffer.java | Tomcat |
508 | 50,325 | Bug 50325 Update Tomcat to use JRE provided solutions for CVE-2009-3555 if available | null | 2010-11-24 05:38:15 | 1,290,600,000 | resolved fixed | b4e9488 | 1,296,520,000 | java/org/apache/tomcat/util/net/jsse/JSSESocketFactory.java | Tomcat |
509 | 50,683 | Bug 50683 Servlet 3.0 annotations not scanned if unpackWars="false" | null | 2011-01-28 18:36:29 | 1,296,260,000 | resolved fixed | d21437e | 1,296,260,000 | java/org/apache/naming/resources/WARDirContext.java | Tomcat |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.