[JBoss JIRA] (DROOLS-1694) Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
by Mario Fusco (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1694?page=com.atlassian.jira.plugi... ]
Mario Fusco updated DROOLS-1694:
--------------------------------
Sprint: 2017 Week 32-33
> Inherited kbases, across multiple modules, fails to build via the kie-maven-plugin
> ----------------------------------------------------------------------------------
>
> Key: DROOLS-1694
> URL: https://issues.jboss.org/browse/DROOLS-1694
> Project: Drools
> Issue Type: Bug
> Components: decision tables
> Affects Versions: 6.3.0.Final
> Reporter: Alistair Black
> Assignee: Massimiliano Dessi
>
> I am working on a multi-module BRMS project, with each module encapsulating a set of rules forming a single knowledge base. There is a "packaging" module which inherits each of these modules in order to generate a KJAR for deployment purposes. The application then utilises this KJAR via the KieScanner/ReleaseId approach to facilitate dynamic rule loading at runtime and decoupling of application/rules.
> Having taken the above approach I have encountered an issue where the master build fails when building the "packaging" module as part of the main project build. If the module is built on it's own, then it completes without error.
> The error reported is:
> {{[ERROR] Failed to execute goal org.kie:kie-maven-plugin:6.3.0.Final:build (default-build) on project rules: Execution default-build of goal org.kie:kie-maven-plugin:6.3.0.Final:build failed: Illegal class for global. Expected [org.drools.template.parser.DefaultGenerator], found [org.drools.template.parser.DefaultGenerator]. -> [Help 1]}}
> Having liased with Maciej Swiderski he has asked me to report it as a bug.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9226) Elytron dir-context referral mode THROW results to LdapReferralException for MS Active Directory
by Jiri Ondrusek (JIRA)
[ https://issues.jboss.org/browse/WFLY-9226?page=com.atlassian.jira.plugin.... ]
Jiri Ondrusek moved JBEAP-12732 to WFLY-9226:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9226 (was: JBEAP-12732)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Security
(was: Security)
Affects Version/s: 11.0.0.CR1
(was: 7.1.0.DR19)
> Elytron dir-context referral mode THROW results to LdapReferralException for MS Active Directory
> ------------------------------------------------------------------------------------------------
>
> Key: WFLY-9226
> URL: https://issues.jboss.org/browse/WFLY-9226
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Affects Versions: 11.0.0.CR1
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Labels: eap72
>
> When Elytron dir-context is configured to use referral mode THROW and MS Active Directory is used and ldap-realm attributes {{identity-mapping.search-base-dn}} or {{identity-mapping.attribute-mapping.filter-base-dn}} is configured to referral domain (i.e. domain which is referred through crossRef of LDAP server configured in related {{dir-context}}) then LdapReferralException is thrown and authentication is failed.
> In correct behavior ldap-realm with THROW referral mode should be able to authenticate user from referral correctly.
> Thrown Exception:
> {code}
> BASIC: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:176)
> at org.wildfly.security.http.util.SetMechanismInformationMechanismFactory$1.evaluateRequest(SetMechanismInformationMechanismFactory.java:114)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:77)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:115)
> at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$100(HttpAuthenticator.java:94)
> at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:78)
> at org.wildfly.elytron.web.undertow.server.SecurityContextImpl.authenticate(SecurityContextImpl.java:100)
> at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:55)
> at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:53)
> at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
> at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
> at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:59)
> at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
> at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
> at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
> at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1704)
> at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
> at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
> at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:211)
> at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:809)
> 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)
> Caused by: org.wildfly.security.http.HttpAuthenticationException: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.http.impl.UsernamePasswordAuthenticationMechanism.authenticate(UsernamePasswordAuthenticationMechanism.java:79)
> at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:152)
> ... 37 more
> Caused by: org.wildfly.security.auth.server.RealmUnavailableException: ELY01108: Ldap-backed realm identity search failed
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.search(LdapSecurityRealm.java:1138)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.getIdentity(LdapSecurityRealm.java:689)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapRealmIdentity.verifyEvidence(LdapSecurityRealm.java:601)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$NameAssignedState.verifyEvidence(ServerAuthenticationContext.java:1859)
> at org.wildfly.security.auth.server.ServerAuthenticationContext.verifyEvidence(ServerAuthenticationContext.java:665)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:877)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:787)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:928)
> at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:735)
> at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$SecurityIdentityCallbackHandler.handle(SecurityIdentityServerMechanismFactory.java:113)
> at org.wildfly.security.http.impl.UsernamePasswordAuthenticationMechanism.authenticate(UsernamePasswordAuthenticationMechanism.java:73)
> ... 38 more
> Caused by: com.sun.jndi.ldap.LdapReferralException: [LDAP: error code 10 - 0000202B: RefErr: DSID-03100781, data 0, 1 access points
> ref 1: 'eap-vm002.mw.lab.eng.bos.redhat.com'
> \00]; remaining name 'ou=SimpleADReferralTestCasea4e11461,OU=secondary,O=eapqe,DC=JBOSS3,DC=test2'
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2975)
> at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2888)
> at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1846)
> at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1769)
> at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1786)
> at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:418)
> at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:396)
> at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:297)
> at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:297)
> at org.wildfly.security.auth.realm.ldap.DelegatingLdapContext.search(DelegatingLdapContext.java:330)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.searchWithPagination(LdapSecurityRealm.java:1158)
> at org.wildfly.security.auth.realm.ldap.LdapSecurityRealm$LdapSearch.search(LdapSecurityRealm.java:1052)
> ... 48 more
> {code}
> Similar issue for referral mode THROW is also included in older version of application server, see JBEAP-3027 and JBEAP-3029.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (DROOLS-1577) Support FIFO queue for agenda group focus
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1577?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-1577:
---------------------------------------
[~rmorrise] ruleflows are orchestrated by BPMN processes with "Rule Task" nodes. Basically design the process with the flow you want where each step in the flow is a "Rule Task" node. In the Rule Task node, select which ruleflow-group should be invoked.
The command to activate a ruleflow-group is "StartProcess" with the ID of the process. In other words, a ruleflow is simply a process where all nodes are Rule Task nodes or gateways.
> Support FIFO queue for agenda group focus
> -----------------------------------------
>
> Key: DROOLS-1577
> URL: https://issues.jboss.org/browse/DROOLS-1577
> Project: Drools
> Issue Type: Feature Request
> Affects Versions: 6.5.0.Final
> Reporter: Russell Morrisey
> Assignee: Mario Fusco
>
> When setting up the ordering of agenda groups, the framework should support adding them in the order they are supposed to be executed.
> Ex:
> agenda.getAgendaGroup( "calculation" ).setQueue();
> agenda.getAgendaGroup( "report" ).setQueue();
> Or, even better:
> agenda.addAgendaGroupsToQueue("calculation", "report");
> And:
> agenda.addAgendaGroupsToQueue(agenda.getAgendaGroup( "calculation" ), agenda.getAgendaGroup( "report" ))
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (LOGMGR-170) TCP reconnect thread does not properly handle interrupts
by James Perkins (JIRA)
James Perkins created LOGMGR-170:
------------------------------------
Summary: TCP reconnect thread does not properly handle interrupts
Key: LOGMGR-170
URL: https://issues.jboss.org/browse/LOGMGR-170
Project: JBoss Log Manager
Issue Type: Bug
Reporter: James Perkins
Assignee: James Perkins
The {{TcpOutputStream}} reconnect thread may not always handle interrupts correctly. In most cases this should not be an issue. However this should at least be examined to ensure a rogue thread won't be left running.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9224) FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9224?page=com.atlassian.jira.plugin.... ]
Brian Stansberry resolved WFLY-9224.
------------------------------------
Fix Version/s: 11.0.0.Alpha1
Assignee: Chao Wang (was: Jason Greene)
Resolution: Done
This is no longer a problem in 11.0.0.Alpha1. I believe the fix for WFCORE-1686 took care of it.
> FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
> -------------------------------------------------------------------------
>
> Key: WFLY-9224
> URL: https://issues.jboss.org/browse/WFLY-9224
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: shashi avirineni
> Assignee: Chao Wang
> Priority: Minor
> Fix For: 11.0.0.Alpha1
>
>
> getting FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1 when i check for wildfly version.
> ./standalone.sh -v
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /u01/app/wildfly/wildfly-10.1.0.Final
> JAVA: /u01/app/jdk1.8.0_65/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 12:54:18,655 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
> 12:54:18,897 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9224) FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-9224?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-9224:
-----------------------------------
Issue Type: Bug (was: Task)
> FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
> -------------------------------------------------------------------------
>
> Key: WFLY-9224
> URL: https://issues.jboss.org/browse/WFLY-9224
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: shashi avirineni
> Assignee: Jason Greene
> Priority: Minor
>
> getting FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1 when i check for wildfly version.
> ./standalone.sh -v
> =========================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: /u01/app/wildfly/wildfly-10.1.0.Final
> JAVA: /u01/app/jdk1.8.0_65/bin/java
> JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 12:54:18,655 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
> WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
> 12:54:18,897 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFLY-9224) FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
by shashi avirineni (JIRA)
shashi avirineni created WFLY-9224:
--------------------------------------
Summary: FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
Key: WFLY-9224
URL: https://issues.jboss.org/browse/WFLY-9224
Project: WildFly
Issue Type: Task
Affects Versions: 10.1.0.Final
Reporter: shashi avirineni
Assignee: Jason Greene
Priority: Minor
getting FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1 when i check for wildfly version.
./standalone.sh -v
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /u01/app/wildfly/wildfly-10.1.0.Final
JAVA: /u01/app/jdk1.8.0_65/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
12:54:18,655 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
12:54:18,897 FATAL [org.jboss.as.server] (main) WFLYSRV0239: Aborting with exit code 1
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months