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: --------------------------------------- This error is still happening in Wildfly 10.1.0, SUSE operating system, do you need any more information about it? {{2016-11-18 17:28:00,002 WARN [org.jboss.as.ejb3.timer] (EJB default - 5) WFLYEJB0043: A previous execution of timer [id=e1bdd4d5-93e9-44e5-a8e1-7f196aa9e935 timedObjectId=prati.supervisorio.nobreaks.supervisorio.nobreaks-ejb.MonitoramentoProcess auto-timer?:false persistent?:false timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@4c67a17f initialExpiration=null intervalDuration(in milli sec)=0 nextExpiration=Fri Nov 18 17:28:00 BRST 2016 timerState=IN_TIMEOUT info=NOBREAK_SEM_BANCO_UPS] is still in progress, skipping this overlapping scheduled execution at: Fri Nov 18 17:28:00 BRST 2016. }} > 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-7629) Elytron key-store requires set credential-reference which is wrongly marked as optional.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7629?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved WFCORE-2018 to WFLY-7629: ------------------------------------------------ Project: WildFly (was: WildFly Core) Key: WFLY-7629 (was: WFCORE-2018) Component/s: Security (was: Security) Fix Version/s: (was: 3.0.0.Alpha13) > Elytron key-store requires set credential-reference which is wrongly marked as optional. > ---------------------------------------------------------------------------------------- > > Key: WFLY-7629 > URL: https://issues.jboss.org/browse/WFLY-7629 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > > In EAP7.1.0.DR7 Elytron key-store uses credential-reference with clear-text attribute for password instead of password attribute. > But there is problem with credential-reference element which is wrongly marked as optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2018) Elytron key-store requires set credential-reference which is wrongly marked as optional.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2018?page=com.atlassian.jira.plugi... ] Brian Stansberry reopened WFCORE-2018: -------------------------------------- I'm going to reopen this and move it back to WFLY since thinking about I suspect the core PR was just step 1. > Elytron key-store requires set credential-reference which is wrongly marked as optional. > ---------------------------------------------------------------------------------------- > > Key: WFCORE-2018 > URL: https://issues.jboss.org/browse/WFCORE-2018 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 3.0.0.Alpha13 > > > In EAP7.1.0.DR7 Elytron key-store uses credential-reference with clear-text attribute for password instead of password attribute. > But there is problem with credential-reference element which is wrongly marked as optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2018) Elytron key-store requires set credential-reference which is wrongly marked as optional.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2018?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-7432 to WFCORE-2018: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2018 (was: WFLY-7432) Component/s: Security (was: Security) > Elytron key-store requires set credential-reference which is wrongly marked as optional. > ---------------------------------------------------------------------------------------- > > Key: WFCORE-2018 > URL: https://issues.jboss.org/browse/WFCORE-2018 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Peter Skopek > Fix For: 3.0.0.Alpha13 > > > In EAP7.1.0.DR7 Elytron key-store uses credential-reference with clear-text attribute for password instead of password attribute. > But there is problem with credential-reference element which is wrongly marked as optional. > Please set this element on mandatory with respect to this issue https://issues.jboss.org/browse/WFLY-7125 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2017) embed-server does not start with standalone-elytron.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2017?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFCORE-2017: ------------------------------------------ Looks fairly trivial, just need to correct the requiresRuntime for the AccessIdentityResourceDefinition add handler. > embed-server does not start with standalone-elytron.xml > ------------------------------------------------------- > > Key: WFCORE-2017 > URL: https://issues.jboss.org/browse/WFCORE-2017 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Affects Versions: 3.0.0.Alpha12 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > > I am unable to start embed-server with standalone-elytron.xml > 1){{./jboss-cli.sh}} > 2) {{embed-server --std-out=echo -c=standalone-elytron.xml}} > 3) server is missing org.wildfly.security.security-domain.ManagementDomain, which is however registered in elytron subsystem. > Starting {{./standalone.sh -c=standalone-elytron.xml}} works fine. > Full log: > {code} > [mchoma@localhost bin]$ ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server --std-out=echo -c=standalone-elytron.xml > 08:15:40,801 INFO [org.jboss.modules] (AeshProcess: 1) JBoss Modules version 1.6.0.Beta3 > 08:15:40,845 INFO [org.jboss.msc] (AeshProcess: 1) JBoss MSC version 1.2.7.Final-redhat-1 > 08:15:40,916 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) starting > 08:15:41,088 INFO [org.jboss.as.domain.management] (MSC service thread 1-5) WFLYDM0136: Registered OpenSSL provider > 08:15:41,804 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 08:15:41,805 INFO [org.wildfly.extension.elytron] (Controller Boot Thread) WFLYELY00001: Activating Elytron Subsystem Elytron Version=1.1.0.Beta13, Subsystem Version=1.0.0.Alpha13 > 08:15:41,811 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 08:15:41,859 INFO [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > 08:15:42,024 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("access" => "identity") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-domain.ManagementDomain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.management.identity is missing [org.wildfly.security.security-domain.ManagementDomain]"] > } > 08:16:19,546 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) stopped in 3ms > Cannot start embedded server: WFLYEMB0021: Cannot start embedded process: java.lang.InterruptedException > [disconnected /] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2017) embed-server does not start with standalone-elytron.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2017?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-7588 to WFCORE-2017: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2017 (was: WFLY-7588) Component/s: CLI Security (was: CLI) (was: Security) Affects Version/s: 3.0.0.Alpha12 (was: 11.0.0.Alpha1) > embed-server does not start with standalone-elytron.xml > ------------------------------------------------------- > > Key: WFCORE-2017 > URL: https://issues.jboss.org/browse/WFCORE-2017 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Security > Affects Versions: 3.0.0.Alpha12 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > > I am unable to start embed-server with standalone-elytron.xml > 1){{./jboss-cli.sh}} > 2) {{embed-server --std-out=echo -c=standalone-elytron.xml}} > 3) server is missing org.wildfly.security.security-domain.ManagementDomain, which is however registered in elytron subsystem. > Starting {{./standalone.sh -c=standalone-elytron.xml}} works fine. > Full log: > {code} > [mchoma@localhost bin]$ ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server --std-out=echo -c=standalone-elytron.xml > 08:15:40,801 INFO [org.jboss.modules] (AeshProcess: 1) JBoss Modules version 1.6.0.Beta3 > 08:15:40,845 INFO [org.jboss.msc] (AeshProcess: 1) JBoss MSC version 1.2.7.Final-redhat-1 > 08:15:40,916 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) starting > 08:15:41,088 INFO [org.jboss.as.domain.management] (MSC service thread 1-5) WFLYDM0136: Registered OpenSSL provider > 08:15:41,804 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 08:15:41,805 INFO [org.wildfly.extension.elytron] (Controller Boot Thread) WFLYELY00001: Activating Elytron Subsystem Elytron Version=1.1.0.Beta13, Subsystem Version=1.0.0.Alpha13 > 08:15:41,811 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 08:15:41,859 INFO [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > 08:15:42,024 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("access" => "identity") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-domain.ManagementDomain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.management.identity is missing [org.wildfly.security.security-domain.ManagementDomain]"] > } > 08:16:19,546 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) stopped in 3ms > Cannot start embedded server: WFLYEMB0021: Cannot start embedded process: java.lang.InterruptedException > [disconnected /] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7588) embed-server does not start with standalone-elytron.xml

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-7588?page=com.atlassian.jira.plugin.... ] Darran Lofthouse reassigned WFLY-7588: -------------------------------------- Assignee: Darran Lofthouse > embed-server does not start with standalone-elytron.xml > ------------------------------------------------------- > > Key: WFLY-7588 > URL: https://issues.jboss.org/browse/WFLY-7588 > Project: WildFly > Issue Type: Bug > Components: CLI, Security > Affects Versions: 11.0.0.Alpha1 > Reporter: Martin Choma > Assignee: Darran Lofthouse > Priority: Blocker > > I am unable to start embed-server with standalone-elytron.xml > 1){{./jboss-cli.sh}} > 2) {{embed-server --std-out=echo -c=standalone-elytron.xml}} > 3) server is missing org.wildfly.security.security-domain.ManagementDomain, which is however registered in elytron subsystem. > Starting {{./standalone.sh -c=standalone-elytron.xml}} works fine. > Full log: > {code} > [mchoma@localhost bin]$ ./jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands. > [disconnected /] embed-server --std-out=echo -c=standalone-elytron.xml > 08:15:40,801 INFO [org.jboss.modules] (AeshProcess: 1) JBoss Modules version 1.6.0.Beta3 > 08:15:40,845 INFO [org.jboss.msc] (AeshProcess: 1) JBoss MSC version 1.2.7.Final-redhat-1 > 08:15:40,916 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) starting > 08:15:41,088 INFO [org.jboss.as.domain.management] (MSC service thread 1-5) WFLYDM0136: Registered OpenSSL provider > 08:15:41,804 INFO [org.wildfly.security] (Controller Boot Thread) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 08:15:41,805 INFO [org.wildfly.extension.elytron] (Controller Boot Thread) WFLYELY00001: Activating Elytron Subsystem Elytron Version=1.1.0.Beta13, Subsystem Version=1.0.0.Alpha13 > 08:15:41,811 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation. > 08:15:41,859 INFO [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none > 08:15:42,024 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("core-service" => "management"), > ("access" => "identity") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.security-domain.ManagementDomain"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.management.identity is missing [org.wildfly.security.security-domain.ManagementDomain]"] > } > 08:16:19,546 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) stopped in 3ms > Cannot start embedded server: WFLYEMB0021: Cannot start embedded process: java.lang.InterruptedException > [disconnected /] > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2005) Tab completion don't work in deploy operation if '~' is used

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2005?page=com.atlassian.jira.plugi... ] Jean-Francois Denise updated WFCORE-2005: ----------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/1967 > Tab completion don't work in deploy operation if '~' is used > ------------------------------------------------------------ > > Key: WFCORE-2005 > URL: https://issues.jboss.org/browse/WFCORE-2005 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > Completion doesn't work properly for: > - ~XXX > - quoted paths > - paths that contain escaped white spaces -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7210) Expose JAX-RS resources as children of the subsystem

by Guillermo González de Agüero (JIRA)

[ https://issues.jboss.org/browse/WFLY-7210?page=com.atlassian.jira.plugin.... ] Guillermo González de Agüero commented on WFLY-7210: ---------------------------------------------------- If HAL is able to use properly read it, then I'm ok with WFLY-7024 format. > Expose JAX-RS resources as children of the subsystem > ---------------------------------------------------- > > Key: WFLY-7210 > URL: https://issues.jboss.org/browse/WFLY-7210 > Project: WildFly > Issue Type: Feature Request > Components: REST > Affects Versions: 10.1.0.Final > Reporter: Guillermo González de Agüero > Assignee: Lin Gao > Attachments: after-wfly7024.png, hal-jaxrs.png > > > Servlets, EJBs, WebSockets, JPA, etc expose its components as children of the subsystem in the management API. For example to list the stateless EJBs of a deployment: > [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=ejb3:read-children-resources(child-type=stateless-session-bean) > This makes it specially easy to navigate trough the web console (attached screenshot). > To read JAX-RS resources, the command would be: > [standalone@localhost:9990 /] /deployment=cdivsejb.war/subsystem=jaxrs:show-resources() > I propose to make deprecate the show-resources operation and create a new "resources" child, containing the Rest resources. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7628) Allow to use an Infinispan cache as EJB timer store

by Guillermo González de Agüero (JIRA)

Guillermo González de Agüero created WFLY-7628: -------------------------------------------------- Summary: Allow to use an Infinispan cache as EJB timer store Key: WFLY-7628 URL: https://issues.jboss.org/browse/WFLY-7628 Project: WildFly Issue Type: Feature Request Components: Clustering, EJB Reporter: Guillermo González de Agüero Assignee: Paul Ferraro EJB subsystem allows to configure a datanase datasource to use as a store for persistent timers. I miss the option to use an Infinispan cache, that could even be configured as the default store out of the box. This is something Payara is already offering with Hazelcast (https://payara.gitbooks.io/payara-server/content/documentation/extended-d...). -- 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