May 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-680) No log messages comming from Elytron - kerberos

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-680?page=com.atlassian.jira.plugin.sy... ] Jan Kalina commented on ELY-680: -------------------------------- Improved in second PR. > No log messages comming from Elytron - kerberos > ----------------------------------------------- > > Key: ELY-680 > URL: https://issues.jboss.org/browse/ELY-680 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Reporter: Martin Choma > Assignee: Jan Kalina > Priority: Critical > > Elytron is missing log messages related to kerberos authentication. These log messages should be added. See JBEAP-6041 for more details. > I consider to be useful to have TRACE log messages at least in: > - SpnegoAuthenticationMechanism > - GSSCredentialSecurityFactory > If there are more classes involved in kerberos authnetication include them as well. > Kerberos issues are very specific. So it is very important to have as much trace information as possible. Therefore raising priority to Critical. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2160) Incorrect JBOSS_HOME warning in vault.sh

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2160?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2160: ------------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1410924|https://bugzilla.redhat.com/show_bug.cgi?id=1410924] from POST to MODIFIED > Incorrect JBOSS_HOME warning in vault.sh > ---------------------------------------- > > Key: WFCORE-2160 > URL: https://issues.jboss.org/browse/WFCORE-2160 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 3.0.0.Alpha16 > Reporter: Dennis Reed > Assignee: Romain Pelisse > Priority: Minor > Fix For: 3.0.0.Alpha23 > > > vault.sh has an incorrect check to make sure JBOSS_HOME is set correctly. > SANITIZED_JBOSS_HOME=`cd "$JBOSS_HOME/.."; pwd` > if [ "$RESOLVED_JBOSS" != "$SANITIZED_JBOSS_HOME" ]; then > The check will always fail because of the incorrect "/..", which should be removed. > The incorrect value is only used for printing the "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." log, and appears to have been around since at least EAP 6.0. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8631) Integration test for WFCORE-2647 Add an option to always send the client SSL certificate to LDAP server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-8631?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-8631: ----------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1327758|https://bugzilla.redhat.com/show_bug.cgi?id=1327758] from POST to MODIFIED > Integration test for WFCORE-2647 Add an option to always send the client SSL certificate to LDAP server > ------------------------------------------------------------------------------------------------------- > > Key: WFLY-8631 > URL: https://issues.jboss.org/browse/WFLY-8631 > Project: WildFly > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 11.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2647) Add an option to always send the client SSL certificate to LDAP server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2647?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-2647: ------------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1327758|https://bugzilla.redhat.com/show_bug.cgi?id=1327758] from POST to MODIFIED > Add an option to always send the client SSL certificate to LDAP server > ---------------------------------------------------------------------- > > Key: WFCORE-2647 > URL: https://issues.jboss.org/browse/WFCORE-2647 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.0.0.Beta18 > > > This is the component issue for https://issues.jboss.org/browse/JBEAP-4439 and https://bugzilla.redhat.com/show_bug.cgi?id=1327758 > The present code in {{LdapConnectionManagerService}} was designed so that the client cert is sent to authenticate the search account but during the username / password verification step, the client cert is not sent. > The present objective is to add an option (that will default to the old behavior) to send the client password also during the username / password verification. > This includes (citing [~dlofthouse]): > * Implement management model based configuration and an implementation for the current version > * Port back to older versions using a system property. > * Forward port the system property to the current version for compatibility. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2876) runtime-failure-causes-rollback does not seem to have effect when configured in model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2876?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFCORE-2876 at 5/30/17 2:20 PM: ------------------------------------------------------------------- The WFLY-1305 fix added the undeploy cleanup task and the WFLY-364 feature done at roughly the same time didn't account for it. was (Author: brian.stansberry): The WFLY-1305 fix added the undeploy cleanup task and the WFLY-264 feature done at roughly the same time didn't account for it. > runtime-failure-causes-rollback does not seem to have effect when configured in model > ------------------------------------------------------------------------------------- > > Key: WFCORE-2876 > URL: https://issues.jboss.org/browse/WFCORE-2876 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 3.0.0.Beta21 > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > > This is follow up on discussion in WFCORE-1912. There is difference in behavior if deployment is deployed like: > {code}deploy ~/tmp/mdb1.jar --unmanaged --headers={rollback-on-runtime-failure=false}{code} > and if it's deployed by copying to deployments directory and setting {{rollback-on-runtime-failure=false}} in model: > {code} > /subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback,value=false) > {code} > If it's deployed by the 1st way using CLI {{deploy}} command then If deployment is missing some dependencies (like connection factories, queues/topics) and those are added later then deployment is able recover from it and start working without need to reload/restart server or redeploy. > However if it's deployed the 2nd way then deployment does not recover when missing dependencies are added. It looks like attribute {{runtime-failure-causes-rollback}} does not have the effect in this case. > This is causing problems when Artemis is configured in colocated HA topology with replicated journal where it takes some time for Artemis to activate but deployment which depends on some connection factories and queues has already tried to deploy. We need deployment to recover from this situation automatically. Restart/Reload will not help in this case as it would end up in the same situation. Only manual redeploy will help which is a workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2876) runtime-failure-causes-rollback does not seem to have effect when configured in model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2876?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2876: ------------------------------------------ The WFLY-1305 fix added the undeploy cleanup task and the WFLY-264 feature done at roughly the same time didn't account for it. > runtime-failure-causes-rollback does not seem to have effect when configured in model > ------------------------------------------------------------------------------------- > > Key: WFCORE-2876 > URL: https://issues.jboss.org/browse/WFCORE-2876 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 3.0.0.Beta21 > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > > This is follow up on discussion in WFCORE-1912. There is difference in behavior if deployment is deployed like: > {code}deploy ~/tmp/mdb1.jar --unmanaged --headers={rollback-on-runtime-failure=false}{code} > and if it's deployed by copying to deployments directory and setting {{rollback-on-runtime-failure=false}} in model: > {code} > /subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback,value=false) > {code} > If it's deployed by the 1st way using CLI {{deploy}} command then If deployment is missing some dependencies (like connection factories, queues/topics) and those are added later then deployment is able recover from it and start working without need to reload/restart server or redeploy. > However if it's deployed the 2nd way then deployment does not recover when missing dependencies are added. It looks like attribute {{runtime-failure-causes-rollback}} does not have the effect in this case. > This is causing problems when Artemis is configured in colocated HA topology with replicated journal where it takes some time for Artemis to activate but deployment which depends on some connection factories and queues has already tried to deploy. We need deployment to recover from this situation automatically. Restart/Reload will not help in this case as it would end up in the same situation. Only manual redeploy will help which is a workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5627) Unable to view the infinispan statistics from CLI

by PEANO LUCA (JIRA)

[ https://issues.jboss.org/browse/WFLY-5627?page=com.atlassian.jira.plugin.... ] PEANO LUCA commented on WFLY-5627: ---------------------------------- and witch cash is used? > Unable to view the infinispan statistics from CLI > ------------------------------------------------- > > Key: WFLY-5627 > URL: https://issues.jboss.org/browse/WFLY-5627 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Chao Wang > Assignee: Paul Ferraro > > When I investigated https://bugzilla.redhat.com/show_bug.cgi?id=1276441 and tested its scenario with WildFly as: > {noformat} > Steps to Reproduce: > =================== > 1) Build latest Wildfly master and consider `standalone-ha.xml` file. > 2) Enable the infinispan statistics in the standalone-ha.xml file. > Configuration looks as below: > ----- > <subsystem xmlns="urn:jboss:domain:infinispan:4.0"> > <cache-container name="server" aliases="singleton cluster" module="org.wildfly.clustering.server" default-cache="default"> > <transport lock-timeout="60000"/> > <replicated-cache name="default" mode="SYNC"> > <transaction mode="BATCH"/> > </replicated-cache> > </cache-container> > <cache-container name="web" module="org.wildfly.clustering.web.infinispan" default-cache="dist" statistics-enabled="true"> > <transport lock-timeout="60000"/> > <distributed-cache name="dist" statistics-enabled="true" mode="ASYNC" l1-lifespan="0" owners="2"> > <locking isolation="REPEATABLE_READ"/> > <transaction mode="BATCH"/> > <file-store/> > </distributed-cache> > </cache-container> > ----- > 3) Start the server with `standalone-ha.xml` file. > 4) Deploy the cluster web application and hit the application. > 5) and check the infinispan statistics by using the below cli command: > ----- > /subsystem=infinispan/cache-container=web/distributed-cache=dist:read-resource(include-runtime=true) > ----- > 6) Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never change. > Actual results: > =============== > - Values for the runtime parameters(i.e.,number-of-entries, hits, etc.,) never changed. > Expected results: > ================= > - There should be a change in the runtime parameters values. > Additional info: > ================= > - I can see the expected result from the jconsole statistics. > jconsole -> mbean tab -> jboss.infinispan -> Cache -> $application -> web -> Statistics. > {noformat} > It actually works fine with 10.0.0.CR4, but it breaks in latest master. It seems commit https://github.com/wildfly/wildfly/commit/79b49a3b930fd5c7cc29e9fe1c9a747... makes such difference. Once I revert this commit, I can see dynamic statistics change in CLI operation. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2876) runtime-failure-causes-rollback does not seem to have effect when configured in model

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2876?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet commented on WFCORE-2876: ------------------------------------------- Ok, this is due to the fact that the deployment failed on boot. Because of that FileSystemDeploymentService.forcedUndeployScan is executed when boot finishes and undeploy the failed deployments. > runtime-failure-causes-rollback does not seem to have effect when configured in model > ------------------------------------------------------------------------------------- > > Key: WFCORE-2876 > URL: https://issues.jboss.org/browse/WFCORE-2876 > Project: WildFly Core > Issue Type: Bug > Components: Deployment Scanner > Affects Versions: 3.0.0.Beta21 > Reporter: Miroslav Novak > Assignee: ehsavoie Hugonnet > > This is follow up on discussion in WFCORE-1912. There is difference in behavior if deployment is deployed like: > {code}deploy ~/tmp/mdb1.jar --unmanaged --headers={rollback-on-runtime-failure=false}{code} > and if it's deployed by copying to deployments directory and setting {{rollback-on-runtime-failure=false}} in model: > {code} > /subsystem=deployment-scanner/scanner=default:write-attribute(name=runtime-failure-causes-rollback,value=false) > {code} > If it's deployed by the 1st way using CLI {{deploy}} command then If deployment is missing some dependencies (like connection factories, queues/topics) and those are added later then deployment is able recover from it and start working without need to reload/restart server or redeploy. > However if it's deployed the 2nd way then deployment does not recover when missing dependencies are added. It looks like attribute {{runtime-failure-causes-rollback}} does not have the effect in this case. > This is causing problems when Artemis is configured in colocated HA topology with replicated journal where it takes some time for Artemis to activate but deployment which depends on some connection factories and queues has already tried to deploy. We need deployment to recover from this situation automatically. Restart/Reload will not help in this case as it would end up in the same situation. Only manual redeploy will help which is a workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-1211) FileAuditEndpoint doesn't allow for file encoding to be overridden

by James Perkins (JIRA)

James Perkins created ELY-1211: ---------------------------------- Summary: FileAuditEndpoint doesn't allow for file encoding to be overridden Key: ELY-1211 URL: https://issues.jboss.org/browse/ELY-1211 Project: WildFly Elytron Issue Type: Enhancement Reporter: James Perkins Assignee: Darran Lofthouse The {{FileAuditEndpoint}} doesn't allow for the file encoding to be overridden. It should likely allow the encoding to be overridden or at the very least specify {{UTF-8}} as the default. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ELY-950) Add local audit log rotation

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/ELY-950?page=com.atlassian.jira.plugin.sy... ] James Perkins commented on ELY-950: ----------------------------------- Will this be solved by the changes in ELY-1206? > Add local audit log rotation > ---------------------------- > > Key: ELY-950 > URL: https://issues.jboss.org/browse/ELY-950 > Project: WildFly Elytron > Issue Type: Task > Components: Audit > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta50 > > > Could be by time, size, rotate on start-up or a combination. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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