December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3481) Remove uses of "new OperationFailedException(ModelNode)"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3481?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-9638 to WFCORE-3481: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-3481 (was: WFLY-9638) Component/s: Domain Management (was: Domain Management) > Remove uses of "new OperationFailedException(ModelNode)" > -------------------------------------------------------- > > Key: WFCORE-3481 > URL: https://issues.jboss.org/browse/WFCORE-3481 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Constructor is deprecated; remove use of it so we can eventually drop it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3481) Remove uses of "new OperationFailedException(ModelNode)"

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3481?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3481: ------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/10731) > Remove uses of "new OperationFailedException(ModelNode)" > -------------------------------------------------------- > > Key: WFCORE-3481 > URL: https://issues.jboss.org/browse/WFCORE-3481 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Constructor is deprecated; remove use of it so we can eventually drop it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9637) Remove uses of "new OperationFailedException(ModelNode)"

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9637: -------------------------------------- Summary: Remove uses of "new OperationFailedException(ModelNode)" Key: WFLY-9637 URL: https://issues.jboss.org/browse/WFLY-9637 Project: WildFly Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Constructor is deprecated; remove use of it so we can eventually drop it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2199) Rule units are executed in reverse order when a consequence calls a sequence of drools.run(unit)

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2199?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-2199. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/a1d778bcb93658f98ab0bac10a520dc... > Rule units are executed in reverse order when a consequence calls a sequence of drools.run(unit) > ------------------------------------------------------------------------------------------------ > > Key: DROOLS-2199 > URL: https://issues.jboss.org/browse/DROOLS-2199 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2199) Rule units are executed in reverse order when a consequence calls a sequence of drools.run(unit)

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2199: ----------------------------------- Summary: Rule units are executed in reverse order when a consequence calls a sequence of drools.run(unit) Key: DROOLS-2199 URL: https://issues.jboss.org/browse/DROOLS-2199 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-1472) [native kerberos] setting channelBinding of gssContext when not used

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1472?page=com.atlassian.jira.plugin.s... ] Jan Kalina closed ELY-1472. --------------------------- Resolution: Rejected Fixing patch of JDK in ELY-283: https://issues.jboss.org/secure/attachment/12429366/jkalina-openjdk-nativ... Closing this, as this is not Elytron issue actually. > [native kerberos] setting channelBinding of gssContext when not used > -------------------------------------------------------------------- > > Key: ELY-1472 > URL: https://issues.jboss.org/browse/ELY-1472 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Affects Versions: 1.2.0.Beta11 > Reporter: Jan Kalina > Assignee: Jan Kalina > Labels: kerberos > > Gs2SaslServer: gssContext's channelBinding setting leads to error when native Kerberos is used. > This lead to following error when using native Kerberos library: > {code} > [GSSLibStub_acceptContext] before2: pCred=35810112, pContext=0 > [GSSLibStub_acceptContext] before3: inToken.length=515 > [GSSLibStub_acceptContext] after: pCred=35810112, pContext=0, pDelegCred=0 > [GSSLibStub_acceptContext] after2: major=262144, GSS_ERROR(major)=262144 minor=12 > [GSSLibStub_acceptContext] acceptSecContext JK Status major/minor = 40000/12 > c/r/s = 0/4/0 > {code} > Which mean routine error 4 has occurred, which is GSS_S_BAD_BINDINGS - Incorrect channel bindings were supplied. > This is fixed when I change cb (in native) to GSS_C_NO_CHANNEL_BINDINGS - equivalent of setting null into channelBinding in gssContext. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-283: -------------------------------- For needs of OpenJDK patch review I has prepared simple reproducer without AS: [^reproducer-gss.zip] {panel} Hi, I was just able to prepare usable reproducer (attaching in ZIP file) and fixing patch of JDK (attaching too). Before I was able to make my usecase working, I has found second issue too - I has included it too. Issues and their reproducing: *1) already described problem of wrong initialized SunNativeProvider.INSTANCE* This can be reproduced by recreating GSSManager before createGSSContext - ProviderList.factories will be initialized as part of initSecContext/acceptSecContext which will cause using wrong initialized SunNativeProvider.INSTANCE and described exception. *2) when channel binding is used SIGSEGV occure* This can be reproduced by setting channel binding without initAddr/acceptAddr. This is caused by sending uninitialized (with random length) cb->initiator_address from JDK to the kerberos. (It is used by krb library for messages checksum calculation even when addrtype is GSS_C_AF_NULLADDR.) Attached reproducer-gss.zip reproduces both issues and attached patch fixes both. I would welcome merging into OpenJDK. (I am covered by OCA of Red Hat) This issue affect both tested JDKs, JKD8u121 and upstream JDK9 from mercurial master. Thanks, Jan {panel} > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: jkalina-openjdk-native-gss.patch, openjdk-patch-native-mechs.patch, reproducer-gss.zip > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-283) Investigate Elytron and gssproxy interoperability

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-283?page=com.atlassian.jira.plugin.sy... ] Jan Kalina updated ELY-283: --------------------------- Attachment: reproducer-gss.zip > Investigate Elytron and gssproxy interoperability > ------------------------------------------------- > > Key: ELY-283 > URL: https://issues.jboss.org/browse/ELY-283 > Project: WildFly Elytron > Issue Type: Task > Components: SASL > Reporter: Peter Skopek > Assignee: Jan Kalina > Fix For: 2.0.0.Alpha1 > > Attachments: jkalina-openjdk-native-gss.patch, openjdk-patch-native-mechs.patch, reproducer-gss.zip > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9636) EJB lookup over HTTP times out connection after 60 seconds

by peter craddock (JIRA)

peter craddock created WFLY-9636: ------------------------------------ Summary: EJB lookup over HTTP times out connection after 60 seconds Key: WFLY-9636 URL: https://issues.jboss.org/browse/WFLY-9636 Project: WildFly Issue Type: Bug Components: EJB, IO, Naming Affects Versions: 11.0.0.Final Environment: I work with https://developer.jboss.org/people/jaikiran on https://developer.jboss.org/thread/276635 so my Wildfly 11 environment has this fix in it. Reporter: peter craddock The code examples and trace logging can be found here https://developer.jboss.org/thread/276840 I have work round the problem but was asked to raise it for further investigation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2198) [GSS](6.4.z) When a declared type is modified during an incremental compilation the old version isn't evicted from the TypeResolver cache

by Martin Weiler (JIRA)

Martin Weiler created DROOLS-2198: ------------------------------------- Summary: [GSS](6.4.z) When a declared type is modified during an incremental compilation the old version isn't evicted from the TypeResolver cache Key: DROOLS-2198 URL: https://issues.jboss.org/browse/DROOLS-2198 Project: Drools Issue Type: Bug Components: core engine Reporter: Martin Weiler Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017