April 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1227) Workaround for JBossGenericBeanMetaData showing up

by Carlo de Wolf (JIRA)

Workaround for JBossGenericBeanMetaData showing up -------------------------------------------------- Key: EJBTHREE-1227 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1227 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Priority: Blocker Fix For: AS 5.0.0.CR1 java.lang.IllegalStateException: Can't find a generic bean meta data wrapper for class org.jboss.metadata.ejb.jboss.JBossMessageDrivenBeanMetaData at org.jboss.ejb3.Ejb3Deployment.getEnterpriseBeanMetaData(Ejb3Deployment.java:829) at org.jboss.ejb3.Ejb3AnnotationHandler.getEnterpriseBeanMetaData(Ejb3AnnotationHandler.java:132) at org.jboss.ejb3.Ejb3AnnotationHandler.getContainers(Ejb3AnnotationHandler.java:215) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:606) at org.jboss.ejb3.Ejb3Deployment.deployElement(Ejb3Deployment.java:566) at org.jboss.ejb3.Ejb3Deployment.deployUrl(Ejb3Deployment.java:548) at org.jboss.ejb3.Ejb3Deployment.deploy(Ejb3Deployment.java:514) at org.jboss.ejb3.Ejb3Deployment.create(Ejb3Deployment.java:426) at org.jboss.ejb3.deployers.Ejb3Deployer.deploy(Ejb3Deployer.java:157) -- 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
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1259) Determine how to model stateful component with mc based component factory

by Scott M Stark (JIRA)

Determine how to model stateful component with mc based component factory ------------------------------------------------------------------------- Key: EJBTHREE-1259 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1259 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Scott M Stark Assigned To: Scott M Stark Since the mc does not support a non-linear state machine, we will need to model the stateful behavior by having the bean context manage the lifecycle callbacks. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBRULES-1556) Modify is not normalising activations, which is impacting lock-on-active

by Mark Proctor (JIRA)

Modify is not normalising activations, which is impacting lock-on-active ------------------------------------------------------------------------ Key: JBRULES-1556 URL: http://jira.jboss.com/jira/browse/JBRULES-1556 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.6, 4.0.5, 4.0.4, 4.0.3 Reporter: Mark Proctor Assigned To: Mark Proctor Fix For: 4.0.7 when using the modify keyword, which uses modifyRetract and modifyInsert underneath the activations are not normalised. Which means on lock-on-active activations that where originally there are not able to re-active on a modify. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-5391) Break AS Asynchronous Aspect into EJB3 "async" Component

by Andrew Lee Rubinger (JIRA)

Break AS Asynchronous Aspect into EJB3 "async" Component -------------------------------------------------------- Key: JBAS-5391 URL: http://jira.jboss.com/jira/browse/JBAS-5391 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Andrew Lee Rubinger Priority: Blocker Fix For: JBossAS-5.0.0.CR1 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-1325) ClassLoader and probable memory leak in ReusableObjectInputStream

by Brian Stansberry (JIRA)

ClassLoader and probable memory leak in ReusableObjectInputStream ----------------------------------------------------------------- Key: JBCACHE-1325 URL: http://jira.jboss.com/jira/browse/JBCACHE-1325 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.1.0.GA Reporter: Brian Stansberry Assigned To: Manik Surtani Priority: Critical Fix For: 2.1.1.GA java.io.ObjectInputStream maintains an internal table of objects it has deserialized. If you don't close the stream (i.e. try to reuse it) that table doesn't get cleared. A classloader leak analysis I'm doing shows this as a cause of a classloader leak; looking at the java.io.ObjectInputStream code's use of its HandleTable inner class makes me think not closing the stream is very likely a memory leak as well. Reference chain leading to a leaked classloader: !--BaseClassLoader@7441b1fd{vfsfile:/home/bes/dev/jboss/trunk/testsuite/output/lib/cluster-clleak-field.war} !--!--ClassLoaderReference @ class org.jboss.test.cluster.web.aop.Person !--!--!--arrayRef [Ljava.lang.Object;[23] id=@1804215529 !--!--!--!--FieldReference java.lang.Object[] java.io.ObjectInputStream$HandleTable.entries=java.io.ObjectInputStream$HandleTable@254ca71 !--!--!--!--!--FieldReference UndefinedField@org.jboss.cache.marshall.io.ReusableObjectInputStream@3274ae84=org.jboss.cache.marshall.io.ReusableObjectInputStream(a)3274ae84 !--!--!--!--!--!--FieldReference volatile java.lang.Object java.util.concurrent.LinkedBlockingQueue$Node.item=java.util.concurrent.LinkedBlockingQueue$Node@185d3a64 !--!--!--!--!--!--!--FieldReference private transient java.util.concurrent.LinkedBlockingQueue$Node java.util.concurrent.LinkedBlockingQueue.last=[org.jboss.cache.marshall.io.ReusableObjectInputStream@59e8f902, org.jboss.cache.marshall.io.ReusableObjectInputStream@4e34206b, org.jboss.cache.marshall.io.ReusableObjectInputStream@403c78e9, org.jboss.cache.marshall.io.ReusableObjectInputStream@422629f1, org.jboss.cache.marshall.io.ReusableObjectInputStream@578baf24, org.jboss.cache.marshall.io.ReusableObjectInputStream@13979163, org.jboss.cache.marshall.io.ReusableObjectInputStream@43ca04a1, org.jboss.cache.marshall.io.ReusableObjectInputStream@3f608cc, org.jboss.cache.marshall.io.ReusableObjectInputStream@dbb8b1c, org.jboss.cache.marshall.io.ReusableObjectInputStream@13a9e24f, org.jboss.cache.marshall.io.ReusableObjectInputStream@7648ba9e, org.jboss.cache.marshall.io.ReusableObjectInputStream@20d417bd, org.jboss.cache.marshall.io.ReusableObjectInputStream@44628a21, org.jboss.cache.marshall.io.ReusableObjectInputStream@215a9f9a, org.jboss.cache.marshall.io.ReusableObjectInputStream@44a44891, org.jboss.cache.marshall.io.ReusableObjectInputStream@7d984acb, org.jboss.cache.marshall.io.ReusableObjectInputStream@195695d8, org.jboss.cache.marshall.io.ReusableObjectInputStream@387a4e7, org.jboss.cache.marshall.io.ReusableObjectInputStream@3e5b3b80, org.jboss.cache.marshall.io.ReusableObjectInputStream@579f707b, org.jboss.cache.marshall.io.ReusableObjectInputStream@2491c82e, org.jboss.cache.marshall.io.ReusableObjectInputStream@5eed56c3, org.jboss.cache.marshall.io.ReusableObjectInputStream@2fdb4ce5, org.jboss.cache.marshall.io.ReusableObjectInputStream@669566ee, org.jboss.cache.marshall.io.ReusableObjectInputStream@5a98c7df, org.jboss.cache.marshall.io.ReusableObjectInputStream@646a2ff0, org.jboss.cache.marshall.io.ReusableObjectInputStream@77716910, org.jboss.cache.marshall.io.ReusableObjectInputStream@36a8d6b3, org.jboss.cache.marshall.io.ReusableObjectInputStream@6a79dce, org.jboss.cache.marshall.io.ReusableObjectInputStream@666942cb, org.jboss.cache.marshall.io.ReusableObjectInputStream@8a051f4, org.jboss.cache.marshall.io.ReusableObjectInputStream@55646e98, org.jboss.cache.marshall.io.ReusableObjectInputStream@3498e8f4, org.jboss.cache.marshall.io.ReusableObjectInputStream@22e60626, org.jboss.cache.marshall.io.ReusableObjectInputStream@2b9dbab0, org.jboss.cache.marshall.io.ReusableObjectInputStream@4b8f2f, org.jboss.cache.marshall.io.ReusableObjectInputStream@60a556cf, org.jboss.cache.marshall.io.ReusableObjectInputStream@6e6619b, org.jboss.cache.marshall.io.ReusableObjectInputStream@7f120aa6, org.jboss.cache.marshall.io.ReusableObjectInputStream@79795976, org.jboss.cache.marshall.io.ReusableObjectInputStream@de09048, org.jboss.cache.marshall.io.ReusableObjectInputStream@12206e16, org.jboss.cache.marshall.io.ReusableObjectInputStream@f1b6fa6, org.jboss.cache.marshall.io.ReusableObjectInputStream@523f0309, org.jboss.cache.marshall.io.ReusableObjectInputStream@26e06e0e, org.jboss.cache.marshall.io.ReusableObjectInputStream@58596d12, org.jboss.cache.marshall.io.ReusableObjectInputStream@5707e60e, org.jboss.cache.marshall.io.ReusableObjectInputStream@4790cdc5, org.jboss.cache.marshall.io.ReusableObjectInputStream@73b56537, org.jboss.cache.marshall.io.ReusableObjectInputStream@3274ae84] !--!--!--!--!--!--!--!--FieldReference java.util.concurrent.BlockingQueue org.jboss.cache.marshall.io.ObjectStreamPool.inputStreams=org.jboss.cache.marshall.io.ObjectStreamPool@21e513fb !--!--!--!--!--!--!--!--!--FieldReference org.jboss.cache.marshall.io.ObjectStreamPool org.jboss.cache.marshall.VersionAwareMarshaller.pool=org.jboss.cache.marshall.VersionAwareMarshaller@37760a63 -- 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
1
0 / 0

[JBoss JIRA] Created: (JBAS-5408) Redesign Async Aspect

by Andrew Lee Rubinger (JIRA)

Redesign Async Aspect --------------------- Key: JBAS-5408 URL: http://jira.jboss.com/jira/browse/JBAS-5408 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1 The current Async Aspect has a dependency on the Remoting Aspect, violating the cross-cutting orthogonal model. This design flaw should be eliminated, leaving "async" unaware of local/remote context. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1983) Inconsistent entries in language drop-downs

by Martin Putz (JIRA)

Inconsistent entries in language drop-downs ------------------------------------------- Key: JBPORTAL-1983 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1983 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS, Portal Core Admin Affects Versions: 2.6.4 Final Reporter: Martin Putz Assigned To: Sohil Shah Throughout the portal, there are several places with language lists offered as drop-down boxes, and the list of entries they offer are not consistent. Moreover, some are localized, some are not: Admin portlet -> page management -> 'Display names': Localized list, based on java.util.Local#getAvailableLocales, only entries for different languages are shown CMS admin portlet -> Create new file: Not localized list, based on java.util.Local#getISOLanguages User portlet -> Edit profile: Localized list, based on java.util.Local#getAvailableLocales, all entries are shown This should be consolidated throughout the Portal. -- 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
0
0 / 0

[JBoss JIRA] Created: (JBAS-5389) EJB3 ClientLauncher not available

by Thomas Diesler (JIRA)

EJB3 ClientLauncher not available --------------------------------- Key: JBAS-5389 URL: http://jira.jboss.com/jira/browse/JBAS-5389 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.CR1 [javac] /home/tdiesler/svn/jbossws/stack/native/trunk/src/test-framework/java/org/jboss/test/ws/jaxws/samples/webserviceref/WebServiceRefClientTestCase.java:31: package org.jboss.ejb3.client does not exist [javac] import org.jboss.ejb3.client.ClientLauncher; [javac] ^ [javac] /home/tdiesler/svn/jbossws/stack/native/trunk/src/test-framework/java/org/jboss/test/ws/jaxws/samples/webserviceref/WebServiceRefClientTestCase.java:80: cannot find symbol -- 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
2
0 / 0

[JBoss JIRA] Commented: (JBAS-2408) JCA1.5 EJB3 integration

by Jesper Pedersen (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2408?page=comments#action_12408236 ] Jesper Pedersen commented on JBAS-2408: --------------------------------------- A new forum thread on this task: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4143396 > JCA1.5 EJB3 integration > ----------------------- > > Key: JBAS-2408 > URL: http://jira.jboss.com/jira/browse/JBAS-2408 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Reporter: Adrian Brock > Assigned To: Jesper Pedersen > Fix For: JBossAS-4.2.3.GA > > > Need to refactor JCA1.5 inbound messaging to work with both EJB2.1 and EJB3.0 -- 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
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1258) Remove Oswego usage

by Jesper Pedersen (JIRA)

Remove Oswego usage ------------------- Key: EJBTHREE-1258 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1258 Project: EJB 3.0 Issue Type: Task Components: core Reporter: Jesper Pedersen Assigned To: Jesper Pedersen Fix For: AS 5.0.0.CR1 Remove the usage of Oswego classes by using the classes from the java.util.concurrent package instead -- 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
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 April 2008