[JBoss JIRA] (WFLY-13391) getContextClassLoader is null in Managed thread factory
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13391?page=com.atlassian.jira.plugi... ]
Brian Stansberry commented on WFLY-13391:
-----------------------------------------
[~dheerajjoshim] Does adding this attribute to the 'managed-executor-service' element fix the problem?
{code}
context-service="default"
{code}
> getContextClassLoader is null in Managed thread factory
> -------------------------------------------------------
>
> Key: WFLY-13391
> URL: https://issues.redhat.com/browse/WFLY-13391
> Project: WildFly
> Issue Type: Bug
> Components: Concurrency Utilities
> Affects Versions: 18.0.1.Final, 19.0.0.Final
> Reporter: Dheeraj Joshi
> Assignee: Eduardo Martins
> Priority: Major
> Attachments: WildFly-16-server.log, WildFly-17-server.log, WildFly-18-server.log
>
>
> We are using managed-thread-factory and Threads belong to this do not have context class loader associated with it
> {code:java}
> <managed-thread-factories>
> <managed-thread-factory name="FlowWorkManagerThreadFactory" jndi-name="java:jboss/ee/concurrency/factory/FlowWorkManagerThreadFactory" context-service="default"/>
> </managed-thread-factories>
> <managed-executor-services>
> <managed-executor-service
> name="InteractiveWorkflowWorkManagerExecutorService"
> jndi-name="java:jboss/ee/concurrency/executor/FLOW_MANAGEDEXECUTOR"
> core-threads="${threadpool.interactiveWorkflow.minthread}"
> max-threads="${threadpool.interactiveWorkflow.maxthread}" keepalive-time="5000"
> queue-length="${threadpool.interactiveWorkflow.queuesize}"
> thread-factory="FlowWorkManagerThreadFactory"
> hung-task-threshold="600000" />
> </managed-executor-services>
> {code}
> classLoader variable in below code
> {code:java}
> final ClassLoader classLoader = Thread.currentThread().getContextClassLoader();
> {code}
> evaluates as null when called inside managed thread.
> Same code works fine with {{Wildfly 16}} and {{Wildfly 17.0.1}}
> In 16 and 17.0.1 The class loader is from Service module loader.
> Server logs with {{org.jboss.as.ee}} in {{TRACE}} level for {{Wildfly 16, 17.0.1 and 18}} are attached.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JGRP-809) Copyless stack
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-809?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-809:
-------------------------------
Similarly to JGRP-815, this issue is moot with JGRP-2218 in place.
> Copyless stack
> --------------
>
> Key: JGRP-809
> URL: https://issues.redhat.com/browse/JGRP-809
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Alpha5
>
> Attachments: Buf.java, BufAllocator.java, Message.java
>
>
> Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can
> - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to)
> - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return
> - each thread in the pool has its own buffer into which the buffer is read from the socket
> Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (JGRP-809) Copyless stack
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-809?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-809.
---------------------------
Resolution: Out of Date
> Copyless stack
> --------------
>
> Key: JGRP-809
> URL: https://issues.redhat.com/browse/JGRP-809
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Major
> Fix For: 5.0.0.Alpha5
>
> Attachments: Buf.java, BufAllocator.java, Message.java
>
>
> Currently (as of 2.7), the transport reads the contents of a received packet into a buffer, then passes a *copy* of the buffer to a thread from the OOB or incoming thread pools. To prevent this copy, we can
> - have the receiver read only the version and OOB flag (to see which thread pool to dispatch the packet to)
> - pass a ref to the socket to a thread from the incoming of OOB pool, have that thread read the packet and return
> - each thread in the pool has its own buffer into which the buffer is read from the socket
> Possibly use NIO: we can install a selector and get woken up whenever data to be read is present. At that point, we can pass the ref to the socket to the handler thread and return immediately. NIO with channels for multicast sockets is available only in JDK 7 (or 8?), so this is a bit off... However, we can already implement this with reading the version and flags bytes and then passing the socket to the handler
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (DROOLS-5229) DMNValidate mojo fails XMLSchema validation with included models
by Guilherme Gomes (Jira)
[ https://issues.redhat.com/browse/DROOLS-5229?page=com.atlassian.jira.plug... ]
Guilherme Gomes updated DROOLS-5229:
------------------------------------
Tester: Jozef Marko
Sprint: 2020 Week 16-18 (from Apr 13)
Labels: drools-tools (was: )
> DMNValidate mojo fails XMLSchema validation with included models
> ----------------------------------------------------------------
>
> Key: DROOLS-5229
> URL: https://issues.redhat.com/browse/DROOLS-5229
> Project: Drools
> Issue Type: Bug
> Affects Versions: 7.34.0.Final
> Reporter: Tracy Hires
> Assignee: Guilherme Gomes
> Priority: Major
> Labels: drools-tools
> Attachments: ValidateDMN Mojo Failure.png, xml_validation_error.zip
>
>
> The attached DMN decision project was built using Business Central 7.34.0.Final. In this project, the dmn model `Math Functions.dmn` invokes business knowledge model `Quotient` from dmn model `Divide.dmn`. Invoking the ValidateDMN mojo (enabled by default) from the kie-maven-plugin fails XML Validation. One can get past this error by disabling DMNValidation with the following configuration in the pom (though disabling DMNValidation for an XML Schema validation also prevents finding FEEL parser errors):
> ```
> <build>
> <plugins>
> <plugin>
> <groupId>org.kie</groupId>
> <artifactId>kie-maven-plugin</artifactId>
> <version>7.34.0.Final</version>
> <extensions>true</extensions>
> <!-- Can get past xml validation error by disabling the ValidateDMN Mojo -->
> <configuration>
> <validateDMN>disabled</validateDMN>
> </configuration>
> </plugin>
> </plugins>
> </build>
> ```
> When one combines the two dmn models into a single model, the XML Validation succeeds (this example is not supplied, but is trivial to re-build).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (SWSQE-1131) Add Option to Check Job for Validating Bookinfo Traffice
by Matthew Mahoney (Jira)
Matthew Mahoney created SWSQE-1131:
--------------------------------------
Summary: Add Option to Check Job for Validating Bookinfo Traffice
Key: SWSQE-1131
URL: https://issues.redhat.com/browse/SWSQE-1131
Project: Kiali QE
Issue Type: QE Task
Reporter: Matthew Mahoney
There are E2Es jobs that are failing due to Bookinfo not having traffic.
Add an option to the Checker job to validate that BI has traffic, so that consuming jobs will not proceed if Bookinfo is not configured as expected.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-717) Add ability to launch H2 console from AS7 console for standalone mode
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-717?page=com.atlassian.jira.plugin.... ]
Brian Stansberry resolved WFLY-717.
-----------------------------------
Fix Version/s: (was: Awaiting Volunteers)
Assignee: (was: Pete Muir)
Resolution: Won't Do
Thanks, [~oranheim] for the instructions on how to do this for those who want it.
I'm resolving this as 'Won't Do' as I don't see this as a proper feature of WildFly itself. Exposing the H2 console is nice for dev use cases but if not done carefully it creates security risks, as the console lets you do a lot more than just examine the data produced by your WildFly app. The basic answer to those risks is "don't expose the console to an untrusted network." If WildFly itself adds a feature that exposes the console we are then somewhat responsible for whether or not it is exposed safely. I don't think that's a responsibility the WildFly project should take on.
> Add ability to launch H2 console from AS7 console for standalone mode
> ---------------------------------------------------------------------
>
> Key: WFLY-717
> URL: https://issues.redhat.com/browse/WFLY-717
> Project: WildFly
> Issue Type: Feature Request
> Components: Documentation
> Reporter: Pete Muir
> Priority: Minor
>
> See http://www.h2database.com/html/tutorial.html#tutorial_starting_h2_console for the console.
> Add ability to easily access this for the H2 datasources.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months
[JBoss JIRA] (WFLY-13393) Helloworld-jms throwing execption java.lang.IllegalThreadStateException
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-13393?page=com.atlassian.jira.plugi... ]
Parul Sharma updated WFLY-13393:
--------------------------------
Description:
Helloworld-jms throwing an exception at the end of the program.
Run : mvn clean compile exec:java
Output :
[INFO] Scanning for projects...
[INFO]
[INFO] ---------------< org.wildfly.quickstarts:helloworld-jms >---------------
[INFO] Building Quickstart: helloworld-jms 19.0.0.Beta2-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ helloworld-jms ---
[INFO] Deleting /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-java-version) @ helloworld-jms ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ helloworld-jms ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ helloworld-jms ---
[INFO] Executing: /bin/sh -c cd '/home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms' && 'git' 'rev-parse' '--verify' 'HEAD'
[INFO] Working directory: /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms
[INFO] Storing buildNumber: 10607568b2392d363f71c4192f41a11687508011 at timestamp: 1587389716538
[INFO] Storing buildScmBranch: master
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ helloworld-jms ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.8.0-jboss-2:compile (default-compile) @ helloworld-jms ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms/target/classes
[INFO]
[INFO] --- maven-checkstyle-plugin:3.0.0:checkstyle (check-style) @ helloworld-jms ---
[INFO] Starting audit...
Audit done.
[INFO]
[INFO] --- exec-maven-plugin:1.6.0:java (default-cli) @ helloworld-jms ---
Apr 20, 2020 7:05:18 PM org.wildfly.naming.client.Version <clinit>
INFO: WildFly Naming version 1.0.12.Final
Apr 20, 2020 7:05:18 PM org.wildfly.security.Version <clinit>
INFO: ELY00001: WildFly Elytron version 1.11.0.Final
Apr 20, 2020 7:05:18 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Attempting to acquire connection factory "jms/RemoteConnectionFactory"
Apr 20, 2020 7:05:18 PM org.xnio.Xnio <clinit>
INFO: XNIO version 3.7.7.Final
Apr 20, 2020 7:05:18 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.7.7.Final
Apr 20, 2020 7:05:18 PM org.jboss.threads.Version <clinit>
INFO: JBoss Threads version 2.3.3.Final
Apr 20, 2020 7:05:18 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 5.0.17.Final
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Found connection factory "jms/RemoteConnectionFactory" in JNDI
Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Attempting to acquire destination "jms/queue/test"
Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Found destination "jms/queue/test" in JNDI
Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Sending 1 messages with content: Hello, World!
Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
INFO: Received message with content Hello, World!
[WARNING] thread Thread[XNIO-1 I/O-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] was interrupted but is still alive after waiting at least 14999msecs
[WARNING] thread Thread[XNIO-1 I/O-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] thread Thread[XNIO-1 Accept,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] thread Thread[XNIO-1 task-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] thread Thread[Thread-0 (ActiveMQ-client-global-scheduled-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] thread Thread[Thread-1 (ActiveMQ-client-global-scheduled-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] thread Thread[Thread-0 (ActiveMQ-client-global-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
[WARNING] NOTE: 6 thread(s) did not finish despite being asked to via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied.
[WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=org.jboss.as.quickstarts.jms.HelloWorldJMSClient,maxpri=10]
java.lang.IllegalThreadStateException
at java.lang.ThreadGroup.destroy (ThreadGroup.java:778)
at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:321)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 19.827 s
[INFO] Finished at: 2020-04-20T19:05:35+05:30
[INFO] ------------------------------------------------------------------------
was:Helloworld-jms throwing exception in the end of the program.
> Helloworld-jms throwing execption java.lang.IllegalThreadStateException
> -----------------------------------------------------------------------
>
> Key: WFLY-13393
> URL: https://issues.redhat.com/browse/WFLY-13393
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Parul Sharma
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: ExceptionScreenShot.png
>
>
> Helloworld-jms throwing an exception at the end of the program.
> Run : mvn clean compile exec:java
> Output :
> [INFO] Scanning for projects...
> [INFO]
> [INFO] ---------------< org.wildfly.quickstarts:helloworld-jms >---------------
> [INFO] Building Quickstart: helloworld-jms 19.0.0.Beta2-SNAPSHOT
> [INFO] --------------------------------[ jar ]---------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ helloworld-jms ---
> [INFO] Deleting /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms/target
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-java-version) @ helloworld-jms ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0-M2:enforce (enforce-maven-version) @ helloworld-jms ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (get-scm-revision) @ helloworld-jms ---
> [INFO] Executing: /bin/sh -c cd '/home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms' && 'git' 'rev-parse' '--verify' 'HEAD'
> [INFO] Working directory: /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms
> [INFO] Storing buildNumber: 10607568b2392d363f71c4192f41a11687508011 at timestamp: 1587389716538
> [INFO] Storing buildScmBranch: master
> [INFO]
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ helloworld-jms ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:3.8.0-jboss-2:compile (default-compile) @ helloworld-jms ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1 source file to /home/parsharm/Documents/Wildlfy/quickstart/helloworld-jms/target/classes
> [INFO]
> [INFO] --- maven-checkstyle-plugin:3.0.0:checkstyle (check-style) @ helloworld-jms ---
> [INFO] Starting audit...
> Audit done.
> [INFO]
> [INFO] --- exec-maven-plugin:1.6.0:java (default-cli) @ helloworld-jms ---
> Apr 20, 2020 7:05:18 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.12.Final
> Apr 20, 2020 7:05:18 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.11.0.Final
> Apr 20, 2020 7:05:18 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Attempting to acquire connection factory "jms/RemoteConnectionFactory"
> Apr 20, 2020 7:05:18 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.7.7.Final
> Apr 20, 2020 7:05:18 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.7.7.Final
> Apr 20, 2020 7:05:18 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.3.Final
> Apr 20, 2020 7:05:18 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.17.Final
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
> Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Found connection factory "jms/RemoteConnectionFactory" in JNDI
> Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Attempting to acquire destination "jms/queue/test"
> Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Found destination "jms/queue/test" in JNDI
> Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Sending 1 messages with content: Hello, World!
> Apr 20, 2020 7:05:19 PM org.jboss.as.quickstarts.jms.HelloWorldJMSClient main
> INFO: Received message with content Hello, World!
> [WARNING] thread Thread[XNIO-1 I/O-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] was interrupted but is still alive after waiting at least 14999msecs
> [WARNING] thread Thread[XNIO-1 I/O-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] thread Thread[XNIO-1 Accept,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] thread Thread[XNIO-1 task-1,5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] thread Thread[Thread-0 (ActiveMQ-client-global-scheduled-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] thread Thread[Thread-1 (ActiveMQ-client-global-scheduled-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] thread Thread[Thread-0 (ActiveMQ-client-global-threads),5,org.jboss.as.quickstarts.jms.HelloWorldJMSClient] will linger despite being asked to die via interruption
> [WARNING] NOTE: 6 thread(s) did not finish despite being asked to via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied.
> [WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=org.jboss.as.quickstarts.jms.HelloWorldJMSClient,maxpri=10]
> java.lang.IllegalThreadStateException
> at java.lang.ThreadGroup.destroy (ThreadGroup.java:778)
> at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:321)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:146)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
> at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
> at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 19.827 s
> [INFO] Finished at: 2020-04-20T19:05:35+05:30
> [INFO] ------------------------------------------------------------------------
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 2 months