February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-7885) Persistent calendar timer force logging for each invocation if the deployed-class has changed

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/WFLY-7885?page=com.atlassian.jira.plugin.... ] Ingo Weiss reassigned WFLY-7885: -------------------------------- Assignee: Ingo Weiss > Persistent calendar timer force logging for each invocation if the deployed-class has changed > --------------------------------------------------------------------------------------------- > > Key: WFLY-7885 > URL: https://issues.jboss.org/browse/WFLY-7885 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Ingo Weiss > Priority: Minor > Labels: ejb, ejb3.1, timers, timerservice > > It will be common to change classes which contains @Schedule timer methods. > In case such methods are removed or renamed (for persistent calendar timers) the server will log the following warning forever for each invocation. > WARN [org.jboss.as.ejb3.timer] (EJB default - 1) WFLYEJB0161: Failed to reinstate timer 'ejb31-timer.ejb31-timer.SimpleScheduleSingletonTimerBean' (id=1a419372-d807-43d8-ac77-5be6696b022d) from its persistent state > As this is intentional there should be a WARN message at (first) deployment time and the timer should be removed from the persistence. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-914) Elytron LdapSearch is not able to log arrays correctly

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-914: -------------------------------- Summary: Elytron LdapSearch is not able to log arrays correctly Key: ELY-914 URL: https://issues.jboss.org/browse/ELY-914 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse In case when log debug level for class {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm.LdapSearch}} is enabled, then arguments and returning attributes are not able to be logged correctly because they are arrays. See: {code} Executing search [(uid={0})] in context [ou=People,dc=jboss,dc=org] with arguments [[Ljava.lang.String;@45535736]. Returning attributes are [[Ljava.lang.String;@331d3f34] {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-914) Elytron LdapSearch is not able to log arrays correctly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-914?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-914: ----------------------------- Component/s: Realms > Elytron LdapSearch is not able to log arrays correctly > ------------------------------------------------------ > > Key: ELY-914 > URL: https://issues.jboss.org/browse/ELY-914 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when log debug level for class {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm.LdapSearch}} is enabled, then arguments and returning attributes are not able to be logged correctly because they are arrays. > See: > {code} > Executing search [(uid={0})] in context [ou=People,dc=jboss,dc=org] with arguments [[Ljava.lang.String;@45535736]. Returning attributes are [[Ljava.lang.String;@331d3f34] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-914) Elytron LdapSearch is not able to log arrays correctly

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-914?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-914: ----------------------------- Affects Version/s: 1.1.0.Beta21 > Elytron LdapSearch is not able to log arrays correctly > ------------------------------------------------------ > > Key: ELY-914 > URL: https://issues.jboss.org/browse/ELY-914 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > > In case when log debug level for class {{org.wildfly.security.auth.realm.ldap.LdapSecurityRealm.LdapSearch}} is enabled, then arguments and returning attributes are not able to be logged correctly because they are arrays. > See: > {code} > Executing search [(uid={0})] in context [ou=People,dc=jboss,dc=org] with arguments [[Ljava.lang.String;@45535736]. Returning attributes are [[Ljava.lang.String;@331d3f34] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-913) Incorrect username is passed to principal when principal-transformers are enabled

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-913: -------------------------------- Summary: Incorrect username is passed to principal when principal-transformers are enabled Key: ELY-913 URL: https://issues.jboss.org/browse/ELY-913 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Critical In case when some principal-transformers are used for transforming principal in security domain then final username which is used for authentication and later for authorization is: input_username transformed by pre-realm-principal-transformer, post-realm-principal-transformer and realm principal-transformer. However Principal assigned to SecurityIdentity uses only name input_username transformed by pre-realm-principal-transformer. It seems it is caused by passing {{preRealmPrincipal}} as fourth parameter in https://github.com/wildfly-security/wildfly-elytron/blob/7b5c89c437d27fec... Value of SecurityIdentity.getPrincipal() can be seen when trace log is enabled due to https://github.com/wildfly-security/wildfly-elytron/blob/7b5c89c437d27fec... Since it seems there is currently no documentation related to this topic I cannot say whether it is real bug. [~dlofthouse] could you please provide some clarification? Log (see Steps to Reproduce for more details about configuration): {code} TRACE [org.wildfly.security] (default task-3) Principal assigning: [user], pre-realm rewritten: [user1], realm name: [ApplicationRealm], post realm rewritten: [user12], realm rewritten: [user123] TRACE [org.wildfly.security] (default task-3) Attempting to authenticate account user123 using LegacyPropertiesSecurityRealm. ... TRACE [org.wildfly.security] (default task-3) Role mapping: principal [user1] -> decoded roles [JBossAdmin] -> realm mapped roles [JBossAdmin] -> domain mapped roles [JBossAdmin] {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-913) Incorrect username is passed to principal when principal-transformers are enabled

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/ELY-913?page=com.atlassian.jira.plugin.sy... ] Ondrej Lukas updated ELY-913: ----------------------------- Affects Version/s: 1.1.0.Beta21 > Incorrect username is passed to principal when principal-transformers are enabled > --------------------------------------------------------------------------------- > > Key: ELY-913 > URL: https://issues.jboss.org/browse/ELY-913 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta21 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Critical > > In case when some principal-transformers are used for transforming principal in security domain then final username which is used for authentication and later for authorization is: input_username transformed by pre-realm-principal-transformer, post-realm-principal-transformer and realm principal-transformer. However Principal assigned to SecurityIdentity uses only name input_username transformed by pre-realm-principal-transformer. > It seems it is caused by passing {{preRealmPrincipal}} as fourth parameter in https://github.com/wildfly-security/wildfly-elytron/blob/7b5c89c437d27fec... > Value of SecurityIdentity.getPrincipal() can be seen when trace log is enabled due to https://github.com/wildfly-security/wildfly-elytron/blob/7b5c89c437d27fec... > Since it seems there is currently no documentation related to this topic I cannot say whether it is real bug. [~dlofthouse] could you please provide some clarification? > Log (see Steps to Reproduce for more details about configuration): > {code} > TRACE [org.wildfly.security] (default task-3) Principal assigning: [user], pre-realm rewritten: [user1], realm name: [ApplicationRealm], post realm rewritten: [user12], realm rewritten: [user123] > TRACE [org.wildfly.security] (default task-3) Attempting to authenticate account user123 using LegacyPropertiesSecurityRealm. > ... > TRACE [org.wildfly.security] (default task-3) Role mapping: principal [user1] -> decoded roles [JBossAdmin] -> realm mapped roles [JBossAdmin] -> domain mapped roles [JBossAdmin] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8013) Out of memory exception after a number of remote deploys

by Tiago Matias (JIRA)

[ https://issues.jboss.org/browse/WFLY-8013?page=com.atlassian.jira.plugin.... ] Tiago Matias updated WFLY-8013: ------------------------------- Priority: Major (was: Minor) > Out of memory exception after a number of remote deploys > -------------------------------------------------------- > > Key: WFLY-8013 > URL: https://issues.jboss.org/browse/WFLY-8013 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Environment: Server: Ubuntu 16.04.1 LTS x64 > bq. > bq. Startup arguments: > bq. > bq. > bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0 > Reporter: Tiago Matias > Assignee: Jason Greene > > Using the wildfly-maven-plugin for remotely deploying a WAR file do Wildfly and, after a few deploys (between 5 and 10) An outofmemory error emerges, requiring a full server restart. > *Full error log of maven.* > {quote} > [INFO] Authenticating against security realm: ManagementRealm > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 47.630 s > [INFO] Finished at: 2017-02-02T15:38:04+00:00 > [INFO] Final Memory: 22M/290M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:deploy (default) on project MyProject: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back > . Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backoffice.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\" > backoffice.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"backoffice.war\" > [ERROR] Caused by: java.lang.OutOfMemoryError: Metaspace"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"MyProject.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/una > vailable dependencies" => undefined}}} > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8013) Out of memory exception after a number of remote deploys

by Tiago Matias (JIRA)

[ https://issues.jboss.org/browse/WFLY-8013?page=com.atlassian.jira.plugin.... ] Tiago Matias updated WFLY-8013: ------------------------------- Issue Type: Bug (was: Enhancement) > Out of memory exception after a number of remote deploys > -------------------------------------------------------- > > Key: WFLY-8013 > URL: https://issues.jboss.org/browse/WFLY-8013 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.1.0.Final > Environment: Server: Ubuntu 16.04.1 LTS x64 > bq. > bq. Startup arguments: > bq. > bq. > bq. java -D[Standalone] -server -Xms256m -Xmx8096m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties -jar /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone -c standalone.xml -b 0.0.0.0 > Reporter: Tiago Matias > Assignee: Jason Greene > Priority: Minor > > Using the wildfly-maven-plugin for remotely deploying a WAR file do Wildfly and, after a few deploys (between 5 and 10) An outofmemory error emerges, requiring a full server restart. > *Full error log of maven.* > {quote} > [INFO] Authenticating against security realm: ManagementRealm > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 47.630 s > [INFO] Finished at: 2017-02-02T15:38:04+00:00 > [INFO] Final Memory: 22M/290M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.1.0.Final:deploy (default) on project MyProject: Failed to execute goal deploy: {"WFLYCTL0062: Composite operation failed and was rolled back > . Steps that failed:" => {"Operation step-1" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"backoffice.war\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\" > backoffice.war\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"backoffice.war\" > [ERROR] Caused by: java.lang.OutOfMemoryError: Metaspace"},"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"MyProject.war\".POST_MODULE"],"WFLYCTL0180: Services with missing/una > vailable dependencies" => undefined}}} > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-911) Add method to obtain the request relative path

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/ELY-911?page=com.atlassian.jira.plugin.sy... ] Pedro Igor updated ELY-911: --------------------------- Git Pull Request: https://github.com/wildfly-security/wildfly-elytron/pull/651, https://github.com/wildfly-security/elytron-web/pull/64 (was: https://github.com/wildfly-security/wildfly-elytron/pull/651) > Add method to obtain the request relative path > ---------------------------------------------- > > Key: ELY-911 > URL: https://issues.jboss.org/browse/ELY-911 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Affects Versions: 1.1.0.Beta21 > Reporter: Pedro Igor > Assignee: Pedro Igor > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-912) Create DirContext is not able to log arrays correctly

by Ondrej Lukas (JIRA)

Ondrej Lukas created ELY-912: -------------------------------- Summary: Create DirContext is not able to log arrays correctly Key: ELY-912 URL: https://issues.jboss.org/browse/ELY-912 Project: WildFly Elytron Issue Type: Bug Reporter: Ondrej Lukas Assignee: Darran Lofthouse In case when debug level for class {{org.wildfly.security.auth.realm.ldap.SimpleDirContextFactoryBuilder}} is enabled and value of any property from properties used for creating DirContext is array, then its value is not logged correctly, example: {code} Property [java.naming.security.credentials] with Value [[C@1bf1b7d5] {code} See https://github.com/wildfly-security/wildfly-elytron/blob/7b5c89c437d27fec... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017