September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4573) Cell selection doesn't span the entire cell

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4573: ---------------------------------- Summary: Cell selection doesn't span the entire cell Key: DROOLS-4573 URL: https://issues.jboss.org/browse/DROOLS-4573 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing, Test Scenarios Editor Affects Versions: 7.27.0.Final Reporter: Yeser Amer Assignee: Yeser Amer Fix For: 7.28.0.Final Attachments: Screen Shot 2019-09-25 at 9.44.24 AM.png If you select a spanned cell, only the subcell which belongs to the selected column is marked as selected -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-544) provide a system property so we can pass in the ZooKeeper user and password when using an authenticated ZK

by Alexandre Bakos (Jira)

[ https://issues.jboss.org/browse/DROOLS-544?page=com.atlassian.jira.plugin... ] Alexandre Bakos closed DROOLS-544. ---------------------------------- Resolution: Won't Fix > provide a system property so we can pass in the ZooKeeper user and password when using an authenticated ZK > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-544 > URL: https://issues.jboss.org/browse/DROOLS-544 > Project: Drools > Issue Type: Feature Request > Reporter: James Strachan > Assignee: Alexandre Bakos > Priority: Major > > I see the system property for passing in ZK URL > http://docs.jboss.org/drools/release/6.0.1.Final/drools-docs/html/wb.Work... > which is great - so org.uberfire.cluster.zk lets us pass in the ZK URL - so when using drools with fabric8 we can pass in the existing ZK ensemble URL. > However we need 2 system properties to also pass in the ZK user and password; as ZK is authenticated by default in fabric8 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4571) It's possible to set an empty title header

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4571?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4571: -------------------------------- Labels: ScenarioSimulation (was: ) > It's possible to set an empty title header > ------------------------------------------ > > Key: DROOLS-4571 > URL: https://issues.jboss.org/browse/DROOLS-4571 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation > Fix For: 7.28.0.Final > > > In Scenario Test, it is currently possibile to set an empty label as Instance name or property name. This should be forbidden. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12525) Upgrade netty-xnio-transport to 0.1.7.Final

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12525?page=com.atlassian.jira.plugin... ] Flavia Rainone commented on WFLY-12525: --------------------------------------- I'm downgrading to Critical, because the problem is not entirely solved by netty-xnio-transport 0.1.7.Final, we are still investigating. > Upgrade netty-xnio-transport to 0.1.7.Final > ------------------------------------------- > > Key: WFLY-12525 > URL: https://issues.jboss.org/browse/WFLY-12525 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Critical > Fix For: 18.0.0.Final > > > Upgrade the netty-xnio-transport containing fix for: [XNIO#14|https://github.com/xnio/netty-xnio-transport/issues/14] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12525) Upgrade netty-xnio-transport to 0.1.7.Final

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12525?page=com.atlassian.jira.plugin... ] Flavia Rainone updated WFLY-12525: ---------------------------------- Priority: Critical (was: Blocker) > Upgrade netty-xnio-transport to 0.1.7.Final > ------------------------------------------- > > Key: WFLY-12525 > URL: https://issues.jboss.org/browse/WFLY-12525 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Flavia Rainone > Assignee: Flavia Rainone > Priority: Critical > Fix For: 18.0.0.Final > > > Upgrade the netty-xnio-transport containing fix for: [XNIO#14|https://github.com/xnio/netty-xnio-transport/issues/14] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12188) Option READ_TIMEOUT is ignored

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ] Flavia Rainone updated WFLY-12188: ---------------------------------- Labels: (was: blocker-WF18) > Option READ_TIMEOUT is ignored > ------------------------------ > > Key: WFLY-12188 > URL: https://issues.jboss.org/browse/WFLY-12188 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 17.0.0.Final > Reporter: Joerg Baesner > Assignee: Flavia Rainone > Priority: Major > > What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See: > {code} > <remote connector-ref="http-remoting-connector" thread-pool-name="default"> > <channel-creation-options> > <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/> > <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> > </channel-creation-options> > </remote> > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> >  > <properties> > <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/> > <property name="KEEP_ALIVE" value="true"/> > <property name="READ_TIMEOUT" value="10000"/> > <property name="WRITE_TIMEOUT" value="10000"/> > </properties> > </http-connector> > {code} > None of those options work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12188) Option READ_TIMEOUT is ignored

by Flavia Rainone (Jira)

[ https://issues.jboss.org/browse/WFLY-12188?page=com.atlassian.jira.plugin... ] Flavia Rainone updated WFLY-12188: ---------------------------------- Priority: Major (was: Blocker) > Option READ_TIMEOUT is ignored > ------------------------------ > > Key: WFLY-12188 > URL: https://issues.jboss.org/browse/WFLY-12188 > Project: WildFly > Issue Type: Bug > Components: EJB, Remoting > Affects Versions: 17.0.0.Final > Reporter: Joerg Baesner > Assignee: Flavia Rainone > Priority: Major > Labels: blocker-WF18 > > What's the difference of the {{READ_TIMEOUT}} in _ejb3_ subsystem vs. _remoting_ subsystem? See: > {code} > <remote connector-ref="http-remoting-connector" thread-pool-name="default"> > <channel-creation-options> > <option name="READ_TIMEOUT" value="${prop.remoting-connector.read.timeout:20}" type="xnio"/> > <option name="MAX_OUTBOUND_MESSAGES" value="1234" type="remoting"/> > </channel-creation-options> > </remote> > {code} > {code} > <subsystem xmlns="urn:jboss:domain:remoting:4.0"> > <endpoint/> > <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"> >  > <properties> > <property name="org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL" value="5000"/> > <property name="KEEP_ALIVE" value="true"/> > <property name="READ_TIMEOUT" value="10000"/> > <property name="WRITE_TIMEOUT" value="10000"/> > </properties> > </http-connector> > {code} > None of those options work. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12598) (7.2.z) ConnectionSecurityContext.getConnectionPrincipals leads to IllegalStateException getConnectionPrincipals

by Ilia Vassilev (Jira)

Ilia Vassilev created WFLY-12598: ------------------------------------ Summary: (7.2.z) ConnectionSecurityContext.getConnectionPrincipals leads to IllegalStateException getConnectionPrincipals Key: WFLY-12598 URL: https://issues.jboss.org/browse/WFLY-12598 Project: WildFly Issue Type: Bug Components: Security Affects Versions: 18.0.0.Beta1 Reporter: Ilia Vassilev Assignee: Daniel Straub Fix For: 18.0.0.Final The commit https://github.com/wildfly/wildfly/commit/121c02b004adaca76e306bf3e8c16b3... leads direct to an IllegalStateException during anonymous login. In this case is no Realm available and the constructor of new RealmUser(realm, principal.getName()) throws an IllegalStateException. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-12592: ----------------------------------------- Setting the 'default-ssl-context' attribute on the Elytron subsystem provides a way to register a JVM wide SSLContext managed by the Elytron subsystem without the need for the 'javax.net.ssl' system properties. > Usage of Elytron's SSL-Context in establishing SSL communication with DataBase > ------------------------------------------------------------------------------ > > Key: WFLY-12592 > URL: https://issues.jboss.org/browse/WFLY-12592 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Priority: Major > > To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFLY-12592) Usage of Elytron's SSL-Context in establishing SSL communication with DataBase

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-12592?page=com.atlassian.jira.plugin... ] Darran Lofthouse reassigned WFLY-12592: --------------------------------------- Assignee: (was: Brian Stansberry) > Usage of Elytron's SSL-Context in establishing SSL communication with DataBase > ------------------------------------------------------------------------------ > > Key: WFLY-12592 > URL: https://issues.jboss.org/browse/WFLY-12592 > Project: WildFly > Issue Type: Feature Request > Components: Security > Affects Versions: 14.0.0.Final > Reporter: Saurabh Shriramwar > Priority: Major > > To secure the connection between Wildfly and datasource using TCP/IP over SSL datasource should be able to utilize the ssl-context for trust-managers (pointing to java keystore or truststore containing the datasource CA certificates) configured in Elytron so that Wildfly can trust the datasource connection instead of setting java truststore in the system properties or providing as JAVA_OPTS (-Djavax.net.ssl.trustStore=/path/to/truststore.jks) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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 September 2019