June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11768) Upgrade libthrift from 0.11.0 to 0.12.0

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11768?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11768: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12345 (was: https://github.com/wildfly/wildfly/pull/12109) > Upgrade libthrift from 0.11.0 to 0.12.0 > --------------------------------------- > > Key: WFLY-11768 > URL: https://issues.jboss.org/browse/WFLY-11768 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 17.0.0.Final > > > Upgrade {{org.apache.thrift:libthrift}} from 0.11.0 to 0.12.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11768) Upgrade libthrift from 0.11.0 to 0.12.0

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11768?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11768: ------------------------------------ Priority: Blocker (was: Major) > Upgrade libthrift from 0.11.0 to 0.12.0 > --------------------------------------- > > Key: WFLY-11768 > URL: https://issues.jboss.org/browse/WFLY-11768 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Reporter: James Perkins > Assignee: Juraci Paixão Kröhling > Priority: Blocker > Fix For: 17.0.0.Final > > > Upgrade {{org.apache.thrift:libthrift}} from 0.11.0 to 0.12.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11768) Upgrade libthrift from 0.11.0 to 0.12.0

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11768?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11768: --------------------------------------- Fix Version/s: 17.0.0.Final Assignee: Brian Stansberry (was: Juraci Paixão Kröhling) Resolution: Done > Upgrade libthrift from 0.11.0 to 0.12.0 > --------------------------------------- > > Key: WFLY-11768 > URL: https://issues.jboss.org/browse/WFLY-11768 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenTracing > Reporter: James Perkins > Assignee: Brian Stansberry > Priority: Blocker > Fix For: 17.0.0.Final > > > Upgrade {{org.apache.thrift:libthrift}} from 0.11.0 to 0.12.0. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Edoardo Vacchi commented on DROOLS-3819: ---------------------------------------- design document https://docs.google.com/document/d/12LcNk6tOWq-5V_fvj4pgCFJQvgjbhQZSPr1l9... > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: PR and (if possible) design document -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4105) SME Review Tech Doc

by Edoardo Vacchi (Jira)

[ https://issues.jboss.org/browse/DROOLS-4105?page=com.atlassian.jira.plugi... ] Edoardo Vacchi updated DROOLS-4105: ----------------------------------- Description: Review docs in BXMSDOC-4211 sect.2-3 (was: Review docs in BXMSDOC-4211) > SME Review Tech Doc > ------------------- > > Key: DROOLS-4105 > URL: https://issues.jboss.org/browse/DROOLS-4105 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core > > Review docs in BXMSDOC-4211 sect.2-3 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build

by Justin Holmes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ] Justin Holmes commented on DROOLS-4137: --------------------------------------- Good to know about XLS decision tables. I will get back to the example my team put together today with this new understanding and see where get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more. Thanks again for your help. I hope you are well, Mario. > KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build > --------------------------------------------------------------------------------------------- > > Key: DROOLS-4137 > URL: https://issues.jboss.org/browse/DROOLS-4137 > Project: Drools > Issue Type: Bug > Affects Versions: 7.22.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Priority: Major > > I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up. > See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information. > Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix. > We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4137) KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build

by Justin Holmes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4137?page=com.atlassian.jira.plugi... ] Justin Holmes edited comment on DROOLS-4137 at 6/6/19 11:41 AM: ---------------------------------------------------------------- Good to know about XLS decision tables. I will get back to the example my team put together today with this new understanding and see where we get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more. Thanks again for your help. I hope you are well, Mario. was (Author: jholmessr): Good to know about XLS decision tables. I will get back to the example my team put together today with this new understanding and see where get. I know the team had some challenges with maven plugin and -DgenerateModel but it is unclear to me precisely what they were. I will update as I know more. Thanks again for your help. I hope you are well, Mario. > KIE Maven Plugin Fails to Load Dependencies for KieBase when Serializing KieBase During Build > --------------------------------------------------------------------------------------------- > > Key: DROOLS-4137 > URL: https://issues.jboss.org/browse/DROOLS-4137 > Project: Drools > Issue Type: Bug > Affects Versions: 7.22.0.Final > Reporter: Justin Holmes > Assignee: Mario Fusco > Priority: Major > > I would like to have kie-maven-plugin build the KJar with a serialized KieBase so that it takes less time to boot strap drools. It appears that the maven configuration used by the kie-maven-plugin is broken, or at least there is not sufficient documentation to set it up. > See https://groups.google.com/forum/#!topic/drools-setup/0TZvE5lpcto for more information. > Documentation is VERY limited / scattered in different areas. It probably needs updates. If we can get help to get the build working / bug fixed, we would be happy to submit a doc fix. > We are trying to use drools in a severless environment (though not quite ready for Quarkus). If we are unable to use this build feature, we may be unable to use drools. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1827) Release WildFly Elytron 1.6.3.Final

by Farah Juma (Jira)

Farah Juma created ELY-1827: ------------------------------- Summary: Release WildFly Elytron 1.6.3.Final Key: ELY-1827 URL: https://issues.jboss.org/browse/ELY-1827 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12174) Configure internal broker not to check for configuration changes

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12174?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-12174: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12348 > Configure internal broker not to check for configuration changes > ---------------------------------------------------------------- > > Key: WFLY-12174 > URL: https://issues.jboss.org/browse/WFLY-12174 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Affects Versions: 17.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 17.0.0.Final > > > Currently the internal broker will scan periodically the logging.properties file to detect changes while the logging configuraiton is managed by WildFly. > Setting the configurationFileRefreshPeriod to -1 to avoid reloading of > logging.properties -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1826) Cannot connect to management interface with Java Security Manager enabled

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1826?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1826: ---------------------------- Fix Version/s: 1.6.3.CR1 > Cannot connect to management interface with Java Security Manager enabled > ------------------------------------------------------------------------- > > Key: ELY-1826 > URL: https://issues.jboss.org/browse/ELY-1826 > Project: WildFly Elytron > Issue Type: Bug > Components: Security Manager > Affects Versions: 1.6.2.Final > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > Fix For: 1.6.3.CR1 > > > When JBoss EAP is configured to authenticate management interfaces with LDAPS and RBAC enabled authentication works unless the security manager is enabled. When security manager is enabled the exception [1] occurs in console and exception [2] is logged in server.log > [1] > {code} > "Failed to connect to the controller: Unable to authenticate against controller at ... Authentication failed: all available authentication mechanisms failed: PLAIN: javax.security.sasl.SaslException: PLAIN: Server rejected authentication" > {code} > [2] > {code} > 2019-05-15 09:30:45,434 DEBUG [org.wildfly.security] (management task-3) Could not create [class javax.naming.ldap.InitialLdapContext]. Failed to connect to LDAP server.: javax.naming.CommunicationException: myldap.mydomain:636 [Root exception is java.lang.ClassNotFoundException: org/wildfly/security/auth/realm/ldap/ThreadLocalSSLSocketFactory] > at com.sun.jndi.ldap.Connection.<init>(Connection.java:238) > at com.sun.jndi.ldap.LdapClient.<init>(LdapClient.java:137) > at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1609) > at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) > at com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319) > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) > at com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210) > at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153) > at com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83) > at org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:116) > at org.jboss.as.naming.InitialContext.init(InitialContext.java:101) > at javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154) > ... > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:245) > at org.xnio.sasl.SaslUtils.evaluateResponse(SaslUtils.java:217) > at org.jboss.remoting3.remote.ServerConnectionOpenListener$AuthStepRunnable.run(ServerConnectionOpenListener.java:486) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949) > 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) > Caused by: java.lang.ClassNotFoundException: org/wildfly/security/auth/realm/ldap/ThreadLocalSSLSocketFactory > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at com.sun.jndi.ldap.VersionHelper12.loadClass(VersionHelper12.java:72) > at com.sun.jndi.ldap.Connection.createSocket(Connection.java:293) > at com.sun.jndi.ldap.Connection.<init>(Connection.java:215) > ... 42 more > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 June 2019