March 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-1226) javax.ejb.EJBContext.lookup must throw IllegalArgumentException if nothing is found

by Carlo de Wolf (JIRA)

javax.ejb.EJBContext.lookup must throw IllegalArgumentException if nothing is found ----------------------------------------------------------------------------------- Key: EJBTHREE-1226 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1226 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Carlo de Wolf Fix For: AS 5.0.0.CR1 http://java.sun.com/javaee/5/docs/api/javax/ejb/EJBContext.html#lookup(ja... The Container throws the exception if the given name does not match an entry within the component's environment. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-152) Dependency names need to be validated earlier

by Scott M Stark (JIRA)

Dependency names need to be validated earlier --------------------------------------------- Key: JBMICROCONT-152 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-152 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta3 I'm seeing an error like the following testing profileservice attachments overrides: Caused by: java.lang.IllegalArgumentException: Null name at org.jboss.dependency.plugins.AbstractController.getContext(AbstractController.java:129) at org.jboss.kernel.plugins.dependency.AbstractKernelController.getContext(AbstractKernelController.java:101) at org.jboss.dependency.plugins.AbstractDependencyItem.resolve(AbstractDependencyItem.java:117) at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:128) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:595) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:531) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) at org.jboss.system.ServiceController.doInstall(ServiceController.java:638) at org.jboss.system.ServiceController.install(ServiceController.java:271) This error regarding the invalid dependency item name not showing up until there is an attempt to resolve it makes it impossible to debug the problem as there is no context in the dependency to understand why its null. -- 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, 4 months

3
11
0 / 0

[JBoss JIRA] Resolved: (JBMICROCONT-25) Configurator tidyup

by Ales Justin (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-25?page=all ] Ales Justin resolved JBMICROCONT-25. ------------------------------------ Resolution: Done Removed the fixme for the absence of classlaoder. It's users fault if one is not provided. > Configurator tidyup > ------------------- > > Key: JBMICROCONT-25 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-25 > Project: JBoss MicroContainer > Issue Type: Task > Components: Configurator > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Minor > Fix For: JBossMC.2.0.0.CR1 > > > The Configurator api is largely being replaced by the JoinPointFactory api. > There is still a usecase for some of the Configurator api as a convenience mechanism > on top of the JoinPointFactory. > This needs cleaning up. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5189) Txn-Manager arjuna commits data after timeout in long transactions

by Rￃﾼdiger Schmitz (JIRA)

Txn-Manager arjuna commits data after timeout in long transactions ------------------------------------------------------------------ Key: JBAS-5189 URL: http://jira.jboss.com/jira/browse/JBAS-5189 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-4.2.0.GA Reporter: Rￃﾼdiger Schmitz Assigned To: Adrian Brock We encountered the following situation: Within an ejb using hibernate (and it's JTA transaction manager) we execute a long transaction. When the transaction run-time exceeds the arjuna timeout, the container outputs the following message: > Abort of action id -5ea551d8:b05:47a18b1f:2f invoked while multiple threads active within it > CheckedAction::check - atomic action -5ea551d8:b05:47a18b1f:2f aborting with 1 threads active! After this, all following operations are directly committed to the database! So, basically we have two problems: - The timeout of the txn-manager triggers, even while the current database transaction is in continuous heavy use (numerous inserts/selects per second) - Instead of aborting with an exception at once, the transaction manager happily carries on accepting data - The data sent to the database _before_ the timeout is discard - The data sent to the database _after_ the timeout is committed to the database. This results in inconsistent data within the database - After the ejb-method commits an exception is thrown, leaving the database in an inconsistent state. A workaround is of course to increase the transaction manager timeout, but this defeats the purpose of the timeout. Furthermore, the duration of a transaction cannot always be estimated. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-10) OSGi Listeners

by Adrian Brock (JIRA)

OSGi Listeners -------------- Key: JBOSGI-10 URL: http://jira.jboss.com/jira/browse/JBOSGI-10 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock OSGi defines three types of listeners 1) Framework listener for global events related to the server 2) Bundle listener for events related to the deployments 3) Service listener for events related services Where these already exist, these need to be "adapted" to the OSGi api. The missing notifications need to be implemented. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREL-1) Setup the svn repository for jboss reliance

by Adrian Brock (JIRA)

Setup the svn repository for jboss reliance ------------------------------------------- Key: JBREL-1 URL: http://jira.jboss.com/jira/browse/JBREL-1 Project: JBoss Reliance Issue Type: Task Components: general Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossReliance-2.0.0.Beta11 Setup the svn repository for reliance -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-4) Deployer changes for OSGi

by Adrian Brock (JIRA)

Deployer changes for OSGi ------------------------- Key: JBOSGI-4 URL: http://jira.jboss.com/jira/browse/JBOSGI-4 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock This is a holder task for the Deployer changes need to make OSGi work and integrate OSGi bundles with other JBoss deployments (and vice versa). -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-7) OSGi ClassLoader

by Adrian Brock (JIRA)

OSGi ClassLoader ---------------- Key: JBOSGI-7 URL: http://jira.jboss.com/jira/browse/JBOSGI-7 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock Implementation of the OSGi classloader. This should be usable for both OSGi bundles and all other JBoss deployments. An new classloader.xml will be supported such that non OSGi deployments can specify their classloading constraints (import, export, etc.) Additionally, it should provide support for things outside the OSGi spec that are required in JavaEE or for backwards compatibility like scoping and j2se classloading compliance. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-15) Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy

by Adrian Brock (JIRA)

Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy --------------------------------------------------------------------------------- Key: JBOSGI-15 URL: http://jira.jboss.com/jira/browse/JBOSGI-15 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Once the VFSClassLoader is done JBOSGI-14, we need to create a concrete subclass that allows injectable policy. i.e. setters. This will be used by the both JBossAS and OSGi through the Deployer layer to construct classloaders from the classloading dependencies/rules they define. -- 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, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-241) Cutover the deployers to use the new public classloading spi

by Adrian Brock (JIRA)

Cutover the deployers to use the new public classloading spi ------------------------------------------------------------ Key: JBMICROCONT-241 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-241 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.CR1 Integerate the new classloading spi into the deployers. -- 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, 4 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 March 2008