March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-2334) NullpointerExcption in SessionListener

by Thomas Schmidt (JIRA)

NullpointerExcption in SessionListener -------------------------------------- Key: JBPORTAL-2334 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2334 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.7.1 Final Environment: Windows XP, JBoss AS 4.2.3 GA Reporter: Thomas Schmidt Priority: Minor Our application has a security issue to invalidate the session on login. This invalidation is implemented in an webserver valve throught: req.getSession(true).invalidate(); Now, on login the Session will be destroyed. This starts the SessionListeners sessionDestroy method. The class org.jboss.portal.server.listener.SessionListener is implemented so, that after calling the context from session the context is not further validated. I think, this is a bug. In a listener you can not expected that somebody has stored a context in the session. a possible solution: Set<String> contexts = (Set<String>)arg0.getSession().getAttribute(KEY); if (context == null) { return; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3828) spelling mistake in xml tag

by Goran Oberg (JIRA)

spelling mistake in xml tag --------------------------- Key: JBAS-3828 URL: http://jira.jboss.com/jira/browse/JBAS-3828 Project: JBoss Application Server Issue Type: Bug Affects Versions: JBossAS-4.0.4.GA Environment: All Reporter: Goran Oberg Priority: Trivial Just a spelling mistake... Should be <url-delimiter> instead of <url-delimeter> in <ha-local-tx-datasource> -- 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, 4 months

5
7
0 / 0

[JBoss JIRA] Created: (JBCL-91) More tests for interrupting classloading requests

by Adrian Brock (JIRA)

More tests for interrupting classloading requests ------------------------------------------------- Key: JBCL-91 URL: https://jira.jboss.org/jira/browse/JBCL-91 Project: JBoss ClassLoader Issue Type: Task Components: ClassLoader Reporter: Adrian Brock Write some more detailed tests for threads being interrupted before and during classloading requests. Also verify an interrupted classloading request doesn't lead to a class being "blacklisted". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-41) Verify persistent file storage

by Thomas Diesler (JIRA)

Verify persistent file storage ------------------------------ Key: JBOSGI-41 URL: https://jira.jboss.org/jira/browse/JBOSGI-41 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Alpha3 Verify that BundleContext.getDataFile("config") creates a directory in the server data directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6568) PersistenceManager should retry all DB operations for a reasonable amount of tries

by Rico Neubauer (JIRA)

PersistenceManager should retry all DB operations for a reasonable amount of tries ---------------------------------------------------------------------------------- Key: JBAS-6568 URL: https://jira.jboss.org/jira/browse/JBAS-6568 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JMS (JBoss Messaging) Affects Versions: JBossAS-4.2.3.GA Reporter: Rico Neubauer Assignee: Clebert Suconic Attachments: PersistenceManager_4_2_3_GA.diff org.jboss.mq.pm.jdbc2.PersistenceManager does contain a simple logic in method remove(MessageReference, Tx) to retry a DB operation and therefore bypass sporadic temporary DB failures. This should be extended to the other DB-operations of PersistenceManager. Tests using a JDBC-driver throwing randomly arbitrary SQLExceptions showed this resolving most of them and keeping the system in a consistent state. Tests without a patched PersistenceManager ran quite fast into a dead end where JMS messages were not being processed anymore until restart of the AS - also see http://www.jboss.org/index.html?module=bb&op=viewtopic&t=151023 for this symptom. Proposed patch will get attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBXB-189) initialization of JBossXBBuilder.useUnorderedSequence with a system property

by Alexey Loubyansky (JIRA)

initialization of JBossXBBuilder.useUnorderedSequence with a system property ---------------------------------------------------------------------------- Key: JBXB-189 URL: https://jira.jboss.org/jira/browse/JBXB-189 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.1.CR1 It would be useful to be able to initialize useUnorderedSequence configuration option with a system property, e.g. xb.builder.useUnorderedSequence. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-39) Bundle undeploy does not clean up properly

by Thomas Diesler (JIRA)

Bundle undeploy does not clean up properly ------------------------------------------ Key: JBOSGI-39 URL: https://jira.jboss.org/jira/browse/JBOSGI-39 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Alpha3 Redeployment of bundles seems to fail -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

1
9
0 / 0

[JBoss JIRA] Created: (JBPORTAL-953) wiki not visible

by Sacha Labourey (JIRA)

wiki not visible ---------------- Key: JBPORTAL-953 URL: http://jira.jboss.com/jira/browse/JBPORTAL-953 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Sacha Labourey deploying wiki.war from portletswap in JBP deploy's folder doesn't make it visible in the list of creatable portlet (admin interface) -- 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, 4 months

3
2
0 / 0

[JBoss JIRA] Created: (JBAS-6573) serialVersionUID mismatch on ManagementViewImpl$ManagedOperationDelegate

by Shelly McGowan (JIRA)

serialVersionUID mismatch on ManagementViewImpl$ManagedOperationDelegate ------------------------------------------------------------------------ Key: JBAS-6573 URL: https://jira.jboss.org/jira/browse/JBAS-6573 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Reporter: Shelly McGowan Assignee: Scott M Stark Fix For: JBossAS-5.1.0.Beta1 Seen since the commit of JBAS-6285: serialVersionUID error for org.jboss.profileservice.management.ManagementViewImpl$ManagedOperationDelegate, 500 -775240509110032859, current: -7167618408932635038 Should this be excluded? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-6445) JBoss 5 - ServletException: OncePerRequestFilter just supports HTTP requests

by Prashanth N (JIRA)

JBoss 5 - ServletException: OncePerRequestFilter just supports HTTP requests ----------------------------------------------------------------------------- Key: JBAS-6445 URL: https://jira.jboss.org/jira/browse/JBAS-6445 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate service, JMS (JBoss Messaging), JSF, Spring integration, Web (Tomcat) service, Web Services Affects Versions: JBossAS-5.0.0.GA Environment: Oracle Enterprise Linux / Redhat Linux, Sun JDK 1.5.0_14 Reporter: Prashanth N Assignee: Steve Ebersole I am new to JBoss 5.0.0 although I have been using JBoss 4.2.x for a while now. We have an application built using ICEfaces, Spring and Hibernate. I have been successful in managing to make changes to the application and deploy it on JBoss 5.0.0 without any startup errors. I am using it with Sun JDK 1.5.0_14 on Linux. However, when I invoke any application URL, I get the following error: [Persistent Faces Servlet]] (http-0.0.0.0-8080-1) Servlet.service() for servlet Persistent Faces Servlet threw exception javax.servlet.ServletException: OncePerRequestFilter just supports HTTP requests at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:62) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) 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:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) We are eager to move our application to JBoss 5 and we are severly gated because of the issue. If I deploy the same WAR file on 4.2.2 it works like a charm without any changes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 4 months

3
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 March 2009