May 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-3954) Cannot compile jsp on Windows with reference to a class in WEB-INF/classes of the same name but difference case as a package name

by Jim Moran (JIRA)

Cannot compile jsp on Windows with reference to a class in WEB-INF/classes of the same name but difference case as a package name --------------------------------------------------------------------------------------------------------------------------------- Key: JBAS-3954 URL: http://jira.jboss.com/jira/browse/JBAS-3954 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: Jim Moran Assigned To: Remy Maucherat If UseJBossWebLoader is true in jbossweb-tomca55.sar/META-INF/jboss-service.xml And there is a class in a war's WEB-INF/classes that has a classname identical to a package name except that the cases are different And there is a jsp which references this class And this war is deployed on Windows Then the jsp causes error on Compile such as: 2006-11-22 12:04:40,414 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jdt].[jsp]] Servlet.service() for servlet jsp threw exception org.apache.jasper.JasperException: Unable to compile class for JSP An error occurred at line: 5 in the jsp file: /index.jsp Generated servlet error: test.mypackage.name cannot be resolved to a type at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:84) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:328) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:414) -- 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
3
0 / 0

[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: (JBAS-4293) Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation

by Vladimir Piskarev (JIRA)

Should not throw TransactionRolledbackException when the transaction is rolled back because of setRollbackOnly invocation ------------------------------------------------------------------------------------------------------------------------- Key: JBAS-4293 URL: http://jira.jboss.com/jira/browse/JBAS-4293 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Vladimir Piskarev Assigned To: Scott M Stark According to 18.3.9 of EJB 2.1 spec "the container should not throw the java.rmi.RemoteException or javax.ejb.EJBException if the container performs a transaction rollback because the instance has invoked the setRollbackOnly method on its EJBContext object. In this case, the container must rollback the transaction and pass the business method result or the application exception thrown by the business method to the client.". Also 17.6.2.8 says "If the container initiated the transaction immediately before dispatching the business method to the instance (as opposed to the transaction being inherited from the caller), the container must note that the instance has invoked the setRollbackOnly method. When the business method invocation completes, the container must roll back rather than commit the transaction. If the business method has returned normally or with an application exception, the container must pass the method result or the application exception to the client after the container performed the rollback.". However, if exception-on-rollback is true, JBoss EJB Container throws the TransactionRolledbackException when the transaction should be rolled back because of the setRollbackOnly invocation. This clearly violates the EJB spec requirements mentioned above. It seems that the TxInterceptorCMT.checkTransactionStatus method should not throw the exception when the transaction status is STATUS_MARKED_ROLLBACK. -- 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: (EJBTHREE-765) EJB3 documentation on website is out of date

by Jeff Schnitzer (JIRA)

EJB3 documentation on website is out of date -------------------------------------------- Key: EJBTHREE-765 URL: http://jira.jboss.com/jira/browse/EJBTHREE-765 Project: EJB 3.0 Issue Type: Task Components: Documentation Reporter: Jeff Schnitzer Two things: The docs at http://docs.jboss.org/ejb3/ are for EJB3 RC6 The "Notes" link on http://labs.jboss.com/portal/jbossejb3/download/index.html points at the release notes for RC4. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira May 2007