December 2017 - jboss-jira - Jboss List Archives

[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 edited comment on ELY-283 at 12/6/17 8:41 AM: --------------------------------------------------------- Few notes: * property *sun.security.jgss.native* needs to be set using JAVA_OPTS="-D ..." before standalone.sh (setting in standalone.xml is applied to late and is ignored by JVM) * to debug SunNativeProvider add property: *sun.security.nativegss.debug=true* * currently Elytron initialize LoginContext/Krb5LoginModule even if native provider should be used - should be made optional for future, but for now there is need to provide keystore with given credential to continue (obtained credential should be ignored by GSSManager if correctly set) * Currently gssproxy supports krb5 only to have filled in mechs in gssproxy.conf - we are unable to put SPNEGO here - cannot be used for SPNEGO HTTP auth * To start: {code}GSSPROXY_BEHAVIOR=REMOTE_FIRST GSS_USE_PROXY=1 JAVA_OPTS="-Djavax.security.auth.useSubjectCredsOnly=false -Dsun.security.jgss.lib=/usr/lib64/libgssapi_krb5.so.2.2 -Dsun.security.jgss.native=true -Dsun.security.nativegss.debug=true -Dsun.security.krb5.debug=true -Dsun.security.jgss.debug=true" bin/standalone.sh{code} was (Author: honza889): Few notes: * property *sun.security.jgss.native* needs to be set using JAVA_OPTS="-D ..." before standalone.sh (setting in standalone.xml is applied to late and is ignored by JVM) * to debug SunNativeProvider add property: *sun.security.nativegss.debug=true* * currently Elytron initialize LoginContext/Krb5LoginModule even if native provider should be used - should be made optional for future, but for now there is need to provide keystore with given credential to continue (obtained credential should be ignored by GSSManager if correctly set) * To start: {code}GSSPROXY_BEHAVIOR=REMOTE_FIRST GSS_USE_PROXY=1 JAVA_OPTS="-Djavax.security.auth.useSubjectCredsOnly=false -Dsun.security.jgss.lib=/usr/lib64/libgssapi_krb5.so.2.2 -Dsun.security.jgss.native=true -Dsun.security.nativegss.debug=true -Dsun.security.krb5.debug=true -Dsun.security.jgss.debug=true" bin/standalone.sh{code} > 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 > > > Investigate Elytron and gssproxy interoperability. > https://fedorahosted.org/gss-proxy/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9593) Add clustering externalizers for InetAddress and InetSocketAddress

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9593?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-9593: ------------------------------- Issue Type: Enhancement (was: Feature Request) > Add clustering externalizers for InetAddress and InetSocketAddress > ------------------------------------------------------------------ > > Key: WFLY-9593 > URL: https://issues.jboss.org/browse/WFLY-9593 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > InetAddress can be marshalled as a fixed sized array depending on whether the address is IPv4 or IPv6, which can be determined by the implementation class. > InetSocketAddress can marshal its address using the InetAddress externalizer, and its port as an unsigned short. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9509) Default SFSB Lifecycle methods transaction attribute causing warnings

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-9509?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-9509: ----------------------------------------------- Aurel Pintea <apintea(a)redhat.com> changed the Status of [bug 1508105|https://bugzilla.redhat.com/show_bug.cgi?id=1508105] from MODIFIED to ON_QA > Default SFSB Lifecycle methods transaction attribute causing warnings > --------------------------------------------------------------------- > > Key: WFLY-9509 > URL: https://issues.jboss.org/browse/WFLY-9509 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Brad Maxwell > Assignee: Brad Maxwell > Fix For: 12.0.0.Alpha1 > > Attachments: warning-reproducer.zip > > > EJB 2 deployment that does not specify transaction attribute for lifecycle methods such as: ejbActivate, ejbRemove, ejbPassivate are logging this warning. > JBAS014279: Invalid transaction attribute type REQUIRED on SFSB lifecyle method Method ejbRemove(), valid types are REQUIRES_NEW and NOT_SUPPORTED. Method will be treated as NOT_SUPPORTED. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-212) Automation Testcase

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created HAWKULARQE-212: ----------------------------------------- Summary: Automation Testcase Key: HAWKULARQE-212 URL: https://issues.jboss.org/browse/HAWKULARQE-212 Project: Hawkular QE Issue Type: Sub-task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Tomas Kraus (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Tomas Kraus commented on WFLY-8954: ----------------------------------- I made changes to implement JTA 1.1 TransactionSynchronizationRegistry in EclipseLink master branch, see https://bugs.eclipse.org/bugs/show_bug.cgi?id=526419 for details. It would be good if you can test next http://www.eclipse.org/eclipselink/downloads/nightly.php (7th dec 2017 and later) and give us feedback. Also, if we'll make backport into 2.7. and 2.6 branches, you can base your changes on extending org.eclipse.persistence.transaction.JTA11TransactionController class instead of current JTATransactionController. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > Fix For: 12.0.0.Alpha1 > > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Description: For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. > Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing > ---------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > > For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9572: --------------------------------- Description: Tracking issue for speeding up clustering testsuite. > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > > Tracking issue for speeding up clustering testsuite. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9572) Speed-up clustering testsuite

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9572?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9572: --------------------------------- Description: (was: For starters, move the testsuite away from using XSLT and just rely on the CLI scripts. ) > Speed-up clustering testsuite > ----------------------------- > > Key: WFLY-9572 > URL: https://issues.jboss.org/browse/WFLY-9572 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Affects Version/s: 11.0.0.Final > Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing > ---------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9598) Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9598?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9598: --------------------------------- Fix Version/s: 12.0.0.Alpha1 > Clustering Testsuite 2.0: no ant, CLI, 3-node DIST testing > ---------------------------------------------------------- > > Key: WFLY-9598 > URL: https://issues.jboss.org/browse/WFLY-9598 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Critical > Fix For: 12.0.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 December 2017