January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2205) NPE thrown in jboss-cli while defining already defined StringListType attribute

by Jan Tymel (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2205?page=com.atlassian.jira.plugi... ] Jan Tymel moved WFLY-7895 to WFCORE-2205: ----------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-2205 (was: WFLY-7895) Component/s: CLI (was: CLI) (was: Security) > NPE thrown in jboss-cli while defining already defined StringListType attribute > ------------------------------------------------------------------------------- > > Key: WFCORE-2205 > URL: https://issues.jboss.org/browse/WFCORE-2205 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jan Tymel > Assignee: Jason Greene > > NullPointerException is thrown when user tries to define already (i.e. previously in current command) defined StringListType attribute. This attempt results in following stack trace and termination of jboss-cli. > {code} > /subsystem=elytron/provider-loader=providerLoader:add(providers=[{class-names=[com.example.Class]},class-names=[{com.example.AnotherClass}Exception in thread "Aesh Process Loop 749282235" java.lang.NullPointerException > at org.jboss.as.cli.impl.DeploymentItemCompleter.getCandidates(DeploymentItemCompleter.java:80) > at org.jboss.as.cli.impl.DeploymentItemCompleter.complete(DeploymentItemCompleter.java:53) > at org.jboss.as.cli.impl.ValueTypeCompleter$ValueTypeCallbackHandler.getCandidatesFromMetadata(ValueTypeCompleter.java:433) > at org.jboss.as.cli.impl.ValueTypeCompleter$ValueTypeCallbackHandler.getSimpleValues(ValueTypeCompleter.java:690) > at org.jboss.as.cli.impl.ValueTypeCompleter$ValueTypeCallbackHandler.getCandidates(ValueTypeCompleter.java:573) > at org.jboss.as.cli.impl.ValueTypeCompleter.complete(ValueTypeCompleter.java:346) > at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:276) > at org.jboss.as.cli.operation.OperationRequestCompleter.complete(OperationRequestCompleter.java:89) > at org.jboss.as.cli.CommandCompleter.doComplete(CommandCompleter.java:137) > at org.jboss.as.cli.CommandCompleter.complete(CommandCompleter.java:64) > at org.jboss.as.cli.impl.Console$Factory$1$1.complete(Console.java:143) > at org.jboss.aesh.console.AeshCompletionHandler.complete(AeshCompletionHandler.java:155) > at org.jboss.aesh.console.AeshInputProcessor.complete(AeshInputProcessor.java:429) > at org.jboss.aesh.console.AeshInputProcessor.parseOperation(AeshInputProcessor.java:166) > at org.jboss.aesh.console.Console.processInternalOperation(Console.java:775) > at org.jboss.aesh.console.Console.execute(Console.java:735) > at org.jboss.aesh.console.Console.access$900(Console.java:73) > at org.jboss.aesh.console.Console$6.run(Console.java:644) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > {code} > Expected result: > No NPE thrown, jboss-cli is not terminated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7896) CME and NPE in Artemis integration seen in test run

by Miroslav Novak (JIRA)

[ https://issues.jboss.org/browse/WFLY-7896?page=com.atlassian.jira.plugin.... ] Miroslav Novak commented on WFLY-7896: -------------------------------------- This issue was reported with EAP 7.1.0.DR10. > CME and NPE in Artemis integration seen in test run > --------------------------------------------------- > > Key: WFLY-7896 > URL: https://issues.jboss.org/browse/WFLY-7896 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: David Lloyd > Assignee: Jeff Mesnil > > The exception of note was: > {noformat} > ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 64) MSC000001: Failed to start service jboss.messaging-activemq.default.jms.manager: org.jboss.msc.service.StartException in service jboss.messaging-activemq.default.jms.manager: WFLYMSGAMQ0033: Failed to start service > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:203) > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:63) > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:97) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > Caused by: java.util.ConcurrentModificationException > at java.util.Hashtable$Enumerator.next(Hashtable.java:1367) > at org.apache.activemq.artemis.core.config.impl.ConfigurationImpl.parseSystemProperties(ConfigurationImpl.java:308) > at org.apache.activemq.artemis.core.config.impl.ConfigurationImpl.parseSystemProperties(ConfigurationImpl.java:299) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:488) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:466) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:412) > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:199) > ... 8 more > {noformat} > The build was https://ci.wildfly.org/viewLog.html?buildTypeId=WildFlyProject_Elytron_Wi... which is a topic branch for Elytron integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2198) Create a picketbox feature pack

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2198?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2198: ---------------------------------------- Assignee: Brian Stansberry > Create a picketbox feature pack > ------------------------------- > > Key: WFCORE-2198 > URL: https://issues.jboss.org/browse/WFCORE-2198 > Project: WildFly Core > Issue Type: Task > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 3.0.0.Alpha20 > > > We should add a picketbox feature pack to WildFly Core, not included in the dist but built there. > Background: > We include PicketBox in the core pom and the vault functionality core provides requires it but we are not willing to include it in the core dist because it adds ~ 1MB to the dist size. > However, the way we are handling the picketbox module is not clean. The version of two of the jars that end up in the module are declared in the core pom.xml (as they are needed at compile time by core) but the 3rd is specified in full's pom.xml and the module.xml is in full. > We need an org.picketbox module in place to properly test core's vault handling in testsuite/rbac and testsuite/manualmode and there's no real good way to get it into the installations used by those testsuites > Option: > Just add the feature pack maven module as a child of the testsuite maven module, limiting the feature pack use to the testsuite, which is the primary driver of me filing this. That removes any implied requirement to maintain it beyond the needs of the testsuite or to include jars in the generated module beyond what the testsuite needs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7904) EJB 2.x session EJBs local home is configured with wrong interceptor

by David Lloyd (JIRA)

David Lloyd created WFLY-7904: --------------------------------- Summary: EJB 2.x session EJBs local home is configured with wrong interceptor Key: WFLY-7904 URL: https://issues.jboss.org/browse/WFLY-7904 Project: WildFly Issue Type: Bug Components: EJB Reporter: David Lloyd Assignee: David Lloyd In org.jboss.as.ejb3.deployment.processors.SessionBeanHomeProcessor, EJB local home views are getting configured with method handlers for methods that they don't have. The method getEJBMetaData pertains to remote homes only (and does not exist on EJBLocalHome) as the EJBMetaData class pertains only to remote views. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4415) RemotingContext should be copied for async EJB calls

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4415?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4415: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1201439|https://bugzilla.redhat.com/show_bug.cgi?id=1201439] from VERIFIED to CLOSED > RemotingContext should be copied for async EJB calls > ---------------------------------------------------- > > Key: WFLY-4415 > URL: https://issues.jboss.org/browse/WFLY-4415 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-590) SSL secured communication between master and slave in domain mode test case

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-590?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-590: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1197058|https://bugzilla.redhat.com/show_bug.cgi?id=1197058] from CLOSED to VERIFIED > SSL secured communication between master and slave in domain mode test case > --------------------------------------------------------------------------- > > Key: WFCORE-590 > URL: https://issues.jboss.org/browse/WFCORE-590 > Project: WildFly Core > Issue Type: Task > Components: Test Suite > Affects Versions: 1.0.0.Alpha19 > Reporter: Ondrej Kotek > Assignee: Ondrej Kotek > Fix For: 1.0.0.Beta4 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2183) ParallelBootOperationStepHandler context isn't rolling back overall operation if a subsystem fails in runtime

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2183?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2183: ---------------------------------------- Assignee: Brian Stansberry > ParallelBootOperationStepHandler context isn't rolling back overall operation if a subsystem fails in runtime > ------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-2183 > URL: https://issues.jboss.org/browse/WFCORE-2183 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > If an subsystem handler calls OperationContext.setRollbackOnly() during boot, only the ParallelBootOperationContext handling that subsystem is effected. The result is that subsystem rolls back but the boot itself is not aborted. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-835: --------------------------- Description: We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. (was: We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains so it does not need to be manually inflowed at a later point.) > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.1.0.Beta20 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-835) SecurityIdentity Automatic Outflow

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-835?page=com.atlassian.jira.plugin.sy... ] Jan Kalina reassigned ELY-835: ------------------------------ Assignee: Jan Kalina > SecurityIdentity Automatic Outflow > ---------------------------------- > > Key: ELY-835 > URL: https://issues.jboss.org/browse/ELY-835 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Jan Kalina > Priority: Blocker > Fix For: 1.1.0.Beta20 > > > We previously discussed that when runAs is called on a SecurityIdentity this should pro-actively outflow to predefined security domains (which it has in trusted-security-domains?) so it does not need to be manually inflowed at a later point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4303) Allow expressions in jboss-ejb-client.xml if configuration jboss-descriptor-property-replacement=true

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4303?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4303: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1194381|https://bugzilla.redhat.com/show_bug.cgi?id=1194381] from VERIFIED to CLOSED > Allow expressions in jboss-ejb-client.xml if configuration jboss-descriptor-property-replacement=true > ----------------------------------------------------------------------------------------------------- > > Key: WFLY-4303 > URL: https://issues.jboss.org/browse/WFLY-4303 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Tomasz Adamski > Fix For: 9.0.0.Beta1 > > > Applications need to have a jboss-ejb-client.xml configuration to use connections to other WildFly servers. > The remote-outbound-connection allow expressions, i.e. for user-name. > But if a cluster come into play the related <cluster> element inside the jboss-ejb-client.xml must have the same username and this can be only hardcoded. > So the jboss-ejb-client.xml parsing should allow expressions for > outbound-connection-ref, username, security-realm etc. > See https://github.com/wildfly/quickstart/blob/master/ejb-multi-server/app-ma... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 January 2017