June 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1631) newKieSession("rules") takes 2 minutes in 6.2.0.Final - takes 20 minutes in 6.5.0.Final and 7.0.0.Final

by Mark Langford (JIRA)

Mark Langford created DROOLS-1631: ------------------------------------- Summary: newKieSession("rules") takes 2 minutes in 6.2.0.Final - takes 20 minutes in 6.5.0.Final and 7.0.0.Final Key: DROOLS-1631 URL: https://issues.jboss.org/browse/DROOLS-1631 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.0.0.Final, 6.5.0.Final Reporter: Mark Langford Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-148) Support suppressed exceptions in log formatting

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-148?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on LOGMGR-148: ------------------------------------------------ Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1441890|https://bugzilla.redhat.com/show_bug.cgi?id=1441890] from VERIFIED to CLOSED > Support suppressed exceptions in log formatting > ----------------------------------------------- > > Key: LOGMGR-148 > URL: https://issues.jboss.org/browse/LOGMGR-148 > Project: JBoss Log Manager > Issue Type: Feature Request > Components: core > Reporter: David Lloyd > Assignee: James Perkins > Fix For: 1.5.7.Final > > > In JDK 7 and on, a Throwable bundles a list of suppressed exceptions. We should be logging these as part of our exception formatting... however we have to do so thoughtfully, because every caused-by and suppressed exception may in turn have more suppressed exceptions and caused-by. > This JIRA was created to track a back port of the JDK 7 enhancement to support suppressed exceptions to the 1.5.x branch which requires JDK 6. This will introduce a new requirement that the 1.5 branch will require JDK 7 to compile, but will still work on JDK 6. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2645) JMX interface should allow non-string values in the jboss.as.expr JMX domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2645?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2645: ------------------------------------- Fix Version/s: 4.0.0.Alpha1 > JMX interface should allow non-string values in the jboss.as.expr JMX domain > ---------------------------------------------------------------------------- > > Key: WFCORE-2645 > URL: https://issues.jboss.org/browse/WFCORE-2645 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 4.0.0.Alpha1 > > > Perhaps an enhancement, perhaps a bug. > TypeConverters.SimpleTypeConverter.toModelNode() is casting the value to String in the expression case (i.e. for jboss.as.expr). This means if the client sends a non-string, i.e. something in the type that would be normal in the jboss.as domain, e.g. Boolean, the call will fail with a class cast exception. > It seems like it would be easy enough to handle non-String. That would allow client code written for jboss.as to more easily deal with jboss.as.expr as well. Our testsuite's JmxManagementInterface client being the specific example that led me to file this. (My work on WFCORE-2633 was impacted when I wanted to use JmxManagementInterface to write a boolean value.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2954) Elytron sasl-authentication-factory does not offer mechanisms in configured order

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2954?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2954: ------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2571 (was: https://github.com/wildfly/wildfly-core/pull/2540) > Elytron sasl-authentication-factory does not offer mechanisms in configured order > --------------------------------------------------------------------------------- > > Key: WFCORE-2954 > URL: https://issues.jboss.org/browse/WFCORE-2954 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Blocker > Labels: eap71_priority > Fix For: 3.0.0.Beta27 > > > Application server does not offer SASL mechanisms in order defined in Elytron sasl-authentication-factory. See Steps to Reproduce for more details. > Screenshot from wireshark 'follow TCP stream' is attached. {{JBOSS-LOCAL-USER}} is offered before {{DIGEST-MD5}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2645) JMX interface should allow non-string values in the jboss.as.expr JMX domain

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2645?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2645: ---------------------------------------- Assignee: Brian Stansberry > JMX interface should allow non-string values in the jboss.as.expr JMX domain > ---------------------------------------------------------------------------- > > Key: WFCORE-2645 > URL: https://issues.jboss.org/browse/WFCORE-2645 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management, JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Perhaps an enhancement, perhaps a bug. > TypeConverters.SimpleTypeConverter.toModelNode() is casting the value to String in the expression case (i.e. for jboss.as.expr). This means if the client sends a non-string, i.e. something in the type that would be normal in the jboss.as domain, e.g. Boolean, the call will fail with a class cast exception. > It seems like it would be easy enough to handle non-String. That would allow client code written for jboss.as to more easily deal with jboss.as.expr as well. Our testsuite's JmxManagementInterface client being the specific example that led me to file this. (My work on WFCORE-2633 was impacted when I wanted to use JmxManagementInterface to write a boolean value.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1897) Follow up WFCORE-296 once migrated to Remoting 5

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1897?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1897: ------------------------------------- Fix Version/s: 3.0.0.Beta28 (was: 3.0.0.Beta27) > Follow up WFCORE-296 once migrated to Remoting 5 > ------------------------------------------------ > > Key: WFCORE-1897 > URL: https://issues.jboss.org/browse/WFCORE-1897 > Project: WildFly Core > Issue Type: Task > Components: Remoting > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta28 > > > WFCORE-296 adds support for the schemes remote:// remote_http:// and remote+https:// - once we switch to centralised Endpoints we need to ensure this new set is still supported along with the previous set. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1282) Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1282?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1282: ------------------------------------- Fix Version/s: 3.0.0.Beta28 (was: 3.0.0.Beta27) > Unable to create HTTPS connection using *ECDH_RSA* cipher suites / kECDHr cipher string > --------------------------------------------------------------------------------------- > > Key: WFCORE-1282 > URL: https://issues.jboss.org/browse/WFCORE-1282 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 1.0.2.Final > Environment: Oracle Java > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 3.0.0.Beta28 > > Attachments: client_debug_eap6.log, client_debug_eap7.log, server-cert-key-ec.jks, server_debug_eap6.log, server_debug_eap7.log > > > User using these cipher suites / cipher name in EAP6 won't be able to use it in EAP7. > Setting as critical as these cipher suites, are considered for strong and widely used in my opinion. > In server log, error "no cipher suites in common" can be seen using -Djavax.net.debug=all. > Note, that analogous configuration in EAP6 works fine. > Issue can be seen on Oracle Java only, as on OpenJDK / IBM these suites are not provided by method getDefaultCipherSuites(). > Also is it possible to log "no cipher suites in common" and similar tls handshake errors without -Djavax.net.debug for better troubleshooting? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-887) "Deprecate" using an expression in model refs to interfaces

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-887?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-887: ------------------------------------ Fix Version/s: 3.0.0.Beta28 (was: 3.0.0.Beta27) > "Deprecate" using an expression in model refs to interfaces > ----------------------------------------------------------- > > Key: WFCORE-887 > URL: https://issues.jboss.org/browse/WFCORE-887 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 3.0.0.Beta28 > > > SocketBindingGroupResourceDefinition and OutboundSocketBindingResourceDefinition both have attributes that represent model refs to interface resources, but which also allow expressions. > Model references should not allow expressions. These were "grandfathered in" when the large scale expression support roll out happened for AS 7.2 / EAP 6.1. > There's no metadata facility to record that expression support is deprecated, but the add handler for these should log a WARN if they encounter an expression. Hopefully in EAP 8 we can then remove expression support. > We should look for other cases like this too, although those changes should be separate JIRAs. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2882) Review & fix xml persistence of elytron subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2882?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2882: ------------------------------------- Fix Version/s: 3.0.0.Beta28 (was: 3.0.0.Beta27) > Review & fix xml persistence of elytron subsystem > ------------------------------------------------- > > Key: WFCORE-2882 > URL: https://issues.jboss.org/browse/WFCORE-2882 > Project: WildFly Core > Issue Type: Task > Components: Domain Management, Security > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 3.0.0.Beta28 > > > Elytron subsystem uses a mess of parsers and duplicate code in them. > Go trough all parsers and unify attribute persistence with rest of the server. > also get rid as much of custom parser code as possible. > Update XSDs where appropriate to follow common model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2609) CLIRolloutPlanTestCase hang

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2609?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2609: ------------------------------------- Fix Version/s: 3.0.0.Beta28 (was: 3.0.0.Beta27) > CLIRolloutPlanTestCase hang > --------------------------- > > Key: WFCORE-2609 > URL: https://issues.jboss.org/browse/WFCORE-2609 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Test Suite > Reporter: Brian Stansberry > Priority: Critical > Fix For: 3.0.0.Beta28 > > Attachments: WFCORE-2609_threads.txt > > > Hang: > https://ci.wildfly.org/viewLog.html?buildId=53176&buildTypeId=WF_MasterWi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 2017