June 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBOOT-90) Add @ManagementProperty.readOnly annotations for all new properties of JBossASServerConfig

by Andrew Lee Rubinger (JIRA)

Add @ManagementProperty.readOnly annotations for all new properties of JBossASServerConfig ------------------------------------------------------------------------------------------ Key: JBBOOT-90 URL: https://jira.jboss.org/jira/browse/JBBOOT-90 Project: JBoss Bootstrap Issue Type: Feature Request Components: impl-as Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Will be available to be exposed/read by JON/consoles -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBID-82) Circle of trust servlet

by Anil Saldhana (JIRA)

Circle of trust servlet ----------------------- Key: JBID-82 URL: https://jira.jboss.org/jira/browse/JBID-82 Project: JBoss Identity Issue Type: Feature Request Components: Identity-Federation Affects Versions: 1.0.0.alpha2 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: 1.0.0.alpha3 Circle of Trust servlet that can be configured to pick up metadata from a set of URLs and update the common store. -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1844) Retry operations after an EJBTransactionRolledbackException

by Carlo de Wolf (JIRA)

Retry operations after an EJBTransactionRolledbackException ----------------------------------------------------------- Key: EJBTHREE-1844 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1844 Project: EJB 3.0 Issue Type: Feature Request Components: transactions Reporter: Carlo de Wolf Assignee: Carlo de Wolf By either annotating a bean or its methods, the applicable methods will retry the operation if an EJBTransactionRolledbackException occurs. @TransactionRetry(numRetries=4, waitTime=1, waitTimeUnit=TimeUnit.SECONDS) numRetries specifies how many times an operation will be tried. waitTime specified the amount of time to wait before retrying with the unit of time specified in waitTimeUnit. Default is 3 retries and 1000 milliseconds wait time after an EJBTransactionRolledbackException. -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1845) CancelAsyncTestCase is hanging

by Carlo de Wolf (JIRA)

CancelAsyncTestCase is hanging ------------------------------ Key: EJBTHREE-1845 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1845 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Priority: Critical Attachments: org.jboss.ejb3.async.impl.test.cancel.unit.CancelAsyncTaskTestCase-output.txt -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1638) Ordering Group messages delivery is not correctly handled after XA prepare()

by Howard Gao (JIRA)

Ordering Group messages delivery is not correctly handled after XA prepare() ----------------------------------------------------------------------------- Key: JBMESSAGING-1638 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1638 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.4.GA, 1.4.0.SP3.CP08 Reporter: Howard Gao Assignee: Howard Gao Fix For: 1.4.0.SP3.CP09, 1.4.5.GA In XA environment, if one ordering group message is received within a transaction but not committed, the next message can't be received. The problem is that after the transaction is prepared, the next message is delivered, thus broken the ordering. -- 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

17 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-6625) EJB 1.x or 2.x Stateless Session Bean metrics

by Scott M Stark (JIRA)

EJB 1.x or 2.x Stateless Session Bean metrics --------------------------------------------- Key: JBAS-6625 URL: https://jira.jboss.org/jira/browse/JBAS-6625 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB2, Management services Reporter: Scott M Stark Assignee: Alexey Loubyansky EJB 1.x or 2.x Stateless Session Bean metrics (in addition to availability)  <metric displayName="Create Calls" property="{stats.createCount.count}" displayType="summary" measurementType="trendsup"/> <metric displayName="Remove Calls" property="{stats.removeCount.count}" displayType="summary" measurementType="trendsup"/> <metric displayName="Method-Ready Beans" property="{stats.methodReadyCount.current}" displayType="summary"/> <metric displayName="Pool Size" property="{{jboss.j2ee:jndiName=%name%,plugin=pool,service=EJB}CurrentSize}"/> <metric displayName="Max Pool Size" property="{{jboss.j2ee:jndiName=%name%,plugin=pool,service=EJB}MaxSize}"/> -- 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

17 years, 1 month

4
12
0 / 0

[JBoss JIRA] Created: (JBAS-7000) issues when starting jboss server using Linux centos 5.3

by wallace njoroge (JIRA)

issues when starting jboss server using Linux centos 5.3 -------------------------------------------------------- Key: JBAS-7000 URL: https://jira.jboss.org/jira/browse/JBAS-7000 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX/Web Console Affects Versions: JBossAS-5.1.0.GA Reporter: wallace njoroge Assignee: Darran Lofthouse Environment: Centos 5.3 running in VM Linux 2.6.18-128.1.10.el5 #1 i686 i686 i386 GNU/Linux java version "1.6.0_13" Java(TM) SE Runtime Environment (build 1.6.0_13-b03) Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing) Steps. 1. $ pwd /usr/local/jboss/bin 2. run.sh pdadmin@PDPERFAppLnx01 bin]$ ./run.sh ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /usr/local/jboss JAVA: /home/centosadmin/jdk1.6.0_13/bin/java JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true CLASSPATH: /usr/local/jboss/bin/run.jar:/home/centosadmin/jdk1.6.0_13/lib/tools.jar ========================================================================= 15:14:42,090 INFO [ServerImpl] Starting JBoss (Microcontainer)... 15:14:42,091 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634) 15:14:42,092 INFO [ServerImpl] Bootstrap URL: null 15:14:42,092 INFO [ServerImpl] Home Dir: /usr/local/jboss 15:14:42,092 INFO [ServerImpl] Home URL: file:/usr/local/jboss/ 15:14:42,092 INFO [ServerImpl] Library URL: file:/usr/local/jboss/lib/ 15:14:42,093 INFO [ServerImpl] Patch URL: null 15:14:42,093 INFO [ServerImpl] Common Base URL: file:/usr/local/jboss/common/ 15:14:42,094 INFO [ServerImpl] Common Library URL: file:/usr/local/jboss/common/lib/ 15:14:42,094 INFO [ServerImpl] Server Name: default 15:14:42,094 INFO [ServerImpl] Server Base Dir: /usr/local/jboss/server 15:14:42,094 INFO [ServerImpl] Server Base URL: file:/usr/local/jboss/server/ 15:14:42,095 INFO [ServerImpl] Server Config URL: file:/usr/local/jboss/server/default/conf/ 15:14:42,095 INFO [ServerImpl] Server Home Dir: /usr/local/jboss/server/default 15:14:42,095 INFO [ServerImpl] Server Home URL: file:/usr/local/jboss/server/default/ 15:14:42,095 INFO [ServerImpl] Server Data Dir: /usr/local/jboss/server/default/data 15:14:42,096 INFO [ServerImpl] Server Library URL: file:/usr/local/jboss/server/default/lib/ 15:14:42,096 INFO [ServerImpl] Server Log Dir: /usr/local/jboss/server/default/log 15:14:42,096 INFO [ServerImpl] Server Native Dir: /usr/local/jboss/server/default/tmp/native 15:14:42,096 INFO [ServerImpl] Server Temp Dir: /usr/local/jboss/server/default/tmp 15:14:42,097 INFO [ServerImpl] Server Temp Deploy Dir: /usr/local/jboss/server/default/tmp/deploy 15:14:42,975 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/usr/local/jboss/server/default/conf/bootstrap.xml 15:14:43,586 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache] 15:14:43,589 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]] 15:14:43,940 INFO [CopyMechanism] VFS temp dir: /usr/local/jboss/server/default/tmp 15:14:43,941 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled. 15:14:45,822 INFO [ServerInfo] Java version: 1.6.0_13,Sun Microsystems Inc. 15:14:45,822 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_13-b03) 15:14:45,823 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 11.3-b02,Sun Microsystems Inc. 15:14:45,823 INFO [ServerInfo] OS-System: Linux 2.6.18-128.1.10.el5,i386 15:14:45,824 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Djava.endorsed.dirs=/usr/local/jboss/lib/endorsed 15:14:45,905 INFO [JMXKernel] Legacy JMX core initialized 15:14:49,308 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@487fb7[domain=default, server=default, name=default] 15:14:50,731 ERROR [AbstractKernelController] Error installing to Parse: name=vfsfile:/usr/local/jboss/server/default/conf/jboss-service.xml state=Not Installed mode=Manual requiredState=Parse org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/usr/local/jboss/server/default/conf/jboss-service.xml at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jbos Expected. Should work Error: Error creating managed object for vfsfile:/usr/local/jboss/server/default/conf/jboss-service.xml -- 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

17 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2111) In-Pattern RestrictionConnectiveDescrs (&& and ||) do not support bindings and restrictions at the same time

by Davide Sottara (JIRA)

In-Pattern RestrictionConnectiveDescrs (&& and ||) do not support bindings and restrictions at the same time ------------------------------------------------------------------------------------------------------------ Key: JBRULES-2111 URL: https://jira.jboss.org/jira/browse/JBRULES-2111 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.0.1.FINAL, 5.0.0.FINAL, 5.0.0.CR1, 5.0.0.M5, 5.0.0.M4, 5.0.0.M3, 5.0.0.M2, 5.0.0.M1 Environment: any Reporter: Davide Sottara Assignee: Mark Proctor Priority: Critical Fix For: FUTURE when trying to use connectives with restrictions and bindings, as in : Type( $f1: field1 op1 expr1 && $f2 : field2 op2 expr2) the fieldRestrictions are ignored by the parser and only the bindings are retained. Thus, reading the values of $f1 or $f2 returns the right value, but the restrictions (field op expr) are not generated -- 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

17 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBJCA-95) JCA/SJC

by Jesper Pedersen (JIRA)

JCA/SJC ------- Key: JBJCA-95 URL: https://jira.jboss.org/jira/browse/JBJCA-95 Project: JBoss JCA Issue Type: Task Components: Core Reporter: Jesper Pedersen Assignee: Jesper Pedersen Fix For: 1.0.0.Alpha1 A simple container. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-6011) Comments on Installation and Getting Started Guide

by Shelly McGowan (JIRA)

Comments on Installation and Getting Started Guide --------------------------------------------------- Key: JBAS-6011 URL: https://jira.jboss.org/jira/browse/JBAS-6011 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Affects Versions: JBossAS-5.0.0.CR2 Reporter: Shelly McGowan Assignee: Samson Kittoli Section 1.1 PreRequisites The wiki reference: Refer to http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossOperatingSystemSpecificIssues refers to issues with Linux 2.6 kernels and installation of JBoss AS 3.x on a MainFrame. This reference should be removed. Section 1.1.1 Hardware and Operating System Requirements This section refers to "supported" OS/JVM/DB combinations. There is no support offered for the community release. Section 1.1.2: Configuring your Java Environment Both JDK5 and JDK6 can be used with JBoss AS 5. Please add JDK 6 to this section. Chapter 2 - Installation Alternatives Binary Files Download ADD (extracted from release notes) JBossAS 5.0.0 can be compiled with both Java5 & Java6. The Java5 compiled binary is our primary/recommended binary distribution. It has undergone rigorous testing and can run under both a Java 5 and a Java 6 runtime. When running under Java 6 you need to manually copy the following libraries from the JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed directory, so that the JAX-WS 2.0 apis supported by JBossWS are used: * jbossws-native-saaj.jar * jbossws-native-jaxrpc.jar * jbossws-native-jaxws.jar * jbossws-native-jaxws-ext.jar The other option is to download the jdk6 distribution (jboss-5.0.0.CR2-jdk6.zip) in which case no configuration changes are required. Refer to the release notes for additional information about running with JDK 6. Correct the following: "Four types of server configurations will be included in your installation - minimal , default , and all . The Getting Started Guide explains in detail the different server configuration file sets." to refer to only Three server configurations. Instead of the reference to the Getting Started Guide (this guide), refer to the section that discusses this topic. Section 3.1 Download and Installation Replace references to jboss-4.2.2 to jboss-5.0.0 There are two binary distributions available: jboss-5.0.0.CR2.zip jboss-5.0.0.CR2-jdk6.zip Source File Download ANT and mvn are included with the JBoss distribution in <installdir>/tools/ so the downloading this section of ANT should be removed. 4.3 Building with Ant [from release notes: If you are building JBossAS from source you'll notice we are migrating to a maven2 build. At this point the build is a hybrid one because it declares all JBoss dependencies as maven2 artifacts, however after the dependencies are resolved/imported the legacy ant based build is used to compile and build the distribution. This will change to a full maven build at some point in time. The jboss maven repo can be found here. Starting from AS5 CR2, please note how the -sources.jar are also downloaded.] Revisit this section for GA for any build changes. Add note: When JBossAS 5 is compiled with Java 6, support for the extended JDBC 4 API is included in the binary, however this can only be used under a Java 6 runtime. Correct the following: The JBoss Application Server files are built under the build/jboss-5.0.0.<release> directory they are built under: build/output/jboss-5.0.0.<release> Chapter 7 - Check your Installation Correct the following: To test your installation, move to JBOSS_DIST/jboss-as/bin to move to JBOSS_DIST/jboss-5.0.0.<release>/bin Remove the NOTE that there is no "Server Started" message. That only pertains to the production config distributed with EAP. Update or remove the reference to refer to "Refer to the Getting Started Guide" to the section that discusses the server layout. -- 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

17 years, 1 month

3
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 June 2009