January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7840) elytron: authentication-context validation errors

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-7840?page=com.atlassian.jira.plugin.... ] Jan Kalina commented on WFLY-7840: ---------------------------------- After adding *setAllowNull(true)* into ObjectListAttributeDefinition declaration the attribute is optional correctly. Without it of with *setAllowNull(false)* it is required (correct), but read-resource-description gives incorrectly: {code} "match-rules" => { "required" => false, "nillable" => true, {code} which I consider kernel bug, [~brian.stansberry]. > elytron: authentication-context validation errors > ------------------------------------------------- > > Key: WFLY-7840 > URL: https://issues.jboss.org/browse/WFLY-7840 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Claudio Miranda > Assignee: Jan Kalina > > elytron resource authentication-context has attribute match-rules marked as required=false and nillable=true, but fail to add an authentication-context with no match-rules attribute > {code} > /profile=default/subsystem=elytron/authentication-context=test123:add > { > "outcome" => "failed", > "failure-description" => {"domain-failure-description" => "WFLYCTL0155: 'match-rules' may not be null"}, > "rolled-back" => true > } > {code} > Resource description snippet > {code} > "match-rules" => { > "type" => LIST, > "description" => "The match-rules for this authentication context.", > "expressions-allowed" => false, > "required" => false, > "nillable" => true, > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2023) Log viewer does not show any log file for rpm installation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2023?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-2023: --------------------------------------- [~baranowb] I closed this as I thought the PR was merged. However this looks like it might be for WildFly Core 2.x. Could you please update the JIRA to the expected version? I'm not certain what the target version is in this case. > Log viewer does not show any log file for rpm installation > ---------------------------------------------------------- > > Key: WFCORE-2023 > URL: https://issues.jboss.org/browse/WFCORE-2023 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Bartosz Baranowski > Assignee: James Perkins > Fix For: 3.0.0.Alpha13 > > > I'm running a fresh RHEL7.3 server subscribed to the current jboss eap7 repository [1] using the rpm package. [2] > [1] subscription-manager repos --enable=jb-eap-7-for-rhel-RHEL_VERSION-server-rpms > [2] https://access.redhat.com/documentation/en/red-hat-jboss-enterprise-appli... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6441) naming context is not setup when starting the persistence unit

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-6441?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-6441. ------------------------------ > naming context is not setup when starting the persistence unit > -------------------------------------------------------------- > > Key: WFLY-6441 > URL: https://issues.jboss.org/browse/WFLY-6441 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: JBoss AS7 7.1.1.Final, JBoss AS7 7.2.0.Final, 9.0.2.Final, 10.0.0.Final > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 10.1.0.CR1, 10.1.0.Final > > > ookup of env-entry throws NameNotFoundException during persistence unit startup > Version-Release number of selected component (if applicable): > How reproducible: > always > Steps to Reproduce: > 1. add env-entry in application.xml > 2. try to lookup during persistent unit startup, e.g. > public class MyType implements UserType { > ... > @Override > public int[] sqlTypes() { > try { > Object ctx = new InitialContext().lookup("java:app/env"); > log.info("java:app/env from JPA = " + ctx); > } catch (Exception e) { > log.error("unable to get java:app/env from JPA", e); > } > return new int[] { Types.VARCHAR }; > } > Actual results: > NameNotFoundException > Expected results: > value of env-entry is available > Additional info: > On 21.03.2016 23:47, Stuart Douglas wrote: > > This should fix it (I think): https://github.com/stuartwdouglas/wildfly/tree/jpa-java-namespace > > > > Stuart -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-363) ManagementResourceRegistration.getOverrideModel never returns null

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-363?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-363: ------------------------------------ Fix Version/s: (was: 3.0.0.Alpha18) > ManagementResourceRegistration.getOverrideModel never returns null > ------------------------------------------------------------------ > > Key: WFCORE-363 > URL: https://issues.jboss.org/browse/WFCORE-363 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > > ManagementResourceRegistration.getOverrideModel ends up returning the wildcard registration if there is no override registration. This isn't correct. > The fix isn't trivial because fixing it results in nasty failures in the smoke tests. From looking at the uses of this method (which all involve a null check) I assume there are some bugs in the code that calls this method that get exposed once it does what it should. > This bug is the cause of the initial failure of my WFLY-2880 fix. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1395) ClassCastException when adding a type declaration with incremental upgrade

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1395: ----------------------------------- Summary: ClassCastException when adding a type declaration with incremental upgrade Key: DROOLS-1395 URL: https://issues.jboss.org/browse/DROOLS-1395 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco The addition of a type declaration during an incremental compilation like the following: {code} declare OtherDummyEvent @role( event ) @timestamp( timestamp ) end {code} is not reflected in the existing knowledge base. For this reason also adding a new rule like this {code} rule "RG_TEST_2" when $event: DummyEvent () $other : OtherDummyEvent(id == $event.id, this after $event) then System.out.println("RG_TEST_2 fired"); retract($other); end {code} and inserting an OtherDummyEvent causes the following ClassCastException : {code} ClassCastException: org.drools.core.common.DefaultFactHandle cannot be cast to org.drools.core.common.EventFactHandle {code} because the instance of OtherDummyEvent is considered a fact instead of an event. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4311) Wildfly patching 8.1 to 8.2 does not update jackson to 2.4.1

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-4311?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-4311: -------------------------------------- Assignee: Alexey Loubyansky (was: Jason Greene) > Wildfly patching 8.1 to 8.2 does not update jackson to 2.4.1 > ------------------------------------------------------------ > > Key: WFLY-4311 > URL: https://issues.jboss.org/browse/WFLY-4311 > Project: WildFly > Issue Type: Bug > Components: Patching > Affects Versions: 8.2.0.Final > Reporter: Christian Beutenmüller > Assignee: Alexey Loubyansky > > Wildfly 8.2 final should update jackson-core, -annotation and -databind modules to 2.4.1, however when using the patch to upgrade an existing Wildfly 8.1 final to 8.2 the jackson libraries are not updated. > Steps to reproduce: > Download wildfly 8.1 distribution > unzip > Download wildfly 8.2 patch > apply patch using jboss-cli > check version in modules/system/layers/base/com/fasterxml/jackson/core/jackson-core/main > It should be 2.4.1 but it is still 2.3.2. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6222) Widlfy Deployments Admin UI screen hides last app when scrolling

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6222?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-6222: -------------------------------------- Component/s: Web Console Assignee: Harald Pehl (was: Jason Greene) > Widlfy Deployments Admin UI screen hides last app when scrolling > ---------------------------------------------------------------- > > Key: WFLY-6222 > URL: https://issues.jboss.org/browse/WFLY-6222 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 10.0.0.Final > Environment: Tested Chrome and Firefox > Reporter: Matthew Casperson > Assignee: Harald Pehl > Priority: Minor > Attachments: Screen Shot 2016-02-16 at 10.25.34 AM.png, Screen Shot 2016-02-16 at 10.33.08 AM.png > > > If you have a lot of applications, the Wildfly admin console will hide the last elements under the footer in Deployments -> Content Repository. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6226) Consider request body encoding when creating PartImpl

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-6226?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-6226: -------------------------------------- Component/s: Web (Undertow) Assignee: Stuart Douglas (was: Jason Greene) > Consider request body encoding when creating PartImpl > ----------------------------------------------------- > > Key: WFLY-6226 > URL: https://issues.jboss.org/browse/WFLY-6226 > Project: WildFly > Issue Type: Enhancement > Components: Web (Undertow) > Reporter: Bauke Scholtz > Assignee: Stuart Douglas > > When {{request.getCharacterEncoding()}} returns non-{{null}}, please consider it while creating {{PartImpl}} instead of falling back to {{<servlet-container name="default" default-encoding="UTF-8">}}. > Related Q&A: http://stackoverflow.com/q/35413585/157882 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2150) Improve error log on resolving interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2150?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-2150: ---------------------------------------- Component/s: Domain Management Assignee: (was: Jason Greene) > Improve error log on resolving interface > ---------------------------------------- > > Key: WFCORE-2150 > URL: https://issues.jboss.org/browse/WFCORE-2150 > Project: WildFly Core > Issue Type: Enhancement > Components: Domain Management > Reporter: Bartosz Baranowski > Attachments: server.log > > > If IP6 is being used, without IP6 stack enabled, WFLY will notify that "it cant resolve", as to why? No indication. > MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: WFLYSRV0082: failed to resolve interface public -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2150) Improve error log on resolving interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2150?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-6351 to WFCORE-2150: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2150 (was: WFLY-6351) > Improve error log on resolving interface > ---------------------------------------- > > Key: WFCORE-2150 > URL: https://issues.jboss.org/browse/WFCORE-2150 > Project: WildFly Core > Issue Type: Enhancement > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Attachments: server.log > > > If IP6 is being used, without IP6 stack enabled, WFLY will notify that "it cant resolve", as to why? No indication. > MSC000001: Failed to start service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: WFLYSRV0082: failed to resolve interface public -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 January 2017