November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6561) EJB Timers Intermittently Execute Repeatedly on Server Restart with Error Code WFLYEJB0043

by Eder F. Freitas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6561?page=com.atlassian.jira.plugin.... ] Eder F. Freitas commented on WFLY-6561: --------------------------------------- I have understood [~swd847], thank you very much by informations. > EJB Timers Intermittently Execute Repeatedly on Server Restart with Error Code WFLYEJB0043 > ------------------------------------------------------------------------------------------ > > Key: WFLY-6561 > URL: https://issues.jboss.org/browse/WFLY-6561 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Kevin Chen > Assignee: Stuart Douglas > Labels: downstream_dependency > Fix For: 10.1.0.CR1, 10.1.0.Final > > > On Wildfly10, we are experiencing intermittent problems where on server startup, an @Timeout annotated method can be executed hundreds of times in a second (log below). Going through the references to the @Timeout methods and the @Scheduled methods, all scheduled methods are set to be non-persistent (ex: timerConfig.setPersistent(false), persistent=false) so we don't know how this could occur. It is not consistent and our only solution has been to kill the Wildfly10 server process and restart. > 13:47:27,824 WARN [org.jboss.as.ejb3] (EJB default - 6) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 96) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 97) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 37) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6561) EJB Timers Intermittently Execute Repeatedly on Server Restart with Error Code WFLYEJB0043

by Eder F. Freitas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6561?page=com.atlassian.jira.plugin.... ] Eder F. Freitas edited comment on WFLY-6561 at 11/22/16 5:15 AM: ----------------------------------------------------------------- In Wildfly 8 it works right? If the current one is not finished the next one is not canceled. Is there a workaround? (Restricted to jira-users group) was (Author: eder.freitas): In Wildfly 8 it works right? If the current one is not finished the next one is not canceled. There is a workaround? (Restricted to jira-users group) > EJB Timers Intermittently Execute Repeatedly on Server Restart with Error Code WFLYEJB0043 > ------------------------------------------------------------------------------------------ > > Key: WFLY-6561 > URL: https://issues.jboss.org/browse/WFLY-6561 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Final > Reporter: Kevin Chen > Assignee: Stuart Douglas > Labels: downstream_dependency > Fix For: 10.1.0.CR1, 10.1.0.Final > > > On Wildfly10, we are experiencing intermittent problems where on server startup, an @Timeout annotated method can be executed hundreds of times in a second (log below). Going through the references to the @Timeout methods and the @Scheduled methods, all scheduled methods are set to be non-persistent (ex: timerConfig.setPersistent(false), persistent=false) so we don't know how this could occur. It is not consistent and our only solution has been to kill the Wildfly10 server process and restart. > 13:47:27,824 WARN [org.jboss.as.ejb3] (EJB default - 6) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 96) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 97) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. > 13:47:27,825 WARN [org.jboss.as.ejb3] (EJB default - 37) [ ] WFLYEJB0043: A previous execution of timer [id=d31eb95a-3f8b-4b7d-882e-f1ff53bc7de8 timedObjectId=synergy.synergy-app-head.QuartzWatcherService auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@dec94c6 initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Wed Apr 06 12:10:00 PDT 2016 timerState=IN_TIMEOUT info=null] is still in progress, skipping this overlapping scheduled execution at: Wed Apr 06 13:47:27 PDT 2016. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7647) Configure Artemis thread pool size without reload

by Martin Styk (JIRA)

Martin Styk created WFLY-7647: --------------------------------- Summary: Configure Artemis thread pool size without reload Key: WFLY-7647 URL: https://issues.jboss.org/browse/WFLY-7647 Project: WildFly Issue Type: Enhancement Components: JMS Affects Versions: 10.1.0.Final Reporter: Martin Styk Assignee: Jeff Mesnil Currently, thread pool size can not be adjusted without server reload. If server runs into performance problem caused by thread pool size, there is no way to adjust thread pool size without termination of all running tasks. Making this configurable "on fly" would prevent this scenario. Attribute {{thread-pool-max-size}} in {{/subsystem=messaging-activemq/server=default}} requires server reload. Size of global client thread pools can be set only before this thread pool is created. Adjusting values of system properties which configure client thread pool size has no effect on running server (with pool already created). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7646) Update description of security-realm in management interfaces

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7646?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7646: ------------------------------- Labels: user_experience (was: ) > Update description of security-realm in management interfaces > ------------------------------------------------------------- > > Key: WFLY-7646 > URL: https://issues.jboss.org/browse/WFLY-7646 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Description of security-realm attribute in HTTP (and native) management interfaces says: > "The security realm to use for the HTTP management interface." or "The security realm to use for the native management interface." > However Elytron also uses security-realms. Description of mentioned about attribute should include information that it uses *legacy* security realm (not Elytron). Without word "legacy" it can be confusing since two different types of security-realm currently occur in configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7646) Update description of security-realm in management interfaces

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-7646: ---------------------------------- Summary: Update description of security-realm in management interfaces Key: WFLY-7646 URL: https://issues.jboss.org/browse/WFLY-7646 Project: WildFly Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Description of security-realm attribute in HTTP (and native) management interfaces says: "The security realm to use for the HTTP management interface." or "The security realm to use for the native management interface." However Elytron also uses security-realms. Description of mentioned about attribute should include information that it uses *legacy* security realm (not Elytron). Without word "legacy" it can be confusing since two different types of security-realm currently occur in configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7646) Update description of security-realm in management interfaces

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7646?page=com.atlassian.jira.plugin.... ] Ondrej Lukas updated WFLY-7646: ------------------------------- Affects Version/s: 11.0.0.Alpha1 > Update description of security-realm in management interfaces > ------------------------------------------------------------- > > Key: WFLY-7646 > URL: https://issues.jboss.org/browse/WFLY-7646 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Labels: user_experience > > Description of security-realm attribute in HTTP (and native) management interfaces says: > "The security realm to use for the HTTP management interface." or "The security realm to use for the native management interface." > However Elytron also uses security-realms. Description of mentioned about attribute should include information that it uses *legacy* security realm (not Elytron). Without word "legacy" it can be confusing since two different types of security-realm currently occur in configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-927) Option roleRecursion does not work in LdapRolesMappingProvider

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SECURITY-927?page=com.atlassian.jira.plug... ] RH Bugzilla Integration commented on SECURITY-927: -------------------------------------------------- Ivo Hradek <ihradek(a)redhat.com> changed the Status of [bug 1269826|https://bugzilla.redhat.com/show_bug.cgi?id=1269826] from ON_QA to VERIFIED > Option roleRecursion does not work in LdapRolesMappingProvider > -------------------------------------------------------------- > > Key: SECURITY-927 > URL: https://issues.jboss.org/browse/SECURITY-927 > Project: PicketBox > Issue Type: Bug > Components: JBossSX > Affects Versions: PicketBox_5_0_0.Alpha2 > Reporter: Ondrej Lukas > Assignee: Ryan Emerson > > Option roleRecursion does not work in org.jboss.security.mapping.providers.role.LdapRolesMappingProvider. Only entries without recursion are found. No recursive search is done by LdapRolesMappingProvider since LdapRolesMappingProvider.rolesSearch method tries to make a recursive search with same parameters. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7457) UT005013 causes OutOfMemoryError

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7457?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-7457: -------------------------------------- Is it possible that the F5 was not actually dropping the TCP connection properly? If no timeout was configured then Wildfly may run out of memory as it will keep the data structures associated with those connections around forever. > UT005013 causes OutOfMemoryError > -------------------------------- > > Key: WFLY-7457 > URL: https://issues.jboss.org/browse/WFLY-7457 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Reporter: Steve Vater > Assignee: Stuart Douglas > Labels: new_and_noteworthy > > There's some F5 WAF within the network where our WildFly is running. The WAF sends multiple Keep Alive-Requests to our WAF via TCP, but without sending "close_notify" after the communication has ended. > Undertow throws UT005013, which is correct, but this causes the JVM to run out of Memory. The keepalive is sent 12 times per minute (every 5 seconds) to our WildFly. > We already installed an update of Undertow (1.4.3); This didn't help. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7228) Improve wording in logging message for key WFLYWELD0013

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-7228?page=com.atlassian.jira.plugin.... ] Stuart Douglas reopened WFLY-7228: ---------------------------------- > Improve wording in logging message for key WFLYWELD0013 > ------------------------------------------------------- > > Key: WFLY-7228 > URL: https://issues.jboss.org/browse/WFLY-7228 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Gunnar Morling > Assignee: Stuart Douglas > Priority: Minor > Fix For: 11.0.0.Alpha1 > > > I'm seeing this message: > {quote} > WFLYWELD0013: Deployment deployment "demo.war" contains CDI annotations but no bean archive was not found. (No beans.xml nor class with bean defining annotations) > {quote} > Apart from the repeated "deployment", the double negation makes it confusing, I reckon it should say something like that: > {quote} > WFLYWELD0013: Deployment "demo.war" contains CDI annotations but is not a bean archive (Found no beans.xml nor a class with bean defining annotations) > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2027) Option server_config should be a file name not a path as stated by command help

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2027?page=com.atlassian.jira.plugi... ] Ken Wills moved JBEAP-7435 to WFCORE-2027: ------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2027 (was: JBEAP-7435) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CLI Domain Management (was: CLI) (was: Domain Management) Affects Version/s: (was: 7.1.0.DR6) > Option server_config should be a file name not a path as stated by command help > ------------------------------------------------------------------------------- > > Key: WFCORE-2027 > URL: https://issues.jboss.org/browse/WFCORE-2027 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Domain Management > Reporter: Ken Wills > Assignee: Ken Wills > > embed-server --help, says the server_config should be the name of the file and not a path, you can set a path relative to the standalone/configuration that can be in any place inside the server ../../../ it does load the file you set there but then fails to change any properties as it does in the default standalone under jboss_home/standalone/config -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 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 November 2016