July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1026) add-jms-queue --help does not work inside a batch

by Brian Stansberry (JIRA)

add-jms-queue --help does not work inside a batch ------------------------------------------------- Key: AS7-1026 URL: https://issues.jboss.org/browse/AS7-1026 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.0.Beta3 Reporter: Brian Stansberry [standalone@localhost:9999 subsystem=messaging] batch [standalone@localhost:9999 subsystem=messaging #] add- add-data-source add-jms-cf add-jms-queue add-jms-topic add-xa-data-source [standalone@localhost:9999 subsystem=messaging #] add-jms- add-jms-cf add-jms-queue add-jms-topic [standalone@localhost:9999 subsystem=messaging #] add-jms-queue --help Failed to add to batch: Required argument '--name' is missing. Discard the batch (or don't start one at all) and it works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBSER-119) Ensure compatibility with Trove

by Christian Effertz (JIRA)

Ensure compatibility with Trove ------------------------------- Key: JBSER-119 URL: https://jira.jboss.org/jira/browse/JBSER-119 Project: JBoss Serialization Issue Type: Thirdparty Change Affects Versions: 1.0.3 GA Reporter: Christian Effertz Assignee: Clebert Suconic Fix For: 1.1.0 Beta The version of [Trove|http://trove4j.sourceforge.net] that is shipped with the latest version of JBoss Serialization is quite old. Trove has had a major release since it was bundled last time for Version 1.0.3 and seems to be facing a next major version 3.0. As it is stated in their release notes that they had some performance improvements and Bug Fixes I would assume that JBoss Serialization would profit in terms of stability and performance if using the newer versions. I will give it a try in our dev system, but it would be more comforting to get a statement if your testsuite turned green if using the newer version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1291) UserTransaction not exposed in JDNI

by Juergen Zimmermann (JIRA)

UserTransaction not exposed in JDNI ----------------------------------- Key: AS7-1291 URL: https://issues.jboss.org/browse/AS7-1291 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.0.0.Final Environment: 7.1.0.Alpha1 Jenkins build 1402 Reporter: Juergen Zimmermann Assignee: John Bailey In JBoss 6 UserTransaction was exposed in JNDI named as java:comp/UserTransaction. Thus an Arquillian test method could be encapsulated in one single transaction: * lookup() the UserTransaction * begin() inside @Before * commit() inside @After Unfortunately, JBoss 7 doesn't have a JNDI entry for UserTransaction. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

8
11
0 / 0

[JBoss JIRA] Created: (JBAS-9072) High level commands for common standalone mode tasks

by Brian Stansberry (JIRA)

High level commands for common standalone mode tasks ---------------------------------------------------- Key: JBAS-9072 URL: https://issues.jboss.org/browse/JBAS-9072 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assignee: Alexey Loubyansky Fix For: 7.0.0.Beta3 Identify and implement the high level commands we want to support for a standalone mode server. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-1034) ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL

by Scott Marlow (JIRA)

ignore persistence unit definitions that have PersistenceUnitTransactionType = RESOURCE_LOCAL --------------------------------------------------------------------------------------------- Key: AS7-1034 URL: https://issues.jboss.org/browse/AS7-1034 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Beta3 Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-9049) Need way to override the boot.log in start scripts

by Scott Stark (JIRA)

Need way to override the boot.log in start scripts -------------------------------------------------- Key: JBAS-9049 URL: https://issues.jboss.org/browse/JBAS-9049 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Logging Affects Versions: 7.0.0.Beta1 Reporter: Scott Stark Assignee: David Lloyd We need the ability to specify the location of the boot.log. Right now the boot.log location is specified via the org.jboss.boot.log.file java system property, but this is always set to $JBOSS_HOME/standalone/log/boot.log in the server start scripts. This should either not be set and simply default to $JBOSS_HOME/standalone/log/boot.log when unset so that it may be passed into the jvm, or, we need a JBOSS_BOOT_LOG env property that can override this value along the line of: if [ "x$JBOSS_BOOT_LOG" = "x" ]; then JBOSS_BOOT_LOG="$JBOSS_HOME/standalone/log/boot.log" fi while true; do if [ "x$LAUNCH_JBOSS_IN_BACKGROUND" = "x" ]; then # Execute the JVM in the foreground eval \"$JAVA\" $JAVA_OPTS \ \"-Dorg.jboss.boot.log.file=$JBOSS_BOOT_LOG\" \ ... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

5
9
0 / 0

[JBoss JIRA] Created: (JBEE-22) Add jboss-jaxrs-api_1.1_spec

by Shelly McGowan (JIRA)

Add jboss-jaxrs-api_1.1_spec ---------------------------- Key: JBEE-22 URL: https://jira.jboss.org/jira/browse/JBEE-22 Project: JBoss JavaEE APIs Issue Type: Sub-task Reporter: Shelly McGowan -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

1
9
0 / 0

[JBoss JIRA] Created: (LOGTOOL-24) Better support for Maven logging messages

by James Perkins (JIRA)

Better support for Maven logging messages ----------------------------------------- Key: LOGTOOL-24 URL: https://issues.jboss.org/browse/LOGTOOL-24 Project: Log Tool Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: James Perkins Assignee: David Lloyd Maven only prints error and warning messages. Check for ways to print informational and possibly debug messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1330) EJB timer service should use a thread pool to avoid OOM

by Galder Zamarreno (JIRA)

EJB timer service should use a thread pool to avoid OOM ------------------------------------------------------- Key: EJBTHREE-1330 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1330 Project: EJB 3.0 Issue Type: Bug Components: pool Affects Versions: AS 4.2.2.GA Reporter: Galder Zamarreno Assigned To: Galder Zamarreno Priority: Minor The default EJB timer service used by the EJB3 layer is based on org.jboss.ejb3.timerservice.jboss.JBossTimerServiceFactory which delegates to the standard org.jboss.ejb.txtimer.EJBTimerService. For EJB3 beans using the EJB timer service the thread local pool should not be used. Since the current EJB timer service creates a new thread for each timer being created, the thread local pool will create a matching instance of the bean for that thread. Thus the number of active instances in total can effectively grow unchecked and thus an OOM will occur. -- 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

12 years, 11 months

5
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2166) no-interface view implementation based on MC constructs is brittle

by jaikiran pai (JIRA)

no-interface view implementation based on MC constructs is brittle ------------------------------------------------------------------ Key: EJBTHREE-2166 URL: https://jira.jboss.org/browse/EJBTHREE-2166 Project: EJB 3.0 Issue Type: Bug Components: nointerface Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai Currently the no-interface view proxy that gets bound into JNDI, internally uses a KernelControllerContext (MC construct) corresponding to the endpoint container of the EJB. The proxy depends just on DESCRIBED state of the endpoint. The invocation handler of that proxy, on first invocation, pushes the context to INSTALLED state (if not already in INSTALLED stated) and then invokes on the endpoint. This approach won't work out because MC returns an UnModifiable kernel controller context which throws an exception when we try to change the state of that context. More on this in the "Important" note at the end of this MC chapter http://docs.jboss.org/jbossmc/docs/2.0.x/userGuide/ch11s04.html: <quote> All context information is wrapped into unmodifiable objects to prevent the user from changing anything outside of the microcontainer's control. </quote> It's just plain luck that no-interface view works currently, because the first invocation on the nointerface view happens after the context has already been set to INSTALLED state by MC. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 11 months

3
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011