October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4650) JSFIntegrationUnitTestCase is failing for JBoss AS 5

by Stan Silvert (JIRA)

JSFIntegrationUnitTestCase is failing for JBoss AS 5 ---------------------------------------------------- Key: JBAS-4650 URL: http://jira.jboss.com/jira/browse/JBAS-4650 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-5.0.0.GA JSFIntegrationUnitTestCase fails. The specific assertion that fails is in the logging test. This was caused by setting a default logging level for JSF in log4j.xml. If you run the test twice, it will pass the second time because the test sets logging levels by hitting the Log4JService via HTTP. However, because the WAR for the test is deployed before the logging levels were changed, the WAR would be deployed with the old logging values. So the fix is to change the test to set the logging levels before the WAR is deployed. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever

by Adrian Brock (JIRA)

JBossMQ WriteTask in UIL2 could block forever --------------------------------------------- Key: JBAS-4525 URL: http://jira.jboss.com/jira/browse/JBAS-4525 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an Thread.interrupt(). If however, something "eats" that interrupt status of the thread then the WriteTask will block forever and never stop. This leads to thread leaks. The solution is not wait forever or an interrupt. Instead the thread should periodically wake up and check the "started" flag. e.g. Here is the suggest patch in outline while (true) { + synchronized (running) + { + if (WriteState != Started) + break; + } BaseMsg msg = null; try { - msg = (BaseMsg) sendQueue.take(); + // Only wait for 10 seconds + msg = (BaseMsg) sendQueue.poll(10000l); + if (msg == null) + continue; // re-start the loop when no message after 10 seconds -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException

by Anil Saldhana (JIRA)

Redeploy of Tomcat5 Service chokes with RuntimeException -------------------------------------------------------- Key: JBAS-3517 URL: http://jira.jboss.com/jira/browse/JBAS-3517 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens. You will notice the following Runtime Exception and the tomcat service fails to deploy. ============================================================================================== 13:33:30,421 INFO [Catalina] Initialization processed in 562 ms 13:33:30,421 INFO [StandardService] Starting service jboss.web 13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1 7 13:33:30,453 INFO [StandardHost] XML validation disabled 13:33:30,468 INFO [Catalina] Server startup in 47 ms 13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185) at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) =================================================================================== Use the following api of PolicyContext in Tomcat5 service http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h... -- 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, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3527) Tomcat 6 fixes needed for JSF

by Stan Silvert (JIRA)

Tomcat 6 fixes needed for JSF ----------------------------- Key: JBAS-3527 URL: http://jira.jboss.com/jira/browse/JBAS-3527 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta Reporter: Stan Silvert Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.GA This JIRA task is for tracking the Tomcat 6 bugs that need to be fixed for JSF in JBoss AS 5.0.0 http://issues.apache.org/bugzilla/show_bug.cgi?id=39803 http://issues.apache.org/bugzilla/show_bug.cgi?id=39805 http://issues.apache.org/bugzilla/show_bug.cgi?id=40279 We have a workaround for this one, but it would be nice if it were fixed: http://issues.apache.org/bugzilla/show_bug.cgi?id=39804 -- 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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBAS-4198) Align EJB3 Security with JEE 1.4 Behavior

by Anil Saldhana (JIRA)

Align EJB3 Security with JEE 1.4 Behavior ----------------------------------------- Key: JBAS-4198 URL: http://jira.jboss.com/jira/browse/JBAS-4198 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3, Security Affects Versions: JBossAS-4.2.0.CR1, JBossAS-5.0.0.Beta1, JBossAS-4.0.5.GA Reporter: Anil Saldhana Assigned To: Bill Burke Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.1.CR1 EJB3 security layer needs to be aligned with the ejb2 security layer. There is a need to sync up metadata and maybe pull a common abstract layer out such that there is alignment. -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-896) Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor

by Carlo de Wolf (JIRA)

Specifying an interceptor-order in ejb-jar.xml also creates a new instance of the interceptor --------------------------------------------------------------------------------------------- Key: EJBTHREE-896 URL: http://jira.jboss.com/jira/browse/EJBTHREE-896 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: interceptor2 Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Critical -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1082) Optimise nodes for single elements

by Manik Surtani (JIRA)

Optimise nodes for single elements ---------------------------------- Key: JBCACHE-1082 URL: http://jira.jboss.com/jira/browse/JBCACHE-1082 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.CR3, 2.0.0.GA Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should: 1) Create a reference to 2 Objects for key and value, as well as a Map. 2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair 3) Otherwise just hold the key/value pair as direct object refs. Would affect UnversionedNode and WorkspaceNodeImpl. -- 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, 1 month

2
8
0 / 0

[JBoss JIRA] Created: (JBCACHE-1009) Support preload functionality as part of region activation

by Brian Stansberry (JIRA)

Support preload functionality as part of region activation ---------------------------------------------------------- Key: JBCACHE-1009 URL: http://jira.jboss.com/jira/browse/JBCACHE-1009 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Manik Surtani Currently a cache loader preload only happens as part of cache start. It could be supported as part of the activateRegion process; i.e. if one of the defined preload regions in the cache loader config encapsulates the region being activated, preload the region. If one of the defined preload regions names a subregion of the region being activated, preload the subregion. -- 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, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1039) Optimized replication of entities and extended persistence context in SFSBs

by Brian Stansberry (JIRA)

Optimized replication of entities and extended persistence context in SFSBs --------------------------------------------------------------------------- Key: EJBTHREE-1039 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1039 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Optimize replication of clustered SFSBs that hold refs to managed entities and extended persistence contexts, while still ensuring that object identity is maintained between refs to an entity held by the SFSB and those held by the replicated EntityManager. Currently object identity is maintained by serializing the SFSB and the related EntityManager in one operation. The entire EM is serialized, including entities that have been flushed to the db. This is inefficient, since the replication is only done to support failover and in the case of node failover, the flushed entities can be restored from the db or the EM's 2nd level cache. Intent is to: 1) Use JBoss serialization in order to have the ability to alter the serialized form of entities and XPCs. 1) Have Hibernate's EM impl expose getUnflushedChanges()/setUnflushedChanges() methods to support replication of only the unflushed changes held in the XPC, rather than all data. 2) When writing the fields in an SFSB, check if the object is a managed entity; if so write it's id to the stream rather than the whole object. 3) Deserialization process needs to ensure that any EntityManager is deserialized before the managed entities. 4) Deserialization of a managed entity would involve reading the id from the stream, identifying the EntityManager and doing a find(). 5) SFSBs should be lazy-deserialized (i.e. only deserialize if needed to handle failover). This is the way SFSBs clustering already works. This is critical, otherwise the cost of the find() operations would likely outweigh the benefits of reducing the amount of replicated data. Additionally, intent is to allow registration with the container of an impl, say, "ManagedPersistenceContextSerializer". If registered, implementation of many of the steps above would be delegated. JBoss Seam would intend to register an implementation. -- 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, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4220) Hot deployment of jars does not always work

by Scott M Stark (JIRA)

Hot deployment of jars does not always work ------------------------------------------- Key: JBAS-4220 URL: http://jira.jboss.com/jira/browse/JBAS-4220 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Scott M Stark Assigned To: Scott M Stark Due to JBMICROCONT-160, redeployment of an existing jar may not work. -- 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, 1 month

2
5
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