October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4131) Tomcat does not invalidate sessions

by Pascal Heraud (JIRA)

Tomcat does not invalidate sessions ----------------------------------- Key: JBAS-4131 URL: http://jira.jboss.com/jira/browse/JBAS-4131 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-3.2.6 Final Environment: Linux RedHat enterprise 3 / JDK 1.4.2_06 / Apache 2.0 / Mod JK Reporter: Pascal Heraud Assigned To: Remy Maucherat On our systems, sessions dos not invalidate with a an high rate ( close to 100 % for some applications !) due to this Tomcat bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=37356 As it seems to be present in all releases of Tomcat right now, even in 5.5, and will be fixed in 5.5.21, how Jboss will integrate this bugfix into 3.2.x and 4.0 branches and when ? Sincerly, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBAS-4436) session.getSession(true) does not create new sessionID after invalidation

by Ludwig Adam (JIRA)

session.getSession(true) does not create new sessionID after invalidation ------------------------------------------------------------------------- Key: JBAS-4436 URL: http://jira.jboss.com/jira/browse/JBAS-4436 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.3 SP1 Environment: JBoss 4.03SP1 running on java version 1.5.0_10, server is a standard SuSE 10 linux Reporter: Ludwig Adam Assigned To: Remy Maucherat It is not possible to generate new session IDs as expected and stated in the servlet specification. A call of HttpSession.invalidate() unbounds all objects attached to the session but does not set the session to invalid. Sample Code: public class SessionTest extends HttpServlet { protected void doGet(HttpServletRequest httpServletRequest, HttpServletResponse httpServletResponse) throws ServletException, IOException { HttpSession curSession=httpServletRequest.getSession(); String prevSession = curSession.getId(); curSession.invalidate(); // Should invalidate session curSession= httpServletRequest.getSession(true); // Should return new valid session, but returns old session instead String newSession= curSession.getId(); boolean testCondition = prevSession.equals(newSession); // is true } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4303) Web session is empty when forwarding request to another web context.

by Penkov Vladimir (JIRA)

Web session is empty when forwarding request to another web context. -------------------------------------------------------------------- Key: JBAS-4303 URL: http://jira.jboss.com/jira/browse/JBAS-4303 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Environment: Fedora Core 6 Reporter: Penkov Vladimir Assigned To: Remy Maucherat I have following in web.xml: ===================== <servlet> <servlet-name>Redirector</servlet-name> <servlet-class>web.servlet.Redirector</servlet-class> </servlet> <servlet-mapping> <servlet-name>Redirector</servlet-name> <url-pattern>/redirect.do</url-pattern> </servlet-mapping> <error-page> <error-code>404</error-code> <location>/redirect.do</location> </error-page> ===================== It is located in /deploy/web.jar. It is deployed under / context. My jsp are in dir: /deploy/resources.war/, deployed under /resources. In Redirector I do: ============== String url = (String) request.getAttribute("javax.servlet.error.request_uri"); String contextPath = (String) context.getAttribute("/resources"); ServletContext c = context.getContext(contextPath); RequestDispatcher disp = c.getRequestDispatcher(url); disp.forward(request, response); ============== So now I can reach my jsp in another context. In servlet Login I do: ============= ClientManager manager = new ClientManager(); Client client = manager.findClientByLogin(login); if (client!=null && client.getPassword().equals(password)) { request.getSession().setAttribute(CLIENT_KEY, client); } response.sendRedirect("/private/index.jsp"); ============= in /deploy/resources.war/private/index.jsp I have: ================ <% Enumeration e = request.getSession().getAttributeNames(); System.out.println("element names:"); while (e.hasMoreElements()) { System.out.println("e.nextElement() = " + e.nextElement()); } %> ================ And I recieve no elements in session. Variables, sent in the request attributes, are accessible fine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4412) maxSpareThreads not honoured

by Ortwin Glück (JIRA)

maxSpareThreads not honoured ---------------------------- Key: JBAS-4412 URL: http://jira.jboss.com/jira/browse/JBAS-4412 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Ortwin Glück Assigned To: Remy Maucherat I have set maxThreads="50" minSpareThreads="5" maxSpareThreads="10" strategy="ms" in the HTTP/1.1 connector. After making many parallel requests the connection pool in the /status page shows 50 threads in READY status which do not decay even when there is no traffic for several minutes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3812) TomcatDeployment should use modified WebMetaData

by Thomas Diesler (JIRA)

TomcatDeployment should use modified WebMetaData ------------------------------------------------ Key: JBAS-3812 URL: http://jira.jboss.com/jira/browse/JBAS-3812 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.Beta The Web Service Deployers modify the WebMetaData. This should then be used to deploy to Tomcat. Rewrite of the war should not be necessary. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

6
11
0 / 0

[JBoss JIRA] Created: (JBAS-4353) request.getRequestURL/request.getRequestURI return different results depending on running behind mod_jk or not.

by Jon Stevens (JIRA)

request.getRequestURL/request.getRequestURI return different results depending on running behind mod_jk or not. --------------------------------------------------------------------------------------------------------------- Key: JBAS-4353 URL: http://jira.jboss.com/jira/browse/JBAS-4353 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.2.0.CR2 Reporter: Jon Stevens Assigned To: Remy Maucherat Priority: Blocker Running with the bundled Tomcat on port 8080, i get this: requestUrl: http://HOSTNAME:8080/data/xxx/members/4457/pictures/thumbs/Behind%20the%2... requestUri: /data/xxx/members/4457/pictures/thumbs/Behind%20the%20Scenes/peter.jpg Running tomcat behind mod_jk, I get this: requestUrl: http://HOSTNAME/data/xxx/members/4457/pictures/thumbs/Behind the Scenes/peter.jpg requestUri: /data/xxx/members/4457/pictures/thumbs/Behind the Scenes/peter.jpg This is a blocker because I depend on knowing if the string is urlencoded or not. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBWEB-77) Servlet throws NPE the first time it is hit.

by Phillip Thurmond (JIRA)

Servlet throws NPE the first time it is hit. -------------------------------------------- Key: JBWEB-77 URL: http://jira.jboss.com/jira/browse/JBWEB-77 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Phillip Thurmond Assigned To: Mladen Turk Priority: Blocker The first time a servlet is hit, it throws a NPE. After the exception is thrown, the servlet works correctly. Here is the stack trace. Example war attached. java.lang.NullPointerException at org.apache.catalina.connector.OutputBuffer.write(OutputBuffer.java:471) at org.apache.catalina.connector.CoyoteOutputStream.print(CoyoteOutputStream.java:113) at test.TestServlet.doGet(TestServlet.java:67) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) 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:228) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445) at java.lang.Thread.run(Thread.java:595) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-768) Fix ShutdownTestCase failures

by Ron Sigal (JIRA)

Fix ShutdownTestCase failures ----------------------------- Key: JBREM-768 URL: http://jira.jboss.com/jira/browse/JBREM-768 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) Some of the <transport>ShutdownTestCase unit tests have been failing randomly. One change to the tests since they were first written was the addition of a blocking callback poller. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1715) Add Producer configuration screen in WSRP admin portlet.

by Chris Laprun (JIRA)

Add Producer configuration screen in WSRP admin portlet. -------------------------------------------------------- Key: JBPORTAL-1715 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1715 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.1 Final, 2.6.2 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final, 2.8 Final -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1007) BMTInterceptor refers to wrong spec

by Carlo de Wolf (JIRA)

BMTInterceptor refers to wrong spec ----------------------------------- Key: EJBTHREE-1007 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1007 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Minor Fix For: EJB 3.0 RC11 - FD 11:52:15,234 ERROR [BMTInterceptor] Application error: BMT stateless bean TesterBean should complete transactions before returning (ejb1.1 spec, 11.6.1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 8 months

1
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007