August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1162) Node.clearData() does not rollback correctly

by Jason T. Greene (JIRA)

Node.clearData() does not rollback correctly -------------------------------------------- Key: JBCACHE-1162 URL: http://jira.jboss.com/jira/browse/JBCACHE-1162 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Jason T. Greene Assigned To: Manik Surtani -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1160) org.jboss.cache.pojo.rollback.InMemoryTxUndoTest (tcp & udp) test failure

by Rajesh Rajasekaran (JIRA)

org.jboss.cache.pojo.rollback.InMemoryTxUndoTest (tcp & udp) test failure ------------------------------------------------------------------------- Key: JBCACHE-1160 URL: http://jira.jboss.com/jira/browse/JBCACHE-1160 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Rajesh Rajasekaran Assigned To: Jason T. Greene http://cruisecontrol.jboss.com/cc/artifacts/jboss-cache-testsuite/2007080... The test attaches a second Person object to an existing node (Person object) within the scope of a transaction and rolls back. The following exception occurs when trying to retrieve the first object. testSimpleTxWithRollback3 Error org.jboss.cache.pojo.test.Person@140984b has possibly been detached remotely. Internal id: /__JBossInternal__/a/_ID_/1s225g61-ezjyl3-f50xq5j0-1-f50xq5o0-4 org.jboss.cache.pojo.PojoCacheAlreadyDetachedException: org.jboss.cache.pojo.test.Person@140984b has possibly been detached remotely. Internal id: /__JBossInternal__/a/_ID_/1s225g61-ezjyl3-f50xq5j0-1-f50xq5o0-4 at org.jboss.cache.pojo.interceptors.dynamic.CacheFieldInterceptor.verifyAttached(CacheFieldInterceptor.java:177) at org.jboss.cache.pojo.interceptors.dynamic.CacheFieldInterceptor.invoke(CacheFieldInterceptor.java:153) at org.jboss.cache.pojo.test.Person$age_Get.invokeNext(Person$age_Get.java) at org.jboss.cache.pojo.test.Person.age_r_$aop(Person.java) at org.jboss.cache.pojo.test.Person.getAge(Person.java:76) at org.jboss.cache.pojo.rollback.InMemoryTxUndoTest.testSimpleTxWithRollback3(InMemoryTxUndoTest.java:121) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBAS-2299) OutOfMemory error when repetatively deploying and undeploying with 10 minute interval

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2299?page=all ] Clebert Suconic closed JBAS-2299. --------------------------------- Fix Version/s: (was: JBossAS-4.2.2.GA) Resolution: Rejected This is a Jakarta commons issue... not a JBoss issue I have created a testcase that replicates this and submitted to them... https://issues.apache.org/jira/browse/BEANUTILS-291 There is nothing else we can do about this now.. we could just wait and see if they will fix it! > OutOfMemory error when repetatively deploying and undeploying with 10 minute interval > ------------------------------------------------------------------------------------- > > Key: JBAS-2299 > URL: http://jira.jboss.com/jira/browse/JBAS-2299 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3RC2 > Environment: WinXP SP2, JBoss 4.0.3RC2, JDK 1.4.2_07 > Reporter: Amar Syed > Assigned To: Clebert Suconic > Attachments: Data.txt, SampleApp.ear, Sampleapp.zip > > Time Spent: 2 hours > Remaining Estimate: 0 minutes > > Using a manual copy and delete mechanism with the server\default\deploy folder the sample ear (attached) caused an outofmemory error eventually after 90 repetitions. > The min and max heap settings were configured as : -Xms128m -Xmx512m > The time delay after dropping/deploying the ear at each repetition was set to 10 minutes after which the ear is deleted/undeployed followed by a 10 second sleep till the next deploy cycle. > I find this behaviour strange because http://jira.jboss.com/jira/browse/JBAS-1319 is supposed to have fixed this issue. > The lines from the server.log surrounding the java.lang.OutOfMemoryError are as follows: > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > 2005-09-24 06:04:31,413 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@e51e50, cl=org.jboss.mx.loading.UnifiedClassLoader3@c90207{ url=null ,addedOrder=0} > 2005-09-24 06:04:33,057 ERROR [org.apache.commons.digester.Digester] Begin event threw error > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] StandardWrapper.Throwable > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,057 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/XMPVXE0Partion/VXE1_ContentTestService]] Servlet /XMPVXE0Partion/VXE1_ContentTestService threw load() exception > java.lang.OutOfMemoryError > 2005-09-24 06:04:33,072 DEBUG [org.jboss.mx.loading.UnifiedClassLoader] New jmx UCL with url null > The following two jars were added to the server\default\lib folder. > commons-validator.jar --- version 1.1.3 > struts.jar ---- version 1.2.4 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-390) Update jboss retro site on jboss.org.

by Paul Gier (JIRA)

Update jboss retro site on jboss.org. ------------------------------------- Key: JBBUILD-390 URL: http://jira.jboss.com/jira/browse/JBBUILD-390 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 Update jbossretro on jboss.org (http://labs.jboss.com/jbossretro). The site content should be generated by maven. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1622) Implement "admin" portlet mode

by Julien Viet (JIRA)

Implement "admin" portlet mode ------------------------------ Key: JBPORTAL-1622 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1622 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.1 Final, 2.8 Final Reporter: Julien Viet Assigned To: Julien Viet Fix For: 2.6.2 Final, 2.8 Final -- 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, 11 months

1
1
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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1161) PojoCache loadtime example failure

by Rajesh Rajasekaran (JIRA)

PojoCache loadtime example failure ---------------------------------- Key: JBCACHE-1161 URL: http://jira.jboss.com/jira/browse/JBCACHE-1161 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Rajesh Rajasekaran Assigned To: Jason T. Greene The following exceptions occurs when running the example under JBossCache-pojo-2.0.0.GA\examples\PojoCache\loadtime "build.bat compile" & "build.bat run.loadtime.example" [java] Exception in thread "main" java.lang.IllegalArgumentException: PojoCache.putObject(): Object type is neither aspectized nor Serializable nor an array of prim itives. Object class name is examples.Student [java] at org.jboss.cache.pojo.util.AopUtil.checkObjectType(AopUtil.java:125) [java] at org.jboss.cache.pojo.interceptors.CheckNonSerializableInterceptor.invoke(CheckNonSerializableInterceptor.java:36) [java] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) [java] at org.jboss.cache.pojo.impl.PojoCacheImpl$attach_3085019539260813833.invokeNext(PojoCacheImpl$attach_3085019539260813833.java) [java] at org.jboss.cache.pojo.interceptors.CheckIdInterceptor.invoke(CheckIdInterceptor.java:33) [java] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) [java] at org.jboss.cache.pojo.impl.PojoCacheImpl$attach_3085019539260813833.invokeNext(PojoCacheImpl$attach_3085019539260813833.java) [java] at org.jboss.cache.pojo.interceptors.PojoBeginInterceptor.invoke(PojoBeginInterceptor.java:36) [java] at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105) [java] at org.jboss.cache.pojo.impl.PojoCacheImpl$attach_3085019539260813833.invokeNext(PojoCacheImpl$attach_3085019539260813833.java) [java] at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java) [java] at org.jboss.cache.pojo.impl.PojoCacheImpl.attach(PojoCacheImpl.java:93) [java] at test.examples.StudentMaintTest.testPropagation(StudentMaintTest.java:99) [java] at test.examples.StudentMaintTest.main(StudentMaintTest.java:145) [java] Java Result: 1 -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (SWAP-25) Update MyFaces JSF tutorial portlet to work with 2.6 and AS 4.2

by Chris Laprun (JIRA)

Update MyFaces JSF tutorial portlet to work with 2.6 and AS 4.2 --------------------------------------------------------------- Key: SWAP-25 URL: http://jira.jboss.com/jira/browse/SWAP-25 Project: PortletSwap Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Chris Laprun Assigned To: Julien Viet Tutorial portlet is out of date as MyFaces is not bundled anymore. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-2861) HttpSession sharing between WAR modules

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2861?page=all ] Hany Mesha reassigned JBAS-2861: -------------------------------- Assignee: Hany Mesha (was: Brian Stansberry) > HttpSession sharing between WAR modules > --------------------------------------- > > Key: JBAS-2861 > URL: http://jira.jboss.com/jira/browse/JBAS-2861 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Affects Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Fix For: JBossAS-4.2.2.GA > > > Creating a redacted version of JBAS-1909, which was opened as a non-public JIRA issue by a customer. > Our J2EE application is composed of several modules, each one addressing one facet of our business process, and currently this application has one web module (WAR) and several JAR modules (EJB). > We need to divide this web module into several smaller web modules. > In order to separate our unique WAR file into several WARs we must guarantee HttpSession sharing. This is due to the fact that we have a lot of session attributes that are used throughout the entire application and we cannot afford to refactor the application, in fact, that's impossible. > The security aspects for this requirement are completely addressed by the JBoss/Tomcat Single Sign-On mechanism but the session sharing requirements are not. > The ideal scenario is to keep the same HttpSession (same object in the heap, same session ID) when authenticating into one application (HttpSession created) and then forwarding to another application. > The current SSO mechanism allows the user to access the second application without reauthentication, as you know, but it creates a new HttpSession object. Also, if the two WARs have different session timeouts, if you access application A, migrates to application B, stays there until session in application A expires and then returns to application A from application B, a new HttpSession is also created in application A. > The ideal solution is to have one unique, monolithic session to all web applications configured to share a common session. IBM WebSphere and BEA WebLogic do have this configuration and feature. Please check the links below in case you want more information: > WebSphere Application Server V5: Sharing Session Context - http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/tips0215.ht... > BEA Weblogic - Enabling Web applications to share the same session - http://e-docs.bea.com/wls/docs90/webapp/sessions.html -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (GPD-121) remove lookup of current editor to obtain commandstack

by Koen Aers (JIRA)

remove lookup of current editor to obtain commandstack ------------------------------------------------------ Key: GPD-121 URL: http://jira.jboss.com/jira/browse/GPD-121 Project: JBoss jBPM GPD Issue Type: Task Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.beta1 Reporter: Koen Aers Assigned To: Koen Aers Fix For: jBPM JPDL Designer 3.1.0.beta2 -- 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, 11 months

1
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 August 2007