October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-2020) illegible code snippets in PDF

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2020?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2020. --------------------------------------- Resolution: Done Fixed when we moved to asciidoc last year. > illegible code snippets in PDF > ------------------------------ > > Key: JBRULES-2020 > URL: https://issues.jboss.org/browse/JBRULES-2020 > Project: JBRULES > Issue Type: Quality Risk > Components: drools-docs > Affects Versions: 5.0.0.CR1 > Environment: n/a > Reporter: Wolfgang Laun > Assignee: Geoffrey De Smet > Priority: Critical > Fix For: 6.0.0.Alpha1 > > Attachments: example.png, jbrules2020.png > > > In the PDF version of the docs, code snippets appear in red print on black backround. > Headache tablets cost money. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-2816) Many dependencies are tagged scope provided, while the should probably be default scope with optional=true

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2816?page=com.atlassian.jira.plug... ] Geoffrey De Smet reassigned JBRULES-2816: ----------------------------------------- Assignee: (was: Geoffrey De Smet) > Many dependencies are tagged scope provided, while the should probably be default scope with optional=true > ---------------------------------------------------------------------------------------------------------- > > Key: JBRULES-2816 > URL: https://issues.jboss.org/browse/JBRULES-2816 > Project: JBRULES > Issue Type: Task > Components: All > Affects Versions: 5.1.1.FINAL > Reporter: Geoffrey De Smet > Fix For: 6.0.0.Alpha1 > > > 86 uses of scope provided. 13 usages of optional true. > Normally scope provided is used for JDK, JAva webstart and when deploying to a servlet container, the servlet API... > Targets > String '<scope>provided</scope>' > Found usages (86 usages) > drools (4 usages) > /home/gdesmet/projects/jboss/drools (4 usages) > pom.xml (4 usages) > (968, 9) <scope>provided</scope> > (975, 9) <scope>provided</scope> > (1576, 9) <scope>provided</scope> > (1582, 9) <scope>provided</scope> > drools-api (12 usages) > /home/gdesmet/projects/jboss/drools/drools-api (12 usages) > pom.xml (12 usages) > (18, 7) <scope>provided</scope> > (23, 7) <scope>provided</scope> > (28, 7) <scope>provided</scope> > (33, 7) <scope>provided</scope> > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > (48, 7) <scope>provided</scope> > (53, 7) <scope>provided</scope> > (58, 7) <scope>provided</scope> > (63, 7) <scope>provided</scope> > (68, 7) <scope>provided</scope> > (73, 7) <scope>provided</scope> > drools-bpmn2 (2 usages) > /home/gdesmet/projects/jboss/drools/drools-process/drools-bpmn2 (2 usages) > pom.xml (2 usages) > (119, 7) <scope>provided</scope> > (124, 7) <scope>provided</scope> > drools-camel (1 usage) > /home/gdesmet/projects/jboss/drools/drools-camel (1 usage) > pom.xml (1 usage) > (186, 7) <scope>provided</scope> > drools-compiler (7 usages) > /home/gdesmet/projects/jboss/drools/drools-compiler (7 usages) > pom.xml (7 usages) > (23, 7) <scope>provided</scope> > (28, 7) <scope>provided</scope> > (82, 7) <scope>provided</scope> > (87, 7) <scope>provided</scope> > (92, 7) <scope>provided</scope> > (97, 7) <scope>provided</scope> > (102, 7) <scope>provided</scope> > drools-core (7 usages) > /home/gdesmet/projects/jboss/drools/drools-core (7 usages) > pom.xml (7 usages) > (18, 7) <scope>provided</scope> > (23, 7) <scope>provided</scope> > (56, 7) <scope>provided</scope> > (61, 7) <scope>provided</scope> > (66, 7) <scope>provided</scope> > (71, 7) <scope>provided</scope> > (76, 7) <scope>provided</scope> > drools-decisiontables (2 usages) > /home/gdesmet/projects/jboss/drools/drools-decisiontables (2 usages) > pom.xml (2 usages) > (32, 7) <scope>provided</scope> > (37, 7) <scope>provided</scope> > drools-flow-compiler (7 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-compiler (7 usages) > pom.xml (7 usages) > (17, 7) <scope>provided</scope> > (22, 7) <scope>provided</scope> > (42, 7) <scope>provided</scope> > (47, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (57, 7) <scope>provided</scope> > (62, 7) <scope>provided</scope> > drools-flow-core (7 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-core (7 usages) > pom.xml (7 usages) > (17, 7) <scope>provided</scope> > (22, 7) <scope>provided</scope> > (37, 7) <scope>provided</scope> > (42, 7) <scope>provided</scope> > (47, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (57, 7) <scope>provided</scope> > drools-flow-persistence-jpa (4 usages) > /home/gdesmet/projects/jboss/drools/drools-flow-persistence-jpa (4 usages) > pom.xml (4 usages) > (98, 7) <scope>provided</scope> > (103, 7) <scope>provided</scope> > (109, 7) <scope>provided</scope> > (114, 7) <scope>provided</scope> > drools-grid (12 usages) > /home/gdesmet/projects/jboss/drools/drools-grid (3 usages) > pom.xml (3 usages) > (24, 13) <scope>provided</scope> > (29, 13) <scope>provided</scope> > (34, 13) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-distributed-api (3 usages) > pom.xml (3 usages) > (36, 10) <scope>provided</scope> > (41, 10) <scope>provided</scope> > (46, 10) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-local (3 usages) > pom.xml (3 usages) > (33, 7) <scope>provided</scope> > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > /home/gdesmet/projects/jboss/drools/drools-grid/drools-grid-remote-api (3 usages) > pom.xml (3 usages) > (38, 7) <scope>provided</scope> > (43, 7) <scope>provided</scope> > (48, 7) <scope>provided</scope> > drools-guvnor (5 usages) > /home/gdesmet/projects/jboss/drools/drools-guvnor (5 usages) > pom.xml (5 usages) > (205, 7) <scope>provided</scope> > (222, 7) <scope>provided</scope> > (265, 7) <scope>provided</scope> > (270, 7) <scope>provided</scope> > (296, 7) <scope>provided</scope> > drools-ide-common (1 usage) > /home/gdesmet/projects/jboss/drools/drools-ide-common (1 usage) > pom.xml (1 usage) > (37, 7) <scope>provided</scope> > drools-jsr94 (1 usage) > /home/gdesmet/projects/jboss/drools/drools-jsr94 (1 usage) > pom.xml (1 usage) > (73, 7) <scope>provided</scope> > drools-persistence-jpa (4 usages) > /home/gdesmet/projects/jboss/drools/drools-persistence-jpa (4 usages) > pom.xml (4 usages) > (83, 7) <scope>provided</scope> > (88, 7) <scope>provided</scope> > (94, 7) <scope>provided</scope> > (99, 7) <scope>provided</scope> > drools-spring (2 usages) > /home/gdesmet/projects/jboss/drools/drools-container/drools-spring (2 usages) > pom.xml (2 usages) > (53, 7) <scope>provided</scope> > (59, 7) <scope>provided</scope> > gwt-console-server-drools (8 usages) > /home/gdesmet/projects/jboss/drools/drools-process/drools-gwt-server-war (8 usages) > pom.xml (8 usages) > (46, 7) <scope>provided</scope> > (52, 7) <scope>provided</scope> > (58, 7) <scope>provided</scope> > (64, 7) <scope>provided</scope> > (70, 7) <scope>provided</scope> > (76, 7) <scope>provided</scope> > (82, 7) <scope>provided</scope> > (88, 7) <scope>provided</scope> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBRULES-2908) Build: Our parent pom must extend jboss parent pom and do not replicate anything in there

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/JBRULES-2908?page=com.atlassian.jira.plug... ] Geoffrey De Smet resolved JBRULES-2908. --------------------------------------- Resolution: Done Fixed a long time ago > Build: Our parent pom must extend jboss parent pom and do not replicate anything in there > ----------------------------------------------------------------------------------------- > > Key: JBRULES-2908 > URL: https://issues.jboss.org/browse/JBRULES-2908 > Project: JBRULES > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Geoffrey De Smet > Priority: Minor > > <parent> > <groupId>org.jboss</groupId> > <artifactId>jboss-parent</artifactId> > <version>5</version> > </parent> > More info in http://community.jboss.org/wiki/MavenDeployingaSnapshot -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3334) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

Masafumi Miura created WFCORE-3334: -------------------------------------- Summary: Expose number of busy threads in the task worker thread pool via CLI (management API) Key: WFCORE-3334 URL: https://issues.jboss.org/browse/WFCORE-3334 Project: WildFly Core Issue Type: Feature Request Components: IO Affects Versions: 3.0.4.Final Reporter: Masafumi Miura Assignee: David Lloyd WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3333) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3333?page=com.atlassian.jira.plugi... ] Masafumi Miura updated WFCORE-3333: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2868, https://github.com/wildfly/wildfly-core/pull/2869 (was: https://github.com/wildfly/wildfly-core/pull/2868) > Expose number of busy threads in the task worker thread pool via CLI (management API) > ------------------------------------------------------------------------------------- > > Key: WFCORE-3333 > URL: https://issues.jboss.org/browse/WFCORE-3333 > Project: WildFly Core > Issue Type: Feature Request > Components: IO > Affects Versions: 3.0.4.Final > Reporter: Masafumi Miura > Assignee: David Lloyd > > WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8547) Elytron, SPNEGO in deployment exceptional states handling, 500 should be returned

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8547?page=com.atlassian.jira.plugin.... ] Jan Kalina closed WFLY-8547. ---------------------------- Resolution: Cannot Reproduce Bug Already resolved: * no authentication mechanisms are available (wrong protocol in http-authentication-factory) correctly returns 500 in currect version * exception evaluating the request and there are no other mechanisms available (wrong principal name in kerberos security factory) correctly returns 500 in currect version Just note second scenario requires to set obtain-kerberos-ticket=true to ensure incorrect principal name causes server-side exception. > Elytron, SPNEGO in deployment exceptional states handling, 500 should be returned > --------------------------------------------------------------------------------- > > Key: WFLY-8547 > URL: https://issues.jboss.org/browse/WFLY-8547 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > > During SPNEGO in deployment authentication, there should be these rules applied > * If authentication is required and no authentication mechanisms are available for use report - 500 > * If a mechanism throws an exception evaluating the request and there are no other mechanisms available - 500 > Same as Elytron securing management interface discussed on https://issues.jboss.org/browse/JBEAP-9970?focusedCommentId=13386447&page... > I test these scenarios by: > * wrong protocol=DOES_NOT_EXIST in http-authentication-factory > ** I get 403 on first GET > ** {code} > 14:35:41,907 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='SPNEGO' host-name='localhost.localdomain' protocol='http' > 14:35:41,908 TRACE [org.wildfly.security] (default task-1) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='SPNEGO', hostName='localhost.localdomain', protocol='http'. > {code} > * wrong principal name in kerberos security factory > ** I get 401 on first GET > ** {code} > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='SPNEGO' host-name='localhost.localdomain' protocol='http' > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Evaluating SPNEGO request: cached GSSContext = null > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Obtaining GSSCredential for the service from callback handler... > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) No valid cached credential, obtaining new one... > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Logging in using LoginContext and subject [Subject: > ] > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Logging in using LoginContext and subject [Subject: > Principal: HTTP/wronghost(a)JBOSS.ORG > Private Credential: /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > ] succeed > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Creating GSSName for Principal 'HTTP/wronghost(a)JBOSS.ORG' > 14:38:37,282 INFO [stdout] (default task-1) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > 14:38:37,282 INFO [stdout] (default task-1) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Obtained GSSCredentialCredential [org.wildfly.security.credential.GSSKerberosCredential@1f] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Handling ServerCredentialCallback: successfully obtained credential type type=class org.wildfly.security.credential.GSSKerberosCredential, algorithm=null, params=null > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Using SpnegoAuthenticationMechanism to authenticate HTTP/wronghost(a)JBOSS.ORG using the following mechanisms: [[Lorg.ietf.jgss.Oid;@7e6a9da] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Caching GSSContext sun.security.jgss.GSSContextImpl@2df4c570 > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Caching KerberosTicket null > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Sent HTTP authorizations: [null] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Request lacks valid authentication credentials > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8547) Elytron, SPNEGO in deployment exceptional states handling, 500 should be returned

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8547?page=com.atlassian.jira.plugin.... ] Jan Kalina reassigned WFLY-8547: -------------------------------- Assignee: Jan Kalina (was: Darran Lofthouse) > Elytron, SPNEGO in deployment exceptional states handling, 500 should be returned > --------------------------------------------------------------------------------- > > Key: WFLY-8547 > URL: https://issues.jboss.org/browse/WFLY-8547 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Martin Choma > Assignee: Jan Kalina > > During SPNEGO in deployment authentication, there should be these rules applied > * If authentication is required and no authentication mechanisms are available for use report - 500 > * If a mechanism throws an exception evaluating the request and there are no other mechanisms available - 500 > Same as Elytron securing management interface discussed on https://issues.jboss.org/browse/JBEAP-9970?focusedCommentId=13386447&page... > I test these scenarios by: > * wrong protocol=DOES_NOT_EXIST in http-authentication-factory > ** I get 403 on first GET > ** {code} > 14:35:41,907 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='SPNEGO' host-name='localhost.localdomain' protocol='http' > 14:35:41,908 TRACE [org.wildfly.security] (default task-1) java.lang.IllegalStateException: ELY01119: Unable to resolve MechanismConfiguration for mechanismType='HTTP', mechanismName='SPNEGO', hostName='localhost.localdomain', protocol='http'. > {code} > * wrong principal name in kerberos security factory > ** I get 401 on first GET > ** {code} > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Handling MechanismInformationCallback type='HTTP' name='SPNEGO' host-name='localhost.localdomain' protocol='http' > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Evaluating SPNEGO request: cached GSSContext = null > 14:38:37,280 TRACE [org.wildfly.security] (default task-1) Obtaining GSSCredential for the service from callback handler... > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) No valid cached credential, obtaining new one... > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Logging in using LoginContext and subject [Subject: > ] > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Logging in using LoginContext and subject [Subject: > Principal: HTTP/wronghost(a)JBOSS.ORG > Private Credential: /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > ] succeed > 14:38:37,281 TRACE [org.wildfly.security] (default task-1) Creating GSSName for Principal 'HTTP/wronghost(a)JBOSS.ORG' > 14:38:37,282 INFO [stdout] (default task-1) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > 14:38:37,282 INFO [stdout] (default task-1) Found KeyTab /home/mchoma/workspace/git-repositories/tests-ldap-kerberos-eap7/eap71/target/krb/krb.6037194374738244164.keytab for HTTP/wronghost(a)JBOSS.ORG > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Obtained GSSCredentialCredential [org.wildfly.security.credential.GSSKerberosCredential@1f] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Handling ServerCredentialCallback: successfully obtained credential type type=class org.wildfly.security.credential.GSSKerberosCredential, algorithm=null, params=null > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Using SpnegoAuthenticationMechanism to authenticate HTTP/wronghost(a)JBOSS.ORG using the following mechanisms: [[Lorg.ietf.jgss.Oid;@7e6a9da] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Caching GSSContext sun.security.jgss.GSSContextImpl@2df4c570 > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Caching KerberosTicket null > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Sent HTTP authorizations: [null] > 14:38:37,282 TRACE [org.wildfly.security] (default task-1) Request lacks valid authentication credentials > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3333) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3333?page=com.atlassian.jira.plugi... ] Masafumi Miura updated WFCORE-3333: ----------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2868 > Expose number of busy threads in the task worker thread pool via CLI (management API) > ------------------------------------------------------------------------------------- > > Key: WFCORE-3333 > URL: https://issues.jboss.org/browse/WFCORE-3333 > Project: WildFly Core > Issue Type: Feature Request > Components: IO > Affects Versions: 3.0.4.Final > Reporter: Masafumi Miura > Assignee: David Lloyd > > WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1679) FEEL list filter returns empty collection when there are errors evaluating filter

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1679?page=com.atlassian.jira.plugi... ] Fedor Gavrilov reassigned DROOLS-1679: -------------------------------------- Assignee: Fedor Gavrilov (was: Edson Tirelli) > FEEL list filter returns empty collection when there are errors evaluating filter > --------------------------------------------------------------------------------- > > Key: DROOLS-1679 > URL: https://issues.jboss.org/browse/DROOLS-1679 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Fedor Gavrilov > Priority: Minor > Fix For: 7.4.0.Final > > > When having this FEEL list with filter which is incorrect: > {code:java} > ["a", "b", "c"][a] > {code} > the evaluation returns an empty list instead of null. Output of this test is here: > https://gist.github.com/baldimir/18232741fdf1b425ba84d00d83edb939 > I will provide PR with a reproducer today. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3333) Expose number of busy threads in the task worker thread pool via CLI (management API)

by Masafumi Miura (JIRA)

Masafumi Miura created WFCORE-3333: -------------------------------------- Summary: Expose number of busy threads in the task worker thread pool via CLI (management API) Key: WFCORE-3333 URL: https://issues.jboss.org/browse/WFCORE-3333 Project: WildFly Core Issue Type: Feature Request Components: IO Affects Versions: 3.0.4.Final Reporter: Masafumi Miura Assignee: David Lloyd WFLY-8203 / XNIO-283 exposed number of busy threads in the task worker thread pool via JMX. It would be useful to expose the metric via CLI (management API). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017