July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1174) Logging: follow logging conventions

by Bela Ban (JIRA)

Logging: follow logging conventions ----------------------------------- Key: JGRP-1174 URL: https://jira.jboss.org/jira/browse/JGRP-1174 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 3.0 https://docspace.corp.redhat.com/docs/DOC-30217 Requires code to be published, which can be copied over to JGroups (no JAR dep) -- 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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (AS7-1203) test for missing xa-datasource properties

by Stefano Maestri (JIRA)

test for missing xa-datasource properties ----------------------------------------- Key: AS7-1203 URL: https://issues.jboss.org/browse/AS7-1203 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Stefano Maestri Fix For: 7.1.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
6
0 / 0

[JBoss JIRA] Created: (JBAS-8222) Common approach to extension properties

by Brian Stansberry (JIRA)

Common approach to extension properties --------------------------------------- Key: JBAS-8222 URL: https://jira.jboss.org/browse/JBAS-8222 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Various elements in the domain models schema will include generic <properties> elements. David LLoyd described such an element as "the last ditch thing where we can add in stuff for support etc. without changing the schema." We need to document and clarify what the users can expect in terms of forward compatibility for content they include in such an element. And then ensure it's applied consistently across the various schema we'll be using. -- 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

14 years, 8 months

4
9
0 / 0

[JBoss JIRA] Created: (JGRP-1320) NAKACK: display the combined size of all messages in the retransmission tables

by Bela Ban (JIRA)

NAKACK: display the combined size of all messages in the retransmission tables ------------------------------------------------------------------------------ Key: JGRP-1320 URL: https://issues.jboss.org/browse/JGRP-1320 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Optional Fix For: 2.12.2, 3.1 - Add a JMX method to dump the size of all messages in all NakReceiverWindows - Add a JMX attribute to dump the combined sizes of *all* messages of all NakReceiverWindows The size could be payload only, or Message.size() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (AS7-1389) Log API dependencies should be included automatically in deployments

by David Lloyd (JIRA)

Log API dependencies should be included automatically in deployments -------------------------------------------------------------------- Key: AS7-1389 URL: https://issues.jboss.org/browse/AS7-1389 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.0.0.Final Reporter: David Lloyd Fix For: 7.0.1.Final The following log APIs should be included by deployments by default: * {{org.slf4j}} * {{org.apache.commons.logging}} * {{org.log4j}} These dependencies should override the deployment's versions of these libraries unless explicitly excluded by {{jboss-deployment-structure.xml}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
11
0 / 0

[JBoss JIRA] Created: (AS7-1306) PersistenceProviderResolver.getPersistenceProviders should return new instances of persistence provider

by Scott Marlow (JIRA)

PersistenceProviderResolver.getPersistenceProviders should return new instances of persistence provider ------------------------------------------------------------------------------------------------------- Key: AS7-1306 URL: https://issues.jboss.org/browse/AS7-1306 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.0.0.Final Reporter: Scott Marlow Assignee: Scott Marlow Fix For: 7.1.0.Alpha1 JPA specification section 9.3 states: {code} The results of calling the PersistenceProviderResolverHolder.getPersistencePro- viderResolver and the PersistenceProviderResolver.getPersistenceProvid- ers methods must not be cached. {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-1075) Support overloading of accumulate functions: Add int (or long) based sum's, int based avarage's, etc

by Geoffrey De Smet (JIRA)

Support overloading of accumulate functions: Add int (or long) based sum's, int based avarage's, etc ----------------------------------------------------------------------------------------------------- Key: JBRULES-1075 URL: http://jira.jboss.com/jira/browse/JBRULES-1075 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Drl Parser/Builder Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Edson Tirelli Priority: Minor Fix For: FUTURE TTP nl10 solver has about a 3% performance increase when switching from sumDouble to sumLong (and possibly a bit more when switching to sumInteger) There are 2 ways I see to implement this: 1) Force the user to explicitly declare he wants to use an integer based sum and add a sumInteger. This is not so user-friendly. This is what I 've done in the patch. 2) Support overloading of accumulate functions based on the function arguments. AFAIK drl is strongly typed (at least with the java dialect), so it should be theoretically possible for the drl parser to see sum($myInteger) and bind it to SumIntegerAccumulateFunction, while binding sum($myInteger.doubleValue()) to SumDoubleAccumulateFunction. And added advantage is that the drl compiler will also mark some bugs as compiler errors. For example sum($myString) -- 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

14 years, 8 months

4
5
0 / 0

[JBoss JIRA] Created: (JBVFS-175) NPE on shutdown

by David Lloyd (JIRA)

NPE on shutdown --------------- Key: JBVFS-175 URL: https://issues.jboss.org/browse/JBVFS-175 Project: JBoss VFS Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.1.GA Reporter: David Lloyd Assignee: John Bailey Fix For: 3.0.2.CR1, 3.1.0.CR1 See AS7-1288 for the sequence of events. The NPE is in DeleteTask in TempFileProvider. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBBOOT-56) Add tests that bootstraps are stutdown in reverse order from start

by Andrew Lee Rubinger (JIRA)

Add tests that bootstraps are stutdown in reverse order from start ------------------------------------------------------------------ Key: JBBOOT-56 URL: https://jira.jboss.org/jira/browse/JBBOOT-56 Project: JBoss Bootstrap Issue Type: Feature Request Components: impl-base Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Fix For: 0.1.2 Ensure that we are shutting down in proper sequence. -- 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

14 years, 8 months

4
12
0 / 0

[JBoss JIRA] Created: (AS7-1083) admin console for Datasource allows to edit JNDI of datasource

by Marek Novotny (JIRA)

admin console for Datasource allows to edit JNDI of datasource -------------------------------------------------------------- Key: AS7-1083 URL: https://issues.jboss.org/browse/AS7-1083 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: No Release Environment: Build #1250 (22.6.2011 2:51:44) Reporter: Marek Novotny admin console for Datasource allows to edit JNDI of datasource although then it complains the JNDI property is not writable. {code:title=Error stack trace} 14:25:02,023 WARN [org.jboss.as.controller] (HttpManagementService-threads - 8) Operation ("write-attribute") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "DefaultDS") ]): org.jboss.as.controller.OperationFailedException [ "Attribute jndi-name is not writeable" ] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$WriteAttributeHandler.execute(GlobalOperationHandlers.java:378) at org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352) at org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299) at org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224) at org.jboss.as.controller.NewCompositeOperationHandler.execute(NewCompositeOperationHandler.java:84) at org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352) at org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299) at org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224) at org.jboss.as.controller.NewModelControllerImpl$DefaultPrepareStepHandler.execute(NewModelControllerImpl.java:350) at org.jboss.as.controller.NewOperationContextImpl.executeStep(NewOperationContextImpl.java:352) at org.jboss.as.controller.NewOperationContextImpl.doCompleteStep(NewOperationContextImpl.java:299) at org.jboss.as.controller.NewOperationContextImpl.completeStep(NewOperationContextImpl.java:224) at org.jboss.as.controller.NewModelControllerImpl.execute(NewModelControllerImpl.java:119) at org.jboss.as.controller.NewModelControllerImpl$1.execute(NewModelControllerImpl.java:209) at org.jboss.as.controller.NewModelControllerImpl$1.execute(NewModelControllerImpl.java:199) at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:188) at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:123) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:80) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:85) at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:606) at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:82) at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:578) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] at org.jboss.threads.JBossThread.run(JBossThread.java:122) {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

7
7
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 July 2011