August 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SASL-36) Release 1.0.2.Final

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-36: ------------------------------------ Summary: Release 1.0.2.Final Key: SASL-36 URL: https://issues.jboss.org/browse/SASL-36 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.2.CR1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (SASL-35) Clean up of temporary files created during authentication process for local mechanism.

by Darran Lofthouse (JIRA)

Darran Lofthouse created SASL-35: ------------------------------------ Summary: Clean up of temporary files created during authentication process for local mechanism. Key: SASL-35 URL: https://issues.jboss.org/browse/SASL-35 Project: JBoss SASL Provider Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.0.1.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.0.2.CR1 The local mechanism creates a temporary file as part of the verification process, if this is not used then the file is left to be deleted only when the JVM terminates. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-5325) Can't set attribute "suffix" on web access-log

by Ed Roberts (JIRA)

Ed Roberts created AS7-5325: ------------------------------- Summary: Can't set attribute "suffix" on web access-log Key: AS7-5325 URL: https://issues.jboss.org/browse/AS7-5325 Project: Application Server 7 Issue Type: Enhancement Components: Web Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final Environment: N/A Reporter: Ed Roberts Assignee: Remy Maucherat In JBoss 5.x you used to be able to specify a suffix attribute value for the JBossWeb access log file, which would be appended to generated log file names. In JBoss 7.x you can only specify a prefix. For the logging handlers you can specify both a prefix and a suffix, which is inconsistent. Please add the suffix attribute to the access-log element within the parent virtual-server element of the web subsystem xml configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5310) javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored

by Michael Locher (JIRA)

Michael Locher created AS7-5310: ----------------------------------- Summary: javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL not honored Key: AS7-5310 URL: https://issues.jboss.org/browse/AS7-5310 Project: Application Server 7 Issue Type: Bug Components: JSF Affects Versions: 7.1.2.Final (EAP) Reporter: Michael Locher Assignee: Stan Silvert The javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL params seems not to be working on EAP 6: <context-param> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] (AS7-5324) Attribute "allow-multiple-users" not handled for xml datasources

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5324: ------------------------------------- Summary: Attribute "allow-multiple-users" not handled for xml datasources Key: AS7-5324 URL: https://issues.jboss.org/browse/AS7-5324 Project: Application Server 7 Issue Type: Feature Request Components: JCA Affects Versions: 7.1.2.Final (EAP) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 XMLDataSourceRuntimeHandler and XMLXaDataSourceRuntimeHandler don't handle attribute "allow-multiple-users". So if you do a read-attribute for that attribute or do a :read-resource(include-runtime=true) the op fails with an ISE. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5291) JBOSS7 server calls getPrimaryKey() on Home interface business method on second call in same transaction

by Mayank Gupta (JIRA)

Mayank Gupta created AS7-5291: --------------------------------- Summary: JBOSS7 server calls getPrimaryKey() on Home interface business method on second call in same transaction Key: AS7-5291 URL: https://issues.jboss.org/browse/AS7-5291 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Reporter: Mayank Gupta Assignee: jaikiran pai If any ejbHome business method is called more then once in same EJB transaction JBOSS7.1.1 server calls getPrimaryKey() on entity home interface. Following exception is thrown by JBOSS server. (java.lang.String): javax.ejb.EJBTransactionRolledbackException: JBAS014527: Cannot call getPrimaryKey() when state is entity bean home method at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:139) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:204) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:306) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
11
0 / 0

[JBoss JIRA] (AS7-3146) HibernatePersistenceProviderAdaptor's putPropertyIfAbsent should check the pu.getProperties() instead of the empty HashMap

by Philippe Guinot (Created) (JIRA)

HibernatePersistenceProviderAdaptor's putPropertyIfAbsent should check the pu.getProperties() instead of the empty HashMap -------------------------------------------------------------------------------------------------------------------------- Key: AS7-3146 URL: https://issues.jboss.org/browse/AS7-3146 Project: Application Server 7 Issue Type: Bug Components: JPA / Hibernate Affects Versions: 7.1.0.CR1b Reporter: Philippe Guinot Assignee: Scott Marlow In org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor and org.jboss.as.jpa.hibernate4.HibernatePersistenceProviderAdaptor putPropertyIfAbsent should check the pu.getProperties() instead of the empty HashMap. If not, AS7-2460 does not work as the override does not take in account what is present in persistence.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] (AS7-5322) CLONE - Logging subsystem should not allow assigning an async-handler as a subhandler to itself

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/AS7-5322?page=com.atlassian.jira.plugin.s... ] James Perkins moved JBPAPP-9663 to AS7-5322: -------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5322 (was: JBPAPP-9663) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: (was: EAP 6.0.0 (CR1)) Security: (was: Public) Fix Version/s: (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Logging subsystem should not allow assigning an async-handler as a subhandler to itself > ----------------------------------------------------------------------------------------------- > > Key: AS7-5322 > URL: https://issues.jboss.org/browse/AS7-5322 > Project: Application Server 7 > Issue Type: Bug > Reporter: Jan Martiska > Assignee: James Perkins > > {noformat} > [standalone@localhost:9999 /] /subsystem=logging/async-handler=a/:add(queue-length=10) > {"outcome" => "success"} > [standalone@localhost:9999 /] /subsystem=logging/async-handler=a/:assign-subhandler(name=a) > {"outcome" => "success"} > {noformat} > The second command should fail. Assigning an async handler to itself leads to a circular dependency, which leads to a fatal error at server boot: > {noformat} > 15:00:28,118 ERROR [org.jboss.as.controller.management-operation] JBAS014612: Operation ("add") failed - address: ([ > ("subsystem" => "logging"), > ("async-handler" => "a") > ]): org.jboss.msc.service.CircularDependencyException: Service jboss-as has a circular dependency > at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:617) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:588) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:562) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2228) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1] > at org.jboss.as.controller.OperationContextImpl$ContextServiceBuilder.install(OperationContextImpl.java:955) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.logging.handlers.HandlerAddProperties.performRuntime(HandlerAddProperties.java:124) > at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:50) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ParallelBootOperationStepHandler.execute(ParallelBootOperationStepHandler.java:161) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:175) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:191) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at org.jboss.as.server.ServerService.boot(ServerService.java:295) > at org.jboss.as.server.ServerService.boot(ServerService.java:270) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32] > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3359) Planning entity locking: A planning variable can be immutable for Planner based on a boolean method on the entity

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3359: ----------------------------------------- Summary: Planning entity locking: A planning variable can be immutable for Planner based on a boolean method on the entity Key: JBRULES-3359 URL: https://issues.jboss.org/browse/JBRULES-3359 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet For use case of "windowed planning", see manual section "repeated planning". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] (JBRULES-3601) Planning variable immovability (not just per entity): A planning variable can be immovable for Planner based on a SelectionFilter while another variable in the same entity is movable

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3601: ----------------------------------------- Summary: Planning variable immovability (not just per entity): A planning variable can be immovable for Planner based on a SelectionFilter while another variable in the same entity is movable Key: JBRULES-3601 URL: https://issues.jboss.org/browse/JBRULES-3601 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
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 August 2012