November 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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

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

17 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5008) boot.log should contain command line options, i.e. -Xms, -Xmx, -b, -c, -XXblah...etc

by Galder Zamarreno (JIRA)

boot.log should contain command line options, i.e. -Xms, -Xmx, -b, -c, -XXblah...etc ------------------------------------------------------------------------------------ Key: JBAS-5008 URL: http://jira.jboss.com/jira/browse/JBAS-5008 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Affects Versions: JBossAS-4.2.2.GA, JBossAS-5.0.0.Beta2 Reporter: Galder Zamarreno Assigned To: Scott M Stark boot.log should show command line options passed to AS, i.e. -b, -Xms, -Xmx, -XXblah... These are currently shown in the console output, but from a support perspective, having all the system properties (which are already included boot.log) and command line options in boot.log would speed up resolution. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1817) package-normal and dependent tasks in distrib.xml incorrectly look for portal-wsrp-exploded.sar which does not exist

by Andrew Oliver (JIRA)

package-normal and dependent tasks in distrib.xml incorrectly look for portal-wsrp-exploded.sar which does not exist -------------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1817 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1817 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.3 Final Reporter: Andrew Oliver Assigned To: Chris Laprun the various targets to create a distribution look for the exploded wsrp but it doesn't exist. It appears that an explode target in the wsrp dir might do this but it isn't actually called because tools/etc/buildfragments/tools.ent has the only thing that looks like it might call it commented out. As a workaround you can comment out the following:  and forgo the joy that is wsrp...and this creates a valid dist...but some peeps want some wsrp too. -- 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

17 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (JGRP-629) Streaming state transfer repeats set state events in highly concurrent situation

by Vladimir Blagojevic (JIRA)

Streaming state transfer repeats set state events in highly concurrent situation -------------------------------------------------------------------------------- Key: JGRP-629 URL: http://jira.jboss.com/jira/browse/JGRP-629 Project: JGroups Issue Type: Bug Affects Versions: 2.6, 2.5.1 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.5.2, 2.6.1, 2.7 Similar to regular state transfer streaming state transfer protocol maintains a list of state requesters. As state response is sent to requesters these entries are removed from the list. However, in highly concurrent scenarios where dozen of nodes are started and request get-and-state transfer state requesters entries in the list are filled up and as the list is iterated *multiple* state responses might be sent to state requester. This behavior is not usually noticed by users as a bug but should be fixed anyhow. -- 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

17 years, 1 month

1
6
0 / 0

[JBoss JIRA] Created: (JGRP-626) TCP ConnectionTable threads should be started after TP threads

by Vladimir Blagojevic (JIRA)

TCP ConnectionTable threads should be started after TP threads -------------------------------------------------------------- Key: JGRP-626 URL: http://jira.jboss.com/jira/browse/JGRP-626 Project: JGroups Issue Type: Bug Affects Versions: 2.6, 2.5.1 Reporter: Vladimir Blagojevic Assigned To: Vladimir Blagojevic Fix For: 2.6.1, 2.7 Just like in UDP we first have to initialize and start TP threads and then threads specific to TCP connection table. Otherwise, we might receive messages in connection table that are passed to uninitialized TP protocol. -- 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

17 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JGRP-624) connect-with-state-transfer not working when multiple clients simultaneously try to connect-with-state-transfer

by Michael Newcomb (JIRA)

connect-with-state-transfer not working when multiple clients simultaneously try to connect-with-state-transfer --------------------------------------------------------------------------------------------------------------- Key: JGRP-624 URL: http://jira.jboss.com/jira/browse/JGRP-624 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Michael Newcomb Assigned To: Bela Ban 1. have 2 members of a group connected 2. simultaneously launch 3 new members that connect with a state transfer request 3. each of the 3 new members eventually time out awaiting state transfer I was watching the log on the initially connected members (1 coordinator and 1 member) and I watched as each of the new members slowly joined (about 10s between each new view). However, on the coordinator log, I saw some GMS 'flush failure' messages. I will be re-running with all the logs on and will report back. -- 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

17 years, 1 month

3
11
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007