December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3478) Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3478?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3478: ------------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3006) > Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3478 > URL: https://issues.jboss.org/browse/WFCORE-3478 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > AttributeDefinition and AbstractAttributeDefinitionBuilder in the controller module have some fields that are protected. This will make it problematic to evolve the management code in the future. Remove all direct use of these, switching to getters instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9632) Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9632?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-3478 to WFLY-9632: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-9632 (was: WFCORE-3478) Component/s: Domain Management (was: Domain Management) > Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields > -------------------------------------------------------------------------------------------- > > Key: WFLY-9632 > URL: https://issues.jboss.org/browse/WFLY-9632 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > AttributeDefinition and AbstractAttributeDefinitionBuilder in the controller module have some fields that are protected. This will make it problematic to evolve the management code in the future. Remove all direct use of these, switching to getters instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3478) Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3478?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-3478: ------------------------------------- Summary: Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields (was: Tighten visibility on some AttributeDefinition fields) > Tighten visibility on some AttributeDefinition and AbstractAttributeDefinitionBuilder fields > -------------------------------------------------------------------------------------------- > > Key: WFCORE-3478 > URL: https://issues.jboss.org/browse/WFCORE-3478 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > AttributeDefinition and some subclasses in the controller module have some fields that are not private. This will make it problematic to evolve the management code in the future. Deprecate any that are protected, with a note to use the getter, and make package protected ones private. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3478) Tighten visibility on some AttributeDefinition fields

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3478: ---------------------------------------- Summary: Tighten visibility on some AttributeDefinition fields Key: WFCORE-3478 URL: https://issues.jboss.org/browse/WFCORE-3478 Project: WildFly Core Issue Type: Task Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor AttributeDefinition and some subclasses in the controller module have some fields that are not private. This will make it problematic to evolve the management code in the future. Deprecate any that are protected, with a note to use the getter, and make package protected ones private. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2243) Provide a protocol to inject arbitrary view on nodes

by andrea tarocchi (JIRA)

andrea tarocchi created JGRP-2243: ------------------------------------- Summary: Provide a protocol to inject arbitrary view on nodes Key: JGRP-2243 URL: https://issues.jboss.org/browse/JGRP-2243 Project: JGroups Issue Type: Enhancement Reporter: andrea tarocchi Assignee: Bela Ban -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9610) Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution

by Serg Pol (JIRA)

[ https://issues.jboss.org/browse/WFLY-9610?page=com.atlassian.jira.plugin.... ] Serg Pol commented on WFLY-9610: -------------------------------- Thank You very much. (y) Marry Christmas and Happy New Year! p.s. i had impression in this case that the number of batch jobs that run in the same time was less as configured max number(10) > Start of a BatchJob is called, but BatchJob is seems no started. Absent entries in DB tables step_execution, job_execution > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9610 > URL: https://issues.jboss.org/browse/WFLY-9610 > Project: WildFly > Issue Type: Bug > Components: Batch > Affects Versions: 9.0.1.Final > Environment: Cluster, standalone-full-ha > Reporter: Serg Pol > Assignee: Cheng Fang > > Start of a BatchJob is called and record/entry is absent sometimes in DB table "step_execution" as well as Endtime and Exitstatus in the table job_execution (there is just info about start of BatchJob). > There are no any error nessages. > BatchJob is not started in this case according Log. > Any idea? Thanks -- 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 edited comment on ELY-1472 at 12/21/17 1:20 PM: ----------------------------------------------------------- Look like {{cb->initiator_address.length}} is not initialized in {{GSSLibStub.c}} in OpenJDK: {code} cb->initiator_address.length = 140608975239744 (should be 0?) cb->acceptor_address.length = 0 {code} => wrong channel binding checksum in kg_checksum_channel_bindings in util_cksum.c in krb5 was (Author: honza889): Look like {{cb->initiator_address.length}} is not initialized in {{GSSLibStub.c}} in OpenJDK: {code} cb->initiator_address.length = 140608975239744 (should be 0?) cb->acceptor_address.length = 0 {code} > [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-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 commented on ELY-1472: --------------------------------- Look like {{cb->initiator_address.length}} is not initialized in {{GSSLibStub.c}} in OpenJDK: {code} cb->initiator_address.length = 140608975239744 (should be 0?) cb->acceptor_address.length = 0 {code} > [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-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 commented on ELY-1472: --------------------------------- Edit: by RFC the GSS-CHANNEL-BINDINGS Structure must be used even when negotiated application level channel binding is unsupported (gs2-cb-flag=n) - need to investigate more... > [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-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 updated ELY-1472: ---------------------------- Comment: was deleted (was: If the setChannelBinding really should not be used, maybe this can resolve also ELY-1331 ...) > [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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017