[JBoss JIRA] (WFLY-9727) WildFly Randomly Terminates after 5-10 minutes
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9727?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9727:
-----------------------------
Priority: Critical (was: Blocker)
> 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: Critical
> 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)
8 years, 2 months
[JBoss JIRA] (WFLY-9590) auto-[create|delete]-jms-queues are not supported in Artemis 2.4
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ]
Kabir Khan commented on WFLY-9590:
----------------------------------
The feature-branch-blocker label is to reflect what [~jmesnil] says: "The issue was reported by QE when they check any regression for the Artemis upgrades.
These issues does not reflect issues in the actual codebase but only in the branch that contains the upgrade, i.e. they are blocker for the upgrade of Artemis."
> auto-[create|delete]-jms-queues are not supported in Artemis 2.4
> ----------------------------------------------------------------
>
> Key: WFLY-9590
> URL: https://issues.jboss.org/browse/WFLY-9590
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: feature-branch-blocker
>
> For more information about origin of this issue see JBEAP-13856.
> Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore.
> In EAP 7.1 the features are disabled by default and they are Technical previews.
> In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect.
> *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9590) auto-[create|delete]-jms-queues are not supported in Artemis 2.4
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9590?page=com.atlassian.jira.plugin.... ]
Kabir Khan updated WFLY-9590:
-----------------------------
Labels: feature-branch-blocker (was: )
> auto-[create|delete]-jms-queues are not supported in Artemis 2.4
> ----------------------------------------------------------------
>
> Key: WFLY-9590
> URL: https://issues.jboss.org/browse/WFLY-9590
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: feature-branch-blocker
>
> For more information about origin of this issue see JBEAP-13856.
> Auto-create-jms-queues and auto-delete-jms-queues enable or disable automatic creation or deletion of JMS queues when they are requested or when they are not used anymore.
> In EAP 7.1 the features are disabled by default and they are Technical previews.
> In EAP 7.2 the features cannot be disabled via mentioned management attributes and thus they are always enabled. The “cannot be” in previous sentence means that the configuration has no effect.
> *Customer impact:* Behavior of messaging broker was changed in case of automatic creation and deletion JMS destinations.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3569?page=com.atlassian.jira.plugi... ]
David Lloyd resolved WFCORE-3569.
---------------------------------
Resolution: Duplicate Issue
> NPE is shown in server shutdown
> -------------------------------
>
> Key: WFCORE-3569
> URL: https://issues.jboss.org/browse/WFCORE-3569
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, IO, Server
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: David Lloyd
> Priority: Critical
>
> NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
> Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
> {noformat}
> 13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
> at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
> at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
> at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9346) Race condition during ORB startup
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9346?page=com.atlassian.jira.plugin.... ]
Kabir Khan edited comment on WFLY-9346 at 2/5/18 11:37 AM:
-----------------------------------------------------------
Reopening as https://github.com/wildfly/wildfly/pull/10702 does not seem to be merged yet, and I don't want to resolve JBEAP-13680 until that is done. Ping me if I have got things wrong
was (Author: kabirkhan):
Reopening as https://github.com/wildfly/wildfly/pull/10702 does not seem to be merged yet
> Race condition during ORB startup
> ---------------------------------
>
> Key: WFLY-9346
> URL: https://issues.jboss.org/browse/WFLY-9346
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Security
> Affects Versions: 11.0.0.CR1
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Fix For: 12.0.0.Alpha1
>
>
> In the code, there is not direct dependency between ORB service and the security which occasionally may lead to the following error:
> {code}
> 2017-09-10 22:06:57,015 WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (MSC service thread 1-3) "IOP01210227: (BAD_OPERATION) Error in running ORB configurator": org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 227 completed: No
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:558) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:576) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:485) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:543) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at org.omg.CORBA.ORB.init(ORB.java:353) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:126) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_144]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_144]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_144]
> Caused by: java.lang.RuntimeException: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain
> at org.wildfly.iiop.openjdk.security.LegacySSLSocketFactory.setORB(LegacySSLSocketFactory.java:86) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT]
> at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.initializeTransport(ORBConfiguratorImpl.java:271) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:149) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:483) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> ... 8 more
> Caused by: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-9346) Race condition during ORB startup
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-9346?page=com.atlassian.jira.plugin.... ]
Kabir Khan reopened WFLY-9346:
------------------------------
Reopening as https://github.com/wildfly/wildfly/pull/10702 does not seem to be merged yet
> Race condition during ORB startup
> ---------------------------------
>
> Key: WFLY-9346
> URL: https://issues.jboss.org/browse/WFLY-9346
> Project: WildFly
> Issue Type: Bug
> Components: IIOP, Security
> Affects Versions: 11.0.0.CR1
> Reporter: Tomasz Adamski
> Assignee: Tomasz Adamski
> Fix For: 12.0.0.Alpha1
>
>
> In the code, there is not direct dependency between ORB service and the security which occasionally may lead to the following error:
> {code}
> 2017-09-10 22:06:57,015 WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (MSC service thread 1-3) "IOP01210227: (BAD_OPERATION) Error in running ORB configurator": org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 227 completed: No
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:558) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:576) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:485) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:543) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at org.omg.CORBA.ORB.init(ORB.java:353) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:126) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_144]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_144]
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_144]
> Caused by: java.lang.RuntimeException: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain
> at org.wildfly.iiop.openjdk.security.LegacySSLSocketFactory.setORB(LegacySSLSocketFactory.java:86) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT]
> at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.initializeTransport(ORBConfiguratorImpl.java:271) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:149) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:483) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1]
> ... 8 more
> Caused by: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain
> ... 12 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFLY-7795) org.jboss.sasl classes still making it into jboss-client.jar
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFLY-7795?page=com.atlassian.jira.plugin.... ]
Darran Lofthouse commented on WFLY-7795:
----------------------------------------
Dropping to Critical - since this was raised a lot of work has been undertaken in Elytron Authentication Client to select the correct providers and implementations. This should be cleaned up at some point but is not an outstanding issue that should block the release.
> org.jboss.sasl classes still making it into jboss-client.jar
> ------------------------------------------------------------
>
> Key: WFLY-7795
> URL: https://issues.jboss.org/browse/WFLY-7795
> Project: WildFly
> Issue Type: Bug
> Components: Build System
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Critical
> Fix For: 12.0.0.Alpha1
>
>
> The dependencies should have been removed but maybe this is still coming in as a transitive dependency from elsewhere.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (WFCORE-3569) NPE is shown in server shutdown
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3569?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFCORE-3569:
------------------------------------------
[~dmlloyd] Yes, this is the same, same as WFCORE-3572.
> NPE is shown in server shutdown
> -------------------------------
>
> Key: WFCORE-3569
> URL: https://issues.jboss.org/browse/WFCORE-3569
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Domain Management, IO, Server
> Affects Versions: 4.0.0.Alpha8
> Reporter: Chao Wang
> Assignee: David Lloyd
> Priority: Critical
>
> NullPointerException is shown in server shutdown with an open CLI connection in current WFLY master since WFCORE 4.0.0.Alpha7.
> Start the server and open a CLI connection, then stop server with Ctrl + C. We will see
> {noformat}
> 13:15:09,136 ERROR [org.jboss.threads.errors] (management task-1) Thread Thread[management task-1,5,main] threw an uncaught exception: java.lang.NullPointerException
> at org.jboss.as.server.mgmt.ManagementWorkerService.stopDone(ManagementWorkerService.java:72)
> at org.xnio.XnioWorker$1.run(XnioWorker.java:138)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1979)
> at org.jboss.threads.EnhancedQueueExecutor.completeTermination(EnhancedQueueExecutor.java:1755)
> at org.jboss.threads.EnhancedQueueExecutor.tryDeallocateThread(EnhancedQueueExecutor.java:1578)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1393)
> at java.lang.Thread.run(Thread.java:748)
> {noformat}
> I assign this to David as it seems this is caused by WFCORE-3397 and https://github.com/wildfly/wildfly-core/pull/3072 Please feel free to reassign to correct person.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months