June 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (REMJMX-110) Switch to depend on Java 8

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-110: --------------------------------------- Summary: Switch to depend on Java 8 Key: REMJMX-110 URL: https://issues.jboss.org/browse/REMJMX-110 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-108) Switch to Remoting 5

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-108: --------------------------------------- Summary: Switch to Remoting 5 Key: REMJMX-108 URL: https://issues.jboss.org/browse/REMJMX-108 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (REMJMX-109) Move from jboss-sasl to Elytron backed security

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-109: --------------------------------------- Summary: Move from jboss-sasl to Elytron backed security Key: REMJMX-109 URL: https://issues.jboss.org/browse/REMJMX-109 Project: Remoting JMX Issue Type: Task Components: Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1602) Elytron integration with JMX

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1602: ---------------------------------------- Summary: Elytron integration with JMX Key: WFCORE-1602 URL: https://issues.jboss.org/browse/WFCORE-1602 Project: WildFly Core Issue Type: Feature Request Components: JMX Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6737) Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6737?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-6737: ---------------------------------------- Please move this to WFCORE. > Server reload is needed for modified security-realm even if {allow-resource-service-restart=true} is used > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-6737 > URL: https://issues.jboss.org/browse/WFLY-6737 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > > When security-realm, which is set as http-interface security-realm in management-interfaces, is modified and operation used {allow-resource-service-restart=true} header then server is NOT in reload-required state but modified security realm does not work correctly until server is manually reloaded. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1523) RestartParentResourceRemoveHandler should fail when removing non-existing resources

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1523?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-1523: -------------------------------------- Assignee: Brian Stansberry (was: Bartosz Spyrko-Śmietanko) I'm reopening this as WFLY-6736 (which is reproducible against latest core master) shows that there are still issues here. Looks like SecurityRealmChildRemoveHandler needs a similar change as was done in the previous PRs for this. > RestartParentResourceRemoveHandler should fail when removing non-existing resources > ----------------------------------------------------------------------------------- > > Key: WFCORE-1523 > URL: https://issues.jboss.org/browse/WFCORE-1523 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 2.1.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > Priority: Minor > Labels: 2.2 > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > > In case when non-existent policy-module is removed through Management CLI, operation should finish with failure. However it finishes with outcome success and nothing is changed. It can be confusing since wrong command seems same as correct command. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-6736) Removing children of security-realm always finishes with {"outcome" => "success"}

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6736?page=com.atlassian.jira.plugin.... ] Brian Stansberry resolved WFLY-6736. ------------------------------------ Resolution: Duplicate Issue > Removing children of security-realm always finishes with {"outcome" => "success"} > --------------------------------------------------------------------------------- > > Key: WFLY-6736 > URL: https://issues.jboss.org/browse/WFLY-6736 > Project: WildFly > Issue Type: Bug > Components: Domain Management > Affects Versions: 10.0.0.Final > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > > Removing children of security-realm (e.g. authentication) always finishes with {"outcome" => "success"}. This happens even if type of children of security-realm does not exist in server configuration. It should rather finish with failure to indicate that nothing was removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1601) Processing stucks for ~12 seconds when ManagementRealm is changed with {allow-resource-service-restart=true}

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1601?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-6735 to WFCORE-1601: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1601 (was: WFLY-6735) Component/s: Domain Management (was: Domain Management) Affects Version/s: (was: 10.0.0.Final) > Processing stucks for ~12 seconds when ManagementRealm is changed with {allow-resource-service-restart=true} > ------------------------------------------------------------------------------------------------------------ > > Key: WFCORE-1601 > URL: https://issues.jboss.org/browse/WFCORE-1601 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Ondrej Lukas > Assignee: Brian Stansberry > > When any operation which changes configuration (add, remove, write-attribute...) is executed on any children of security-realm (e.g. authentication) with {allow-resource-service-restart=true} operation header, then processing stucks for ~12 seconds. > This happens only in case when changed security-realm is set as http-interface security-realm in management-interfaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-711) Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test

by Hendy Irawan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-711?page=com.atlassian.jira.plugin... ] Hendy Irawan edited comment on DROOLS-711 at 6/17/16 10:56 AM: --------------------------------------------------------------- I get this error with 6.4.0.Final, but I'm not sure if it's exactly the same cause. {noformat} Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'droolsConfig': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kieBase' defined in class path resource [org/lskk/lumen/reasoner/DroolsConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.kie.api.KieBase]: Circular reference involving containing bean 'droolsConfig' - consider declaring the factory method as static for independence from its containing instance. Factory method 'kieBase' threw exception; nested exception is java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rabbitmq.drl, line=25, column=0 text=Field Reader does not exist for declaration '$delayMillis' in '$delayMillis : delayMillis' in the rule 'Send SemanticMessage to RabbitMQ'], Message [id=2, level=ERROR, path=story.drl, line=22, column=0 text=Field Reader does not exist for declaration '$id' in '$id : id' in the rule 'get random story']] {noformat} story.drl : {noformat} dialect "mvel" import org.lskk.lumen.reasoner.* import org.lskk.lumen.reasoner.event.* import org.lskk.lumen.reasoner.expression.* import org.lskk.lumen.reasoner.intent.* import org.lskk.lumen.reasoner.story.* global org.slf4j.Logger log global StoryRepository storyRepo declare TellStory @role( event ) end declare PropositionTold @role( event ) end rule "get random story" when $intent : TellStory(story == null, $id : id) then log.info("Setting story for intent {}", $intent); modify($intent) { setStoryId("soon_see"), setStory(storyRepo.findOne("soon_see")) } end rule "tell initial proposition" when $tellStory : TellStory(story != null) not( PropositionTold(tellStory == $tellStory) ) then log.info("Telling initial proposition for {}", $tellStory); PropositionTold $propositionTold = new PropositionTold($tellStory, 0); insert($propositionTold); boolean done = $propositionTold.index >= $tellStory.story.propositions.size - 1; if (done) { log.info("Done telling {} propositions for {}", $tellStory.story.propositions.size, $tellStory); } modify($tellStory) { setLastPropositionIndex($propositionTold.index), setDone(done) } end rule "tell next proposition until done" when $lastProposition : PropositionTold($tellStory : tellStory, $lastIndex : index, tellStory.done == false) not( PropositionTold(tellStory == $tellStory, index == $lastIndex + 1, this after[0s,10s] $lastProposition) ) then log.debug("Telling proposition {} for {}", $lastIndex + 1, $tellStory); PropositionTold $propositionTold = new PropositionTold($tellStory, $lastIndex + 1); insert($propositionTold); boolean done = $propositionTold.index >= $tellStory.story.propositions.size - 1; if (done) { log.info("Done telling {} propositions for {}", $tellStory.story.propositions.size, $tellStory); } modify($tellStory) { setLastPropositionIndex($propositionTold.index), setDone(done) } end rule "communicate proposition" when $proposition : PropositionTold($tellStory : tellStory, $index : index) then log.debug("Expressing proposition {} for {}", $index, $tellStory); $tellStory.channel.express($tellStory.avatarId, $tellStory.story.propositions[$index], true, null); end {noformat} was (Author: ceefour): I get this error with 6.4.0.Final, but I'm not sure if it's exactly the same cause. {noformat} Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'droolsConfig': Invocation of init method failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kieBase' defined in class path resource [org/lskk/lumen/reasoner/DroolsConfig.class]: Bean instantiation via factory method failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.kie.api.KieBase]: Circular reference involving containing bean 'droolsConfig' - consider declaring the factory method as static for independence from its containing instance. Factory method 'kieBase' threw exception; nested exception is java.lang.RuntimeException: Error while creating KieBase[Message [id=1, level=ERROR, path=rabbitmq.drl, line=25, column=0 text=Field Reader does not exist for declaration '$delayMillis' in '$delayMillis : delayMillis' in the rule 'Send SemanticMessage to RabbitMQ'], Message [id=2, level=ERROR, path=story.drl, line=22, column=0 text=Field Reader does not exist for declaration '$id' in '$id : id' in the rule 'get random story']] {noformat} > Kie Server unable to build KieBase which builds fine with kie-maven-plugin and unit test > ---------------------------------------------------------------------------------------- > > Key: DROOLS-711 > URL: https://issues.jboss.org/browse/DROOLS-711 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR4, 6.2.0.Final > Environment: kie-server on WildFly 8.2.0.Final running with JDK 8 > Reporter: Matteo Mortari > Assignee: Mario Fusco > Attachments: 20150213.DROOLS-711.zip > > > I have deployed Kie Server kie-server-distribution-wars-6.2.0.CR4-ee7.war on WildFly 8.2.0.Final. > I have a simple rule base in the project {{client-test-rules}} as per below, in a kie project structured as kie-drools-archetype, which passes all test and install in m2 repo with {{mvn clean install}}. > {code:java} > package com.acme.client_test_rules; > declare Measurement > @role(event) > end > rule "keep latest Measurement ID" > salience 1000 > no-loop > when > $old : Measurement( $id : id ) > $new : Measurement( id == $id , this after $old ) > then > System.out.println("keep latest old : "+$old+" new (kept): "+$new); > retract($old); > end > {code} > Then I issue Kie Server commands, using the client library, using project {{client-test}} to instantiate a container for the same artifact, but in the wildfly logs I get the following error below - which doesn't happen for kie-maven-plugin nor during unit test. Please note I'm assuming user {{kieserver}} with password {{kieserver}} is a valid user for the Kie Server Realm, or configure wildfly or the code in the project {{client-test}} accordingly to your environment =). > {code} > 09:41:41,700 ERROR [org.drools.compiler.kie.builder.impl.AbstractKieModule] (default task-4) Unable to build KieBaseModel:kbase1 > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Unable to create Field Extractor for 'id'Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > : [Rule name='keep latest Measurement ID'] > java.lang.RuntimeException: Field/method 'id' not found for class 'com.acme.client_test_rules.Measurement' > Field Reader does not exist for declaration '$id' in 'predicate 'id == $id'' in the rule 'keep latest Measurement ID' : [Rule name='keep latest Measurement ID'] > Unable to Analyse Expression id == $id: > [Error: unable to resolve method using strict-mode: com.acme.client_test_rules.Measurement.id()] > [Near : {... id == $id ....}] > ^ > [Line: 12, Column: 4] : [Rule name='keep latest Measurement ID'] > {code} > Can you kindly verify if some bug is hiding behind this odd behavior, please? > Thank you > MM -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-1600) Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-1600: ---------------------------------------- Summary: Update the legacy security realms to add factory methods to obtain SaslAuthenticationFactory and HttpAuthenticationFactory instances. Key: WFCORE-1600 URL: https://issues.jboss.org/browse/WFCORE-1600 Project: WildFly Core Issue Type: Enhancement Components: Domain Management, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha2 These are for use when security realms are directly referenced, although Elytron types these should not be advertised as capabilities as these are for specific backwards compatibility requirements and not to increase their use as Elytron capabilities. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 June 2016