February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9727) WildFly Randomly Terminates after 5-10 minutes

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9727?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-9727: ----------------------------------- What is the exact version of JDK you are using? > WildFly Randomly Terminates after 5-10 minutes > ---------------------------------------------- > > Key: WFLY-9727 > URL: https://issues.jboss.org/browse/WFLY-9727 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.Final > Environment: Running WildFly 10.x from within Eclipse Oxygen (4.7.2) on 2015 MacBook Pro running OS X El Capitan (10.11.6) > Reporter: Daniel Wiseman > Assignee: Jason Greene > Priority: Blocker > Original Estimate: 1 week > Remaining Estimate: 1 week > > I've been experiencing an odd intermittent issue on my WildFly server that has been running on my local system. Every other day or so my server will shutdown, without warning, after running for five to ten minutes from launch. The WildFly server logs contain no errors but the Eclipse logs output these two stack identical stack traces every time: > {{Exception in thread "Remoting "management-client" I/O-1" java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:354) > at org.xnio.AbstractIoFuture.runAllNotifiers(AbstractIoFuture.java:233) > at org.xnio.AbstractIoFuture.setCancelled(AbstractIoFuture.java:291) > at org.xnio.FutureResult.setCancelled(FutureResult.java:98) > at org.xnio.nio.WorkerThread$ConnectHandle.forceTermination(WorkerThread.java:339) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:492) > Exception in thread "Remoting "management-client" I/O-1" java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating > at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588) > at org.xnio.AbstractIoFuture.runNotifier(AbstractIoFuture.java:354) > at org.xnio.AbstractIoFuture.runAllNotifiers(AbstractIoFuture.java:233) > at org.xnio.AbstractIoFuture.setCancelled(AbstractIoFuture.java:291) > at org.xnio.FutureResult.setCancelled(FutureResult.java:98) > at org.xnio.nio.WorkerThread$ConnectHandle.forceTermination(WorkerThread.java:339) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:492)}} > This issue will occur on every server start for an entire day and then the next day it won't happen at all. However, when it happens it makes debugging the software I write that runs of the server near impossible. Does anyone have any ideas what could be causing this issue? Let me know if you need more details, thanks! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3571) Improve CLI error handling in ListCommand

by Marek Kopecký (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3571?page=com.atlassian.jira.plugi... ] Marek Kopecký updated WFCORE-3571: ---------------------------------- Affects Version/s: 4.0.0.Alpha8 > Improve CLI error handling in ListCommand > ----------------------------------------- > > Key: WFCORE-3571 > URL: https://issues.jboss.org/browse/WFCORE-3571 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Alpha8 > Reporter: Marek Kopecký > Assignee: Marek Kopecký > Priority: Minor > > Improve CLI error handling in ListCommand class. If management operation doesn't return correct results, CLI should throw correct error message. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3571) Improve CLI error handling in ListCommand

by Marek Kopecký (JIRA)

Marek Kopecký created WFCORE-3571: ------------------------------------- Summary: Improve CLI error handling in ListCommand Key: WFCORE-3571 URL: https://issues.jboss.org/browse/WFCORE-3571 Project: WildFly Core Issue Type: Bug Components: CLI Reporter: Marek Kopecký Assignee: Marek Kopecký Priority: Minor Improve CLI error handling in ListCommand class. If management operation doesn't return correct results, CLI should throw correct error message. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9748) Support new method-level "@Priority" annotation

by David Lloyd (JIRA)

David Lloyd created WFLY-9748: --------------------------------- Summary: Support new method-level "@Priority" annotation Key: WFLY-9748 URL: https://issues.jboss.org/browse/WFLY-9748 Project: WildFly Issue Type: Enhancement Components: CDI / Weld, EE, EJB Reporter: David Lloyd Priority: Critical Fix For: 12.0.0.Alpha1 The {{@Priority}} annotation in Common Annotations 1.3 has gained a METHOD applicability level. We must ensure that our interceptor metadata processing picks up these annotations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9748) Support new method-level "@Priority" annotation

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9748?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-9748: ------------------------------ Labels: JavaEE8 (was: ) > Support new method-level "@Priority" annotation > ----------------------------------------------- > > Key: WFLY-9748 > URL: https://issues.jboss.org/browse/WFLY-9748 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld, EE, EJB > Reporter: David Lloyd > Priority: Critical > Labels: JavaEE8 > Fix For: 12.0.0.Alpha1 > > > The {{@Priority}} annotation in Common Annotations 1.3 has gained a METHOD applicability level. We must ensure that our interceptor metadata processing picks up these annotations. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6463) Common Annotations 1.3 Support

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6463?page=com.atlassian.jira.plugin.... ] Tomaz Cerar commented on WFLY-6463: ----------------------------------- component tagged under jboss-annotations-api_1.3_spec-1.0.0.Final and released to maven > Common Annotations 1.3 Support > ------------------------------ > > Key: WFLY-6463 > URL: https://issues.jboss.org/browse/WFLY-6463 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Tomaz Cerar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9282) UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9282?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9282: ----------------------------------- Per discussions, this may be fully resolved already. Let's see if we can close this out. > UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9282 > URL: https://issues.jboss.org/browse/WFLY-9282 > Project: WildFly > Issue Type: Enhancement > Components: EJB > Environment: Remote client EJB invocation > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > It should be possible to lookup a UserTransaction from a node or a cluster and call .begin() with starting the Transaction lazy until the first EJB invocation. > The invocation will implicit begin the transaction and all invocation are sticky to that node. > This is to spread the load across several server instances if there is no running transaction but keep the transaction sticky to the first selected node. > It prevents from a strong affinity to one instance via URI affinity or the necessity to define the node for the UserTransaction upfront. > The sticiness is because of issues with persistence like JPA as here the server is not really 'stateless' as the session of EntityManager can decide to not flush the changed data to the underlying database which can cause issues if the transaction will continued on a different instance if the client invoke EJB's multiple times. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6463) Common Annotations 1.3 Support

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6463?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-6463: --------------------------------- Assignee: Tomaz Cerar > Common Annotations 1.3 Support > ------------------------------ > > Key: WFLY-6463 > URL: https://issues.jboss.org/browse/WFLY-6463 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > Assignee: Tomaz Cerar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6463) Common Annotations 1.3 Support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6463?page=com.atlassian.jira.plugin.... ] David Lloyd reopened WFLY-6463: ------------------------------- > Common Annotations 1.3 Support > ------------------------------ > > Key: WFLY-6463 > URL: https://issues.jboss.org/browse/WFLY-6463 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6463) Common Annotations 1.3 Support

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-6463?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-6463: ------------------------------ Comment: was deleted (was: Dropped.) > Common Annotations 1.3 Support > ------------------------------ > > Key: WFLY-6463 > URL: https://issues.jboss.org/browse/WFLY-6463 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: David Lloyd > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2018