October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2210) fix message endpoint isDeliveryTransacted

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2210?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2210: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > fix message endpoint isDeliveryTransacted > ----------------------------------------- > > Key: WFLY-2210 > URL: https://issues.jboss.org/browse/WFLY-2210 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Alpha4 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 8.0.0.CR1 > > > The org.jboss.as.ejb3.inflow.MessageEndpointService#isDeliveryTransacted method is checking the transaction attribute of the method using the MethodIntf.BEAN while it should use the MethodIntf.MESSAGE_ENDPOINT type. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2208) CLI over HTTP should switch to / be redirected to https automatically.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2208?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2208: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > CLI over HTTP should switch to / be redirected to https automatically. > ---------------------------------------------------------------------- > > Key: WFLY-2208 > URL: https://issues.jboss.org/browse/WFLY-2208 > Project: WildFly > Issue Type: Enhancement > Components: CLI, Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 8.0.0.CR1 > > > When using the native interface a TLS upgrade was already automatically in place once a keystore was added to the linked realm. > With the switch to http with an upgrade there is no automatic switch to https. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2215) WorkManagerService does not start work manager

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2215?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2215: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > WorkManagerService does not start work manager > ---------------------------------------------- > > Key: WFLY-2215 > URL: https://issues.jboss.org/browse/WFLY-2215 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: Bartosz Baranowski > Assignee: Stefano Maestri > Fix For: 8.0.0.CR1 > > > WorkManagerService does not start/restart WorkManager > https://github.com/wildfly/wildfly/blob/master/connector/src/main/java/or... > WorkManager is set in constructor. In stop method, WorkManager.shutdown() is called. start() should invoke WorkManager.cancelShutdown(). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2220) Unable to reload server after adding role and executing :reload

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2220?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2220: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Unable to reload server after adding role and executing :reload > --------------------------------------------------------------- > > Key: WFLY-2220 > URL: https://issues.jboss.org/browse/WFLY-2220 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 8.0.0.CR1 > > > Start a clean build of WildFly 8 and execute the following commands in the CLI: - > {code} > [standalone@localhost:9990 /connect > [standalone@localhost:9990 /] ./core-service=management/access=authorization/role-mapping=Operator:add > {"outcome" => "success"} > [standalone@localhost:9990 /] :reload > { > "outcome" => "success", > "result" => undefined > } > [standalone@localhost:9990 /] > {code} > Results in the following error and the server shuts down: - > {code} > 15:15:02,275 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 15:15:02,278 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("access" => "authorization"), > ("role-mapping" => "SuperUser") > ]): java.lang.UnsupportedOperationException > at java.util.Collections$UnmodifiableMap.put(Collections.java:1342) [rt.jar:1.7.0_17] > at org.jboss.as.controller.access.management.WritableAuthorizerConfiguration.addRoleMappingImmediate(WritableAuthorizerConfiguration.java:163) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.domain.management.access.RoleMappingAdd$1.execute(RoleMappingAdd.java:76) [wildfly-domain-management-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:609) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:487) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:321) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:290) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:252) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17] > 15:15:02,287 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report > JBAS014775: New missing/unsatisfied dependencies: > service jboss.remoting.endpoint.management (missing) dependents: [service jboss.remoting.management.channel.registry] > 15:15:02,290 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > 15:15:02,297 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Beta1-SNAPSHOT "WildFly" stopped in 2ms > {code} > What is interesting is that the server is manually startable to something has gone wrong regarding resetting the runtime state of RBAC at the time of the reload. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2219) Update to console 2.0.3.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2219?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2219: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Update to console 2.0.3.Final > ----------------------------- > > Key: WFLY-2219 > URL: https://issues.jboss.org/browse/WFLY-2219 > Project: WildFly > Issue Type: Task > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2216) include-all role mappings don't work in domain

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2216?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-2216: ------------------------------- Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > include-all role mappings don't work in domain > ---------------------------------------------- > > Key: WFLY-2216 > URL: https://issues.jboss.org/browse/WFLY-2216 > Project: WildFly > Issue Type: Sub-task > Components: Domain Management, Security > Reporter: Ladislav Thon > Assignee: Darran Lofthouse > Labels: rbac-filed-by-qa > Fix For: 8.0.0.CR1 > > > If I understand correctly, roles that have {{include-all=true}} in their role mappings should be added to all authenticated users. In my tests, though, this only works in standalone mode. > In domain mode, if I set a role mapping to {{include-all}}, this setting is not reflected (at least not immediately; maybe it would work after restart, but that's wrong anyway). It doesn't matter which role is set to be {{include-all}} -- in my tests, I use both standard roles and scoped roles and it consistently doesn't work. There's probably some wrong caching going on. > The failing test case is in my pull request https://github.com/wildfly/wildfly/pull/5166 (it's the _RBAC tests for include-all role mappings in domain_ commit). If it's more convenient, the pull request is the same as my _rbac_ branch (https://github.com/Ladicek/wildfly/commits/rbac). > Darran, I'm not sure if you are the right assignee -- please reassign if needed. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2183: -------------------------------- Attachment: add-custom-handler.png > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > Attachments: add-custom-handler.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-2183: ------------------------------------- [~heiko.braun] This is not an issue with the logging subsystem. While the attributes are not writable and should be locked during an update, they are required by the add operation. I'm attaching the screen shot of an add operation. AFAIK there is no requirement that all attributes be writable. > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: James Perkins > Fix For: 8.0.0.CR1 > > Attachments: add-custom-handler.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2183) Module and ClassName fields are disabled in new Custom handler dialog

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-2183?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-2183: -------------------------------- Assignee: Heiko Braun (was: James Perkins) > Module and ClassName fields are disabled in new Custom handler dialog > --------------------------------------------------------------------- > > Key: WFLY-2183 > URL: https://issues.jboss.org/browse/WFLY-2183 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Logging > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 8.0.0.CR1 > > Attachments: add-custom-handler.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2221) NPE in BinderService

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/WFLY-2221?page=com.atlassian.jira.plugin.... ] Jesper Pedersen commented on WFLY-2221: --------------------------------------- Should probably throw an IllegalStateException or add a guard for the possible NPE. > NPE in BinderService > -------------------- > > Key: WFLY-2221 > URL: https://issues.jboss.org/browse/WFLY-2221 > Project: WildFly > Issue Type: Bug > Components: Naming > Affects Versions: 8.0.0.Beta1 > Reporter: Jesper Pedersen > Assignee: Eduardo Martins > > {noformat} > 11:03:33,766 ERROR [org.jboss.msc.service] (MSC service thread 1-4) MSC000002: Invocation of listener "org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$BinderReleaseListener@2d6f9ce1" failed: java.lang.NullPointerException > at org.jboss.as.naming.service.BinderService.release(BinderService.java:100) [wildfly-naming-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$BinderReleaseListener.transition(ModuleJndiBindingProcessor.java:302) [wildfly-ee-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl.invokeListener(ServiceControllerImpl.java:1533) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:51) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at org.jboss.msc.service.ServiceControllerImpl$ListenerTask.run(ServiceControllerImpl.java:2095) [jboss-msc-1.2.0.Beta2.jar:1.2.0.Beta2] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > {noformat} > Master from 3 days ago -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 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 October 2013