November 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3379) RuntimeService API should not require a KSession to create an instance

by Edoardo Vacchi (Jira)

Edoardo Vacchi created DROOLS-3379: -------------------------------------- Summary: RuntimeService API should not require a KSession to create an instance Key: DROOLS-3379 URL: https://issues.jboss.org/browse/DROOLS-3379 Project: Drools Issue Type: Enhancement Reporter: Edoardo Vacchi Assignee: Edoardo Vacchi {{<T> T getKieRuntime(Class<T> cls)}} is in {{KieSession}} but in some cases a session is overkill. A KieBase is enough (TBF a package may be enough, but let's go with KieBase for now) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11430) tasks-rs: Add to README a instruction to comment an import line

by Sande Gilda (Jira)

[ https://issues.jboss.org/browse/WFLY-11430?page=com.atlassian.jira.plugin... ] Sande Gilda moved JBEAP-15934 to WFLY-11430: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-11430 (was: JBEAP-15934) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: (was: 7.2.0.GA.CR1) > tasks-rs: Add to README a instruction to comment an import line > ---------------------------------------------------------------- > > Key: WFLY-11430 > URL: https://issues.jboss.org/browse/WFLY-11430 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Sande Gilda > Assignee: Sande Gilda > Priority: Major > > Currently maven checkstyle plugin [fails|https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7.x-...] on unused import after adding JSON support to the tasks-rs quickstart: > {noformat} > tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java:30:8: Unused import - javax.ws.rs.Produces. [UnusedImports] > {noformat} > Our QE tests are fixed now, but for the customers it would be useful to have an instruction to comment the line > {noformat} > import javax.ws.rs.Produces > {noformat} > in _tasks-rs/src/main/java/org/jboss/as/quickstarts/tasksrs/service/TaskResource.java_ file, line 30. > Ii would be nice to have this instruction in _Modify this Quickstart to Support JSON Representations of Tasks_ section, step 3, _Add comments to this line_ sentence. > Thanks! -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11374) Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted

by Srinivas ev (Jira)

[ https://issues.jboss.org/browse/WFLY-11374?page=com.atlassian.jira.plugin... ] Srinivas ev commented on WFLY-11374: ------------------------------------ Hi [~mnovak], How are you stopping the Wildfly master service ? - I am able to see master announcing backup when I stopped the master using ctrl+C and restarted. Updating cluster password in standalone-full-ha.xml can be ignored as it worked. But this is not the same behaviour when I used below of the options for stopping the wildfly service and restarted. 1. Using custom start and stop process. Stop process contains kill for pid of the Wildfly. (kill -15 pid). This custom start process just invokes standalone.sh with -D params. 2. ./jboss-cli.sh -c --controller=xxx:xxx:xxx:xxx:13990 --command=":shutdown()" --user=admin --password=admin@123 Can you let me know what is the correct way to stop the master Wildfly service.I can explain more in case it required. > Master Artemis in Wildfly 10.1.0.Final is not announcing backup when restarted > ------------------------------------------------------------------------------ > > Key: WFLY-11374 > URL: https://issues.jboss.org/browse/WFLY-11374 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Srinivas ev > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: active standalone full ha.xml, master and slave log samples on startup.txt, master restart.txt, master shutdown.txt, master-server-linux.log, master-server-windows.log, master.xml, rotateserver_active.log, rotateserver_active.log, rotateserver_backup.log, rotateserver_slave.log, slave standalone full ha.xml, slave-server-linux.log, slave-server-windows.log, slave.xml > > > I have 2 wildfly servers acting as artemis master and slave. I am expecting failback and replication and the related configurations are done for this to work. > This is working as expected when I have the setup in Windows. Failing in linux RHEL 7.3 machine. > master in standalone-full-ha.xml - refer master.xml > slave in standalone-full-ha.xml - refer slave.xml > In the startup script, I am passing all the values for placeholders of my server host ip's accordingly. > Test scenario - > 1. Bring master up. > 2. Bring slave up. > 3. slave will announce the backup. (AMQ221031: backup announced). > 4. Make master down. > 5. Replication is success. > 6. Slave is acting as master/live. > 7. Make master up. > Issue - master is unable to announce the backup and starts normally as a standalone wildfly. > This backup announcement works fine in windows and failover also works as expected. > Please let me know if anything specific required along with this details. > Artemis jar version - artemis-*****-1.1.0.wildfly-017.jar > in path - /opt/aor/${my project}/wildfly/modules/system/layers/base/org/apache/activemq/artemis/main > Few logs I found which may be impacting and I am not clear - > 1.2018-11-21 14:28:07,238 TRACE [org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge] (Thread-18 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@38e819b6-2112524495)) Setting up bridge between TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-30 and ServerLocatorImpl [initialConnectors=[TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEnabled=true&httpPpgradeEndpoint=http-acceptor&port=12080&host=135-250-139-41], discoveryGroupConfiguration=null]: java.lang.Exception: trace > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionBridge.<init>(ClusterConnectionBridge.java:129) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.createNewRecord(ClusterConnectionImpl.java:778) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl.nodeUP(ClusterConnectionImpl.java:698) > at org.apache.activemq.artemis.core.client.impl.Topology$1.run(Topology.java:264) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > 2. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-981) Referrals roles assignment for referral user does not work for AdvancedLdapLoginModule with Active Directory

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/SECURITY-981?page=com.atlassian.jira.plug... ] Darran Lofthouse updated SECURITY-981: -------------------------------------- Fix Version/s: Negotiation_3_0_5_CR1 > Referrals roles assignment for referral user does not work for AdvancedLdapLoginModule with Active Directory > ------------------------------------------------------------------------------------------------------------ > > Key: SECURITY-981 > URL: https://issues.jboss.org/browse/SECURITY-981 > Project: PicketBox > Issue Type: Bug > Components: Negotiation > Affects Versions: Negotiation_3_0_4_Final > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > Priority: Minor > Fix For: Negotiation_3_0_5_CR1 > > > Consider two MS Active Directory domains with configured crossRef to each other. EAP using AdvancedLdapLoginModule for MS AD with referrals and rolesCtxDN is set to the referral DN where user account are stored; also EAP is configured for searching roles based on users entries (mapping users to roles). > If referral users (from EAP point of view - hostname is configured for original LDAP and user is obtained as referral user - from second of domains) authenticate then they have not assigned roles from AD attribute from 'roleAttributeID' option. > Example: > I have two MS AD domains - DC=jboss,DC=test (Domain A) and DC=jboss,DC=test2 (Domain B) with crossRef. > Part of ldif for Domain A: > {code} > ... > dn: CN=TheDuke,OU=Roles,O=eapqe,DC=jboss,DC=test > objectClass: groupOfNames > objectClass: top > cn: TheDuke > businessCategory: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > member: CN=jdukeNotUsed,OU=People,O=eapqe,DC=jboss,DC=test > ... > {code} > Part of ldif for Domain B > {code} > ... > dn: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > objectclass: top > objectclass: person > objectClass: inetOrgPerson > cn: jduke > sn: Duke > description: CN=TheDuke,OU=Roles,O=eapqe,DC=jboss,DC=test > description: CN=Admin,OU=Roles,O=eapqe,DC=jboss,DC=test2 > userPassword: Password1 > dn: CN=Admin,OU=Roles,O=eapqe,DC=jboss,DC=test2 > objectClass: groupOfNames > objectClass: top > cn: Admin > businessCategory: CN=jduke,OU=People,O=eapqe,DC=jboss,DC=test2 > member: CN=jdukeNotUsed,OU=People,O=eapqe,DC=jboss,DC=test2 > ... > {code} > EAP AdvancedLdapLoginModule is configured: > {code:xml} > <security-domain name="AdvancedLdapReferrals"> > <authentication> > <login-module code="AdvancedLdap" flag="required"> > <module-option name="java.naming.factory.initial" value="com.sun.jndi.ldap.LdapCtxFactory"/> > <module-option name="java.naming.provider.url" value="HOSTNAME_OF_DOMAIN_A"/> > <module-option name="bindDN" value="BIND_DN"/> > <module-option name="bindCredential" value="PASSWORD"/> > <module-option name="referralUserAttributeIDToCheck" value="businessCategory"/> > <module-option name="roleAttributeIsDN" value="true"/> > <module-option name="roleFilter" value="(CN={0})"/> > <module-option name="roleAttributeID" value="description"/> > <module-option name="rolesCtxDN" value="OU=People,O=eapqe,DC=jboss,DC=test2"/> > <module-option name="java.naming.security.authentication" value="simple"/> > <module-option name="baseCtxDN" value="OU=People,O=eapqe,DC=jboss,DC=test2"/> > <module-option name="java.naming.referral" value="follow"/> > <module-option name="throwValidateError" value="true"/> > <module-option name="baseFilter" value="(CN={0})"/> > <module-option name="roleNameAttributeID" value="CN"/> > </login-module> > </authentication> > </security-domain> > {code} > Then when jduke try to authenticate to application roles TheDuke and Admin should be assigned to him. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3243) [DMN Designer] Move the Data Type dialog to a tab in the DMN editor

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3243?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3243: -------------------------------- Description: https://issues.jboss.org/browse/DROOLS-3156 h2. Manual Acceptance Test - Chrome - Firefox - Edge was:https://issues.jboss.org/browse/DROOLS-3156 > [DMN Designer] Move the Data Type dialog to a tab in the DMN editor > ------------------------------------------------------------------- > > Key: DROOLS-3243 > URL: https://issues.jboss.org/browse/DROOLS-3243 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > https://issues.jboss.org/browse/DROOLS-3156 > h2. Manual Acceptance Test > - Chrome > - Firefox > - Edge -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3355) Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3355?page=com.atlassian.jira.plugi... ] Edoardo Vacchi edited comment on DROOLS-3355 at 11/28/18 5:19 AM: ------------------------------------------------------------------ *Overview:* Assembler/Weaver/Runtime is the triplet of services that constitute a "Knowledge Plug-In", i.e. a component that plugs into the Drools (or maybe more correctly, KIE) core to provide a "knowledge runtime" and a common interface to submit pieces of knowledge to such runtimes in a uniform way. *AssemblerService* finds or create a package for a given Resource; inserts the resource into the package, and the package into a registry. The package notion is akin to that of namespace (or "Java-style" packages). *WeaverService* merges the contents of a fresh package to an existing package, when the name of such packages matches. *RuntimeService*, on the other hand is completely separate from the other two. For a given Session, it returns a runtime instance of a "knowledge plugin" (e.g, DMN, PMML, etc.). was (Author: evacchi): *Overview:* Assembler/Weaver/Runtime is the triplet of services that constitute a "Knowledge Plug-In", i.e. a component that plugs into the Drools (or maybe more correctly, KIE) core to provide a "knowledge runtime" and a common interface to submit pieces of knowledge to such runtimes in a uniform way. *AssemblerService* finds or create a package for a given Resource; inserts the resource into the package, and the package into a registry. Lots of boilerplate. In many cases, the useful logic boils down to parsing the Resource and adding it to a relevant package. The package notion is akin to that of namespace (or "Java-style" packages). *WeaverService* merges the contents of a fresh package to an existing package, when the name of such packages matches. *RuntimeService*, on the other hand is completely separate from the other two. For a given Session, it returns a runtime instance of a "knowledge plugin" (e.g, DMN, PMML, etc.). > Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes > --------------------------------------------------------------------------------------- > > Key: DROOLS-3355 > URL: https://issues.jboss.org/browse/DROOLS-3355 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current API may be too Drools/Rule-Engine-centric, might want to rethink it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3355) Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3355?page=com.atlassian.jira.plugi... ] Edoardo Vacchi edited comment on DROOLS-3355 at 11/28/18 5:18 AM: ------------------------------------------------------------------ *Overview:* Assembler/Weaver/Runtime is the triplet of services that constitute a "Knowledge Plug-In", i.e. a component that plugs into the Drools (or maybe more correctly, KIE) core to provide a "knowledge runtime" and a common interface to submit pieces of knowledge to such runtimes in a uniform way. *AssemblerService* finds or create a package for a given Resource; inserts the resource into the package, and the package into a registry. Lots of boilerplate. In many cases, the useful logic boils down to parsing the Resource and adding it to a relevant package. The package notion is akin to that of namespace (or "Java-style" packages). *WeaverService* merges the contents of a fresh package to an existing package, when the name of such packages matches. *RuntimeService*, on the other hand is completely separate from the other two. For a given Session, it returns a runtime instance of a "knowledge plugin" (e.g, DMN, PMML, etc.). > Discuss and verify Assembler/Weaver API to better support for jBPM and generic runtimes > --------------------------------------------------------------------------------------- > > Key: DROOLS-3355 > URL: https://issues.jboss.org/browse/DROOLS-3355 > Project: Drools > Issue Type: Enhancement > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Current API may be too Drools/Rule-Engine-centric, might want to rethink it -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11082) ClassCastExceptions and unexpected ServletContainerInitializer executions

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11082?page=com.atlassian.jira.plugin... ] Bartosz Baranowski commented on WFLY-11082: ------------------------------------------- Can we get proper reproducer? > ClassCastExceptions and unexpected ServletContainerInitializer executions > ------------------------------------------------------------------------- > > Key: WFLY-11082 > URL: https://issues.jboss.org/browse/WFLY-11082 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 14.0.1.Final > Reporter: Alexander Kudrevatykh > Assignee: Jason Greene > Priority: Major > Attachments: dependencies.zip > > > I got unexpected ClassCastExceptions in setup as in attached test > ServiceLoader provide only one instance of SCI, but wildlfy executes it twice > More weird - wrong Set of classes passed to onStartup method - classes are not extends @HandlesTypes annotation (because they loaded with different classloaders) > sorry for complex description, look for attached test -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11429) Avoid hard-coding of the groupId in wildfly-client-all artifact

by Yeray Borges (Jira)

Yeray Borges created WFLY-11429: ----------------------------------- Summary: Avoid hard-coding of the groupId in wildfly-client-all artifact Key: WFLY-11429 URL: https://issues.jboss.org/browse/WFLY-11429 Project: WildFly Issue Type: Task Reporter: Yeray Borges Assignee: Yeray Borges Currently, we have {{org.wildfly}} hardcoded in {{wildfly-client-all}} artifact, however the use of {{${project.groupId}}} facilitates the switching to different product branches. See relate issue to get more information. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11313) Does the wildfly 14 support java ee security api 1.0?

by Bartosz Baranowski (Jira)

[ https://issues.jboss.org/browse/WFLY-11313?page=com.atlassian.jira.plugin... ] Bartosz Baranowski resolved WFLY-11313. --------------------------------------- Resolution: Explained Please ask questions on forums: https://developer.jboss.org/en/wildfly?view=discussions > Does the wildfly 14 support java ee security api 1.0? > ----------------------------------------------------- > > Key: WFLY-11313 > URL: https://issues.jboss.org/browse/WFLY-11313 > Project: WildFly > Issue Type: Support Patch > Components: EE > Affects Versions: 14.0.0.Final > Reporter: 69699 i > Assignee: Bartosz Baranowski > Priority: Minor > Attachments: EE8Security.7z > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 November 2018