February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-925) PojoCache to re-try if UpgradeException occur

by Ben Wang (JIRA)

PojoCache to re-try if UpgradeException occur --------------------------------------------- Key: JBCACHE-925 URL: http://jira.jboss.com/jira/browse/JBCACHE-925 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0.BETA1 Currently, PojoCache attach & detach is prone to encoutner UpgradeException on __JBossInternal__ node. This is becuase of the flat space approach that we use such that all the POJO are stored there. As a result, UpgradeException can happen and we should catch it and re-try it. -- 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, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-771) PojoCache to have events reacting to transactional context

by Ben Wang (JIRA)

PojoCache to have events reacting to transactional context ---------------------------------------------------------- Key: JBCACHE-771 URL: http://jira.jboss.com/jira/browse/JBCACHE-771 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.1.0 Currently, the 2.0 POJO based events are not tx aware meaning they can't not react to tx rollback (and therefore not sending the events). If we want to acheieve the tx-based events, we will need to use event interceptor and react to before and afterCompletion, perhaps. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1231) Management beans initialized too many times

by Ryszard Kozmik (JIRA)

Management beans initialized too many times ------------------------------------------- Key: JBPORTAL-1231 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1231 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1, 2.6.Alpha2 Environment: AS 4.0.5 Portal 2.6Alpha1 or Alpha2 from svn tag Reporter: Ryszard Kozmik Assigned To: Julien Viet Priority: Minor Fix For: 2.6.Beta1 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalobjectmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portalAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addPageAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'addWindowAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'themePropertyAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'instancemgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'preferenceAction' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'portletmgr' - only keeping the last 10:44:14,533 WARN [FacesConfigurator] More than one managed bean w/ the name of 'createInstanceAction' - only keeping the Those warnings are harmless and are caused by newer myfaces libraries in AS 4.0.5. Please look at forum link included in this task for sollution. However, this sollution might not fully work as Portal has quite old Facelets libraries. -- 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, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1146) java.lang.NegativeArraySizeException in uploading zip archive

by Antoine Herzog (JIRA)

java.lang.NegativeArraySizeException in uploading zip archive ------------------------------------------------------------- Key: JBPORTAL-1146 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1146 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: Windows XP / JBP 2.4 Reporter: Antoine Herzog Assigned To: Roy Russo when uploading an archive file, there is an exception : java.lang.NegativeArraySizeException at org.jboss.portal.cms.impl.jcr.command.StoreArchiveCommand.execute(StoreArchiveCommand.java:72) at org.jboss.portal.cms.impl.jcr.JCRCommand.dispatch(JCRCommand.java:61) It is because of the zipEntry.getSize() that return -1 (unknown size). this is because of the use of ZipInputStream class. there is a turnaround with using the ZipFile class instead. see : http://forum.java.sun.com/thread.jspa?threadID=492219&messageID=2316626 -- 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, 9 months

5
9
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-123) Better mechanism to determine Array class

by Adrian Brock (JIRA)

Better mechanism to determine Array class ----------------------------------------- Key: JBMICROCONT-123 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-123 Project: JBoss MicroContainer Issue Type: Task Components: BeanInfo Affects Versions: JBossMC_2_0_0 Beta Reporter: Adrian Brock Priority: Minor The current implementation of getArrayClass uses the horrible public static Class getArrayClass(Class clazz, int depth) { return Array.newInstance(clazz, depth).getClass(); } there must be a better way to do this? -- 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, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-868) java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars

by William DeCoste (JIRA)

java.lang.IllegalArgumentException: Unable to find operation XYZ for dependent beans in seperate jars ----------------------------------------------------------------------------------------------------- Key: EJBTHREE-868 URL: http://jira.jboss.com/jira/browse/EJBTHREE-868 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste java.lang.IllegalArgumentException: Unable to find operation sayHello() javax.ejb.EJBException: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:69) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:102) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:263) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:999) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:848) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:454) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:527) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:261) Caused by: java.lang.IllegalArgumentException: Unable to find operation sayHello() at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:231) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy89.sayHello(Unknown Source) at org.jboss.ejb3.test.dependency.ABean.getHelloB(ABean.java:18) -- 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, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-878) correct ejb3 testsuite so that all "expected" failures do not ... well ... fail

by William DeCoste (JIRA)

correct ejb3 testsuite so that all "expected" failures do not ... well ... fail ------------------------------------------------------------------------------- Key: EJBTHREE-878 URL: http://jira.jboss.com/jira/browse/EJBTHREE-878 Project: EJB 3.0 Issue Type: Task Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: William DeCoste Assigned To: William DeCoste Fix For: EJB 3.0 RC10 - FD -- 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, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-846) PojoCache 2.0 key features

by Ben Wang (JIRA)

PojoCache 2.0 key features -------------------------- Key: JBCACHE-846 URL: http://jira.jboss.com/jira/browse/JBCACHE-846 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Manik Surtani Priority: Minor Fix For: 2.0.0.GA Manik, FYI, followings are the key features for PojoCache 2.0. When do the announcement later, please include them in. Thanks! -Ben Key PojoCache 2.0 features: 1. Supports replicated POJO field as Enum class (JBCACHE-619) 2. Option to replicate POJO final field (JBCACHE-839) 3. Support JDK5.0 only 4. PojoCache provides MBean interface (JBCACHE-783) 5. Uses a pojocache-aop.xml for configuration (JBCACHE-780) 6. Handle complete rollback of POJO field operation under transaction if needed (JBCACHE-723) 7. PojoCache to throw PojoCacheException only runtime exception (JBCACHE-700) 8. Interceptor based architecture to allow easy customization (JBCACHE-588) 9. PojoCache now uses Cache as a delegate (JBCACHE-673) 10. PojoCache event listener (JBCACHE-85) 11. During passivation, PojoCache now lazily loads the individual POJO. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-886) Upgrading from JGroups 2.2.9.2 to JGroups 2.4

by Galder Zamarreno (JIRA)

Upgrading from JGroups 2.2.9.2 to JGroups 2.4 --------------------------------------------- Key: JBCACHE-886 URL: http://jira.jboss.com/jira/browse/JBCACHE-886 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Fix For: 1.4.1.GA, 2.0.0.GA -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-967) Upgrade to JGroups 2.4.SP1

by Manik Surtani (JIRA)

Upgrade to JGroups 2.4.SP1 -------------------------- Key: JBCACHE-967 URL: http://jira.jboss.com/jira/browse/JBCACHE-967 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Affects Versions: 2.0.0.BETA1 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.BETA2, 2.0.0.GA This fixes MUX/State transfer test failures present with 2.4.GA. -- 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, 9 months

2
3
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 February 2007