July 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-198) Allow the association of Provider[] with a security domain and add support for mechanism loading.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-198?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-198. ---------------------------------- Resolution: Out of Date We now have the SecurityDomainSaslServerFactoryConfiguration to pair up the mechs with a domain and allow provider based lookups. > Allow the association of Provider[] with a security domain and add support for mechanism loading. > ------------------------------------------------------------------------------------------------- > > Key: ELY-198 > URL: https://issues.jboss.org/browse/ELY-198 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha3 > > > Where no Provider[] is made available to a SecurityDomain the domain will use Security.getProviders() instead. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4998) Domain deployment batch subsystem resources throw an NPE when an attempting to read the resource

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4998?page=com.atlassian.jira.plugin.... ] James Perkins closed WFLY-4998. ------------------------------- Resolution: Cannot Reproduce Bug I probably should have tested before I filed this bug. > Domain deployment batch subsystem resources throw an NPE when an attempting to read the resource > ------------------------------------------------------------------------------------------------ > > Key: WFLY-4998 > URL: https://issues.jboss.org/browse/WFLY-4998 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > Jobs should likely not be allowed to be read from this address, but an NPE should not be thrown. > {code} > 2015-07-23 10:54:23,469 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool – 154) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("deployment" => "alploy-loyaltybe.ear"), > ("subdeployment" => "loyalty-bundle.jar"), > ("subsystem" => "batch"), > ("job" => "RESOURCE_BUNDLE_JOB") > ]): java.lang.NullPointerException > at org.wildfly.extension.batch.deployment.JobOperationStepHandler.execute(JobOperationStepHandler.java:45) > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174) [wildfly-controller-1.0.0.Final.jar:1.0.0.Final] > at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137) [wildfly-controller-1.0.0.Final.jar:1.0.0.Final] > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4918) Remove default-stack usage and make stack required/explicit per channel

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4918: --------------------------------- Priority: Major (was: Minor) > Remove default-stack usage and make stack required/explicit per channel > ----------------------------------------------------------------------- > > Key: WFLY-4918 > URL: https://issues.jboss.org/browse/WFLY-4918 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 10.0.0.Beta1 > > > We discussed with Paul earlier today to go the way of making this explicit per channel, since currently there is a info when booting the default ha profiles: > 18:06:44,039 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4937) Implement graceful shutdown for transactions

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-4937?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-4937: ------------------------------------- Sorry, I was unclear. I wasn't proposing to pause the individual transactions. What I meant was: 1. When suspend is called 2. Allow existing remote transactions to complete 3. Do not allow new remote transactions to be created 4. Until resume is called (or server restarts) Is that the intended behavior? I think it would be consistent with what you are proposing (so long as doOtherStuff is @RequiresNew - if it was @Requires as the TX is already existing we wouldn't actually reject those ones as the lookup of the transaction would succeed) > Implement graceful shutdown for transactions > -------------------------------------------- > > Key: WFLY-4937 > URL: https://issues.jboss.org/browse/WFLY-4937 > Project: WildFly > Issue Type: Feature Request > Components: Transactions > Affects Versions: 10.0.0.Alpha5 > Reporter: Michael Musgrove > Assignee: Michael Musgrove > Fix For: 11.0.0.Alpha1 > > > We will handle suspend for JTA and JTS by disallowing new transactions and then block the suspend thread until the count of active transactions drops to zero. We will also suspend the recovery manager. > We will *not* do graceful shutdown for the optional XTS subsystem. For example an incoming XTS request for an existing transaction will be blocked. > Question: should we > - raise a new JIRA for this XTS case; > - document the deficiency and see if there are complaints; > - document the deficiency and fix it in a subsequent release -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4918) Remove default-stack usage and make stack required/explicit per channel

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4918: --------------------------------- Summary: Remove default-stack usage and make stack required/explicit per channel (was: Remove default-stack usage and make stack required per channel) > Remove default-stack usage and make stack required/explicit per channel > ----------------------------------------------------------------------- > > Key: WFLY-4918 > URL: https://issues.jboss.org/browse/WFLY-4918 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.Beta1 > > > We discussed with Paul earlier today to go the way of making this explicit per channel, since currently there is a info when booting the default ha profiles: > 18:06:44,039 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4918) Remove default-stack usage and make stack required/explicit per channel

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4918: --------------------------------- Summary: Remove default-stack usage and make stack required/explicit per channel (was: Remove default-stack and make stack required/explicit per channel) > Remove default-stack usage and make stack required/explicit per channel > ----------------------------------------------------------------------- > > Key: WFLY-4918 > URL: https://issues.jboss.org/browse/WFLY-4918 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.Beta1 > > > We discussed with Paul earlier today to go the way of making this explicit per channel, since currently there is a info when booting the default ha profiles: > 18:06:44,039 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4918) Remove default-stack usage and make stack required per channel

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4918?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-4918: --------------------------------- Summary: Remove default-stack usage and make stack required per channel (was: Remove default-stack usage and make stack required/explicit per channel) > Remove default-stack usage and make stack required per channel > -------------------------------------------------------------- > > Key: WFLY-4918 > URL: https://issues.jboss.org/browse/WFLY-4918 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha5 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > Fix For: 10.0.0.Beta1 > > > We discussed with Paul earlier today to go the way of making this explicit per channel, since currently there is a info when booting the default ha profiles: > 18:06:44,039 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'default-stack' in the resource at address '/subsystem=jgroups' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4628) Add ability to restart and stop batch jobs

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4628?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4628: -------------------------------- Fix Version/s: 10.0.0.Beta1 > Add ability to restart and stop batch jobs > ------------------------------------------ > > Key: WFLY-4628 > URL: https://issues.jboss.org/browse/WFLY-4628 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > Fix For: 10.0.0.Beta1 > > > Currently there is only a way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to restart and stop running jobs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4628) Add ability to restart and stop batch jobs

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-4628?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-4628: -------------------------------- Priority: Blocker (was: Major) > Add ability to restart and stop batch jobs > ------------------------------------------ > > Key: WFLY-4628 > URL: https://issues.jboss.org/browse/WFLY-4628 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > Priority: Blocker > Fix For: 10.0.0.Beta1 > > > Currently there is only a way to view batch jobs for a deployment with in the batch subsystem management. There should be a way to restart and stop running jobs as well. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-855) Intermittent Disconnection from CLI After Reload in domain mode

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-855?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-855: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1249031 > Intermittent Disconnection from CLI After Reload in domain mode > --------------------------------------------------------------- > > Key: WFCORE-855 > URL: https://issues.jboss.org/browse/WFCORE-855 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 2.0.0.Alpha12 > Reporter: Joe Wertz > Assignee: Joe Wertz > Fix For: 2.0.0.Alpha12 > > Original Estimate: 3 minutes > Remaining Estimate: 3 minutes > > Description of problem: > CLI scripts for management of managed domain > Version-Release number of selected component (if applicable): > 6.4.3.CP.CR1 > How reproducible: > Always > Steps to Reproduce: > Use CLI script: > :read-attribute(name=process-type) > reload --host=master > :read-attribute(name=process-type) > or commands option for script > Actual results: > 6.4.3 > ./jboss-cli.sh -c commands=':read-attribute(name=process-type), reload --host=master, :read-attribute(name=process-type)' > { > "outcome" => "success", > "result" => "Domain Controller" > } > Failed to establish connection in 6025ms > Expected results: > 6.3.3 > ./jboss-cli.sh -c commands=':read-attribute(name=process-type), reload --host=master, :read-attribute(name=process-type)' > { > "outcome" => "success", > "result" => "Domain Controller" > } > { > "outcome" => "success", > "result" => "Domain Controller" > } > Additional info: > - Follow up to https://bugzilla.redhat.com/show_bug.cgi?id=1232933 > - using --timeout doesn't workaround the problem -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 July 2015