April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-324) Build.xml in testsuite directory doesn't support multiple JVM argument

by Sunny Chan (JIRA)

Build.xml in testsuite directory doesn't support multiple JVM argument ---------------------------------------------------------------------- Key: JBBUILD-324 URL: http://jira.jboss.com/jira/browse/JBBUILD-324 Project: JBoss Build System Issue Type: Feature Request Components: Targets and Tasks Affects Versions: Repository Build head, Repsository Build Branch_4_0 Environment: Any Reporter: Sunny Chan Priority: Minor We are using the JBoss unit test as part of our JVM verification testsuite. We wanted to be able to invoke tests with multiple JVM options, but it didn't work. If you set parameters via build.sh -Djunit.vm.options with multiple paramters (e.g. -Djunit.vm.options="-d64 -verbose:gc"), it will fail with unrecongized option error. The problem is that in testsuite/build.xml, the junit.vm.options is passed onto junit ant task via <jvmarg value> tag rather then <jvmarg line> tag. The jvmarg line allows multiple JVM options exist in one line. Once I replace all instance of <jvmarg value="${junit.jvm.options}"/> with <jvmarg line="${junit.jvm.options}"/> then the problem goes away. I can provide a patch for this if you want - but I don't know the rules on patches (whether I need to be cleared for contribution) so let me know if you want that. -- 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, 6 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4301) Evaluate replacing FileCacheLoader with JdbmCacheLoader

by Brian Stansberry (JIRA)

Evaluate replacing FileCacheLoader with JdbmCacheLoader ------------------------------------------------------- Key: JBAS-4301 URL: http://jira.jboss.com/jira/browse/JBAS-4301 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need to establish a relationship with the JDBM guys to see how suitable and supportable it is. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-930) Simplify use of @CacheConfig

by Brian Stansberry (JIRA)

Simplify use of @CacheConfig ---------------------------- Key: EJBTHREE-930 URL: http://jira.jboss.com/jira/browse/EJBTHREE-930 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: AS 4.2.0 CR1 Reporter: Brian Stansberry Assigned To: Brian Stansberry There are two separate @CacheConfig impls -- one for the simple cache and one for the clustered. We should support something like: @Stateful @org.jboss.annotation.ejb.cache.simple.CacheConfig(maxSize=200000, idleTimeoutSeconds=500) @Remote(Test.class) public class TestBean implements Test..... where clustering is enabled via <clustered>true</clustered> in jboss.xml. Similarly, @Stateful @org.jboss.annotation.ejb.cache.tree.CacheConfig(maxSize=200000, idleTimeoutSeconds=500, replicationIsPassivation=false) @Remote(Test.class) public class TestBean implements Test..... where clustering is disabled via <clustered>false</clustered> in jboss.xml. Basically, the StatefulCache impls should check for the existence of the other @CacheConfig if the standard one isn't present. Then use the common values between the two, and the default values for any missing configurations (e.g. replicationIsPassivation). Probably the @CacheConfig annotations themselves as well as the impls should be refactored into a type hierarchy. -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-936) Allow jboss descriptor entries for unknown bean type

by Carlo de Wolf (JIRA)

Allow jboss descriptor entries for unknown bean type ---------------------------------------------------- Key: EJBTHREE-936 URL: http://jira.jboss.com/jira/browse/EJBTHREE-936 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC11 - FD Allow generic descriptor entries without knowing the bean type. The following could be specified in '<session>', but we don't want to know the actual annotation. So it should possible to use '<ejb>'. <jboss xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <enterprise-beans> <ejb> <ejb-name>MyStatelessBean</ejb-name> <resource-ref> <res-ref-name>qFactory</res-ref-name> <jndi-name>ConnectionFactory</jndi-name> </resource-ref> </ejb> </enterprise-beans> </jboss> -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-931) ejb-link with relative path not working

by Carlo de Wolf (JIRA)

ejb-link with relative path not working --------------------------------------- Key: EJBTHREE-931 URL: http://jira.jboss.com/jira/browse/EJBTHREE-931 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD 12:44:55,904 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_ejb.jar,name=RemoteCalculatorBean,service=EJB3 with dependencies: 12:44:59,748 INFO [EJBContainer] STARTED EJB: com.sun.ts.tests.ejb30.bb.session.stateful.basic.RemoteCalculatorBean ejbName: RemoteCalculatorBean 12:44:59,995 WARN [DeploymentEjbResolver] can't find a deployment for path '' of ejb link '#RemoteCalculatorBean' 12:44:59,996 WARN [EJBHandler] IGNORING DEPENDENCY: unable to find <ejb-ref> of interface com.sun.ts.tests.ejb30.bb.session.stateful.basic.StatefulRemoteCalculator and ejbLink of ejb3_bb_stateful_basic_ejb.jar#RemoteCalculatorBean in application-client.xml of ejb3_bb_stateful_basic_client it might not be deployed yet12:45:00,022 INFO [MCKernelAbstraction] installing bean: jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_client.jar,name=ejb3_bb_stateful_basic_client,service=EJB3 with dependencies: 12:45:00,256 WARN [DeploymentEjbResolver] can't find a deployment for path '' of ejb link '#RemoteCalculatorBean' 12:45:00,258 ERROR [AbstractKernelController] Error installing to Start: name=jboss.j2ee:ear=ejb3_bb_stateful_basic.ear,jar=ejb3_bb_stateful_basic_client.jar,name=ejb3_bb_stateful_basic_client,service=EJB3 state=Create java.lang.RuntimeException: Failed to populate ENC: env/ejb/RemoteCalculatorBean global jndi name was 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-947) Relaxed signature checking

by Carlo de Wolf (JIRA)

Relaxed signature checking -------------------------- Key: EJBTHREE-947 URL: http://jira.jboss.com/jira/browse/EJBTHREE-947 Project: EJB 3.0 Issue Type: Feature Request Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD Allow RuntimeException throwing if relaxed signature checking is on for methods which should not throw any exception (EJB3 12.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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-910) AllowedSuffixes in the deployer has inverted logic

by Carlo de Wolf (JIRA)

AllowedSuffixes in the deployer has inverted logic -------------------------------------------------- Key: EJBTHREE-910 URL: http://jira.jboss.com/jira/browse/EJBTHREE-910 Project: EJB 3.0 Issue Type: Bug Environment: trunk Reporter: Carlo de Wolf Fix For: EJB 3.0 RC11 - FD Specifying AllowedSuffixes on the EJB3 deployer actually makes it ignore those and pick up the others. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-893) Set hibernate.session_factory_name to an appropriate default if the user don't

by Emmanuel Bernard (JIRA)

Set hibernate.session_factory_name to an appropriate default if the user don't ------------------------------------------------------------------------------ Key: EJBTHREE-893 URL: http://jira.jboss.com/jira/browse/EJBTHREE-893 Project: EJB 3.0 Issue Type: Feature Request Reporter: Emmanuel Bernard Fix For: EJB 3.0 RC11 - FD This is useful for clustering http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4017398#4017398 -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-861) Dependencies should be registered using a canonical name

by Carlo de Wolf (JIRA)

Dependencies should be registered using a canonical name -------------------------------------------------------- Key: EJBTHREE-861 URL: http://jira.jboss.com/jira/browse/EJBTHREE-861 Project: EJB 3.0 Issue Type: Feature Request Affects Versions: EJB 3.0 RC9 - Patch 1 Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD Tip from Adrian: Why don't you just fix it like the ServiceMetaData does when it doesn't know whether it is dealing with a bean name or ObjectName? String dependency = ... try { ObjectName on = new ObjectName(dependency); dependency = on.getCanonicalName(); } catch (MalformedObjectName ignored) { // Not an object name } -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-840) OutOfMemoryError: Java heap space

by Carlo de Wolf (JIRA)

OutOfMemoryError: Java heap space --------------------------------- Key: EJBTHREE-840 URL: http://jira.jboss.com/jira/browse/EJBTHREE-840 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - Patch 1 Environment: AS 4.2 (20070122) Reporter: Carlo de Wolf Priority: Critical Fix For: EJB 3.0 RC10 - FD OutOfMemoryError when running microbench -- 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, 7 months

3
15
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 2007