November 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6132) Revert to AS 4 behavior of handling distributable webapps in default config

by Brian Stansberry (JIRA)

Revert to AS 4 behavior of handling distributable webapps in default config --------------------------------------------------------------------------- Key: JBAS-6132 URL: https://jira.jboss.org/jira/browse/JBAS-6132 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.0.GA Just log a WARN instead of failing due to missing dependency. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5964) NPE in expiration of passivated sessions

by Brian Stansberry (JIRA)

NPE in expiration of passivated sessions ---------------------------------------- Key: JBAS-5964 URL: https://jira.jboss.org/jira/browse/JBAS-5964 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.0.0.GA >From Radoslav Husar: The other NPE I was talking about, occured only after few minutes: [JBoss] 10:15:19,851 ERROR [JBossCacheManager] processExpirationPassivation(): failed handling unloaded session XYZ [JBoss] java.lang.NullPointerException [JBoss] at org.jboss.web.tomcat.service.session.JBossCacheManager.processExpirationPassivation(JBossCacheManager.java:1292) [JBoss] at org.jboss.web.tomcat.service.session.JBossManager.backgroundProcess(JBossManager.java:353) [JBoss] at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1327) [JBoss] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1612) [JBoss] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1621) [JBoss] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1621) [JBoss] at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1601) [JBoss] at java.lang.Thread.run(Thread.java:619) This is due to a missing null check in some code I added for JBAS-5693. -- 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, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4370) SecurityDeployer: XACML Policy Registration

by Anil Saldhana (JIRA)

SecurityDeployer: XACML Policy Registration ------------------------------------------- Key: JBAS-4370 URL: http://jira.jboss.com/jira/browse/JBAS-4370 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 Move the XACML Policy registration from the component modules to the security deployer. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1566) Convert StatefulTreeCache to use JBoss Cache 3

by Brian Stansberry (JIRA)

Convert StatefulTreeCache to use JBoss Cache 3 ---------------------------------------------- Key: EJBTHREE-1566 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1566 Project: EJB 3.0 Issue Type: Task Components: Clustering, core Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 1.0.0-Beta6 JBoss Cache 3.x has some changes in eviction configuration best practices and in how to configure "never/no-limit" (was '0', now '-1'). Convert StatefulTreeCache and related classes to conform. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1565) Remove unused legacy classes from org.jboss.ejb3.cache.tree

by Brian Stansberry (JIRA)

Remove unused legacy classes from org.jboss.ejb3.cache.tree ----------------------------------------------------------- Key: EJBTHREE-1565 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1565 Project: EJB 3.0 Issue Type: Task Components: Clustering, core Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: 1.0.0-Beta6 There are a number of classes in this package that are not used, even in the 4.2 branch. Remove them. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBWEB-125) Crash ending an event driven HTTP connection

by Remy Maucherat (JIRA)

Crash ending an event driven HTTP connection -------------------------------------------- Key: JBWEB-125 URL: https://jira.jboss.org/jira/browse/JBWEB-125 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-2.1.1.GA Reporter: Remy Maucherat Assignee: Mladen Turk I experienced a very rare crash when using events (bayeux stock ticker on localhost + F5), when setting back the socket timeout at the end of the processing. The odd part is that it seems to be caught with an exception (very good) but causes a JVM crash anyway. Oct 31, 2008 5:31:47 PM org.apache.coyote.http11.Http11AprProcessor event SEVERE: Error processing request org.apache.tomcat.jni.Error: Socket operation on non-socket at org.apache.tomcat.jni.Socket.timeoutSet(Native Method) at org.apache.coyote.http11.Http11AprProcessor.action(Http11AprProcessor.java:1262) at org.apache.coyote.Response.action(Response.java:184) at org.apache.catalina.connector.CoyoteAdapter.event(CoyoteAdapter.java:272) at org.apache.coyote.http11.Http11AprProcessor.event(Http11AprProcessor.java:786) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.event(Http11AprProtocol.java:544) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1988) at java.lang.Thread.run(Thread.java:636) # # An unexpected error has been detected by Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00b43521, pid=5850, tid=101182352 # # Java VM: OpenJDK Server VM (1.6.0-b09 mixed mode linux-x86) # Problematic frame: # C [libtcnative-1.so.0.1.15+0xf521] Java_org_apache_tomcat_jni_Socket_timeoutSet+0x61 # # An error report file with more information is saved as: # /home/remm/Work/jbossweb/jbossweb-2.1.x/output/build/hs_err_pid5850.log [thread 97975184 also had an error] # # If you would like to submit a bug report, please visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Assigning to Mladen since the error hints the crash can be avoided (as it seems detected already). -- 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, 8 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2224) create script to bundle EAP and portal

by Prabhat Jha (JIRA)

create script to bundle EAP and portal -------------------------------------- Key: JBPORTAL-2224 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2224 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Prabhat Jha -- 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, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2168) automate tests with Branch 26 and Branch27

by Prabhat Jha (JIRA)

automate tests with Branch 26 and Branch27 ------------------------------------------ Key: JBPORTAL-2168 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2168 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Prabhat Jha Assignee: Viliam Rockai -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (SECURITY-303) Release Security 2.0.2.CR12

by Anil Saldhana (JIRA)

Release Security 2.0.2.CR12 --------------------------- Key: SECURITY-303 URL: https://jira.jboss.org/jira/browse/SECURITY-303 Project: JBoss Security and Identity Management Issue Type: Sub-task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Affects Versions: 2.0.2.CR11 Reporter: Anil Saldhana Assignee: Stefan Guilhen Fix For: 2.0.2.CR12 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-854) Unit tests: make sure GossipRouter related tests start GossipRouter on different ports

by Bela Ban (JIRA)

Unit tests: make sure GossipRouter related tests start GossipRouter on different ports -------------------------------------------------------------------------------------- Key: JGRP-854 URL: https://jira.jboss.org/jira/browse/JGRP-854 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.7 This requires the ability to replace properties (e.g. router_port in TUNNEL, PING, TCPGOSSIP) before the channel is created -- 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, 8 months

1
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 November 2008