[JBoss JIRA] (DROOLS-3422) Validate scenario dmn import validation
by Gabriele Cardosi (Jira)
Gabriele Cardosi created DROOLS-3422:
----------------------------------------
Summary: Validate scenario dmn import validation
Key: DROOLS-3422
URL: https://issues.jboss.org/browse/DROOLS-3422
Project: Drools
Issue Type: Task
Components: Scenario Simulation and Testing
Reporter: Gabriele Cardosi
Assignee: Gabriele Cardosi
When importing a dmn-scenario, validate the dmn file path it points to, and eventually discard import.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11493) Core queues loaded at boot are not removable
by ehsavoie Hugonnet (Jira)
ehsavoie Hugonnet created WFLY-11493:
----------------------------------------
Summary: Core queues loaded at boot are not removable
Key: WFLY-11493
URL: https://issues.jboss.org/browse/WFLY-11493
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 15.0.0.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
A core queue created via the ServerAdd operation is not removable.
Reproducer :
/subsystem=messaging-activemq/server=default/queue=queue.standalone:add(queue-address=queue.standalone, durable)
:reload
/subsystem=messaging-activemq/server=default/queue=queue.standalone:remove
:reload
/subsystem=messaging-activemq/server=default/queue=queue.standalone:add(queue-address=queue.standalone, durable)
The 2nd add will fail as the queue still exists.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11475) Counter - registry.counter(metadata)- IllegalArgumentException
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-11475?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski commented on WFLY-11475:
-------------------------------------------
(default task-1) UT005023: Exception handling request to /hello-prometheus/resources/coffee/stats: org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Previously registered metric statsHits was not flagged as reusable
at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:78)
at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:222)
at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:193)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:455)
at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:229)
at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:135)
at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355)
at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:138)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:215)
at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:227)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:791)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:74)
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:129)
at io.opentracing.contrib.jaxrs2.server.SpanFinishingFilter.doFilter(SpanFinishingFilter.java:55)
at io.undertow.servlet.core.ManagedFilter.doFilter(ManagedFilter.java:61)
at io.undertow.servlet.handlers.FilterHandler$FilterChainImpl.doFilter(FilterHandler.java:131)
at io.undertow.servlet.handlers.FilterHandler.handleRequest(FilterHandler.java:84)
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at io.undertow.servlet.handlers.ServletChain$1.handleRequest(ServletChain.java:68)
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:132)
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46)
at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64)
at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60)
at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77)
at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50)
at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at org.wildfly.extension.undertow.deployment.GlobalRequestControllerHandler.handleRequest(GlobalRequestControllerHandler.java:68)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:292)
at io.undertow.servlet.handlers.ServletInitialHandler.access$100(ServletInitialHandler.java:81)
at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:138)
at io.undertow.servlet.handlers.ServletInitialHandler$2.call(ServletInitialHandler.java:135)
at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:272)
at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81)
at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:104)
at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalArgumentException: Previously registered metric statsHits was not flagged as reusable
at io.smallrye.metrics.MetricsRegistryImpl.get(MetricsRegistryImpl.java:219)
at io.smallrye.metrics.MetricsRegistryImpl.counter(MetricsRegistryImpl.java:155)
at org.eclipse.microprofile.metrics.MetricRegistry$Proxy$_$$_WeldClientProxy.counter(Unknown Source)
at com.sebastian_daschner.hello_prometheus.CoffeesResource.getTotalDonations(CoffeesResource.java:128)
at com.sebastian_daschner.hello_prometheus.CoffeesResource$Proxy$_$$_WeldSubclass.getTotalDonations(Unknown Source)
at com.sebastian_daschner.hello_prometheus.CoffeesResource$Proxy$_$$_WeldClientProxy.getTotalDonations(Unknown Source)
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.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139)
at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:509)
at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:399)
at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$0(ResourceMethodInvoker.java:363)
at org.jboss.resteasy.core.interception.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:355)
at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:365)
at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:337)
at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:310)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:439)
... 55 more
> Counter - registry.counter(metadata)- IllegalArgumentException
> --------------------------------------------------------------
>
> Key: WFLY-11475
> URL: https://issues.jboss.org/browse/WFLY-11475
> Project: WildFly
> Issue Type: Bug
> Components: MP Metrics
> Affects Versions: 15.0.0.Final
> Reporter: Rostislav Svoboda
> Assignee: Bartosz Baranowski
> Priority: Critical
>
> Counter - registry.counter(metadata) returns IllegalArgumentException on second invocation of the endpoint. The same app works fine on Open Liberty.
> JavaDoc for counter(Metadata metadata) says @return a new or pre-existing @link Counter.
> Second invocation should return the pre-existing counter.
> https://github.com/smallrye/smallrye-metrics/issues/43
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3370) Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
by Marek Novotny (Jira)
[ https://issues.jboss.org/browse/DROOLS-3370?page=com.atlassian.jira.plugi... ]
Marek Novotny commented on DROOLS-3370:
---------------------------------------
this is a duplicate, linking and closing as follow up
> Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
> -------------------------------------------------------------------------
>
> Key: DROOLS-3370
> URL: https://issues.jboss.org/browse/DROOLS-3370
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.14.0.Final, 7.15.0.Final
> Environment: JBoss Developer Studio 12.0 and Eclipse 12
> Reporter: Mister PM
> Assignee: Ant Stephenson
> Priority: Minor
> Fix For: 7.14.0.Final
>
>
> When you try to use the quick start from the catalog or create any kjar project the kie-maven-plugin is not recognised therefore project is not building by Eclipse, even if you try to build from command line and refresh, eclipse don't pick up forcing you to include a workaround in the pom file.
> <pluginManagement>
> <plugins>
> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
> <plugin>
> <groupId>org.eclipse.m2e</groupId>
> <artifactId>lifecycle-mapping</artifactId>
> <version>1.0.0</version>
> <configuration>
> <lifecycleMappingMetadata>
> <pluginExecutions>
> <pluginExecution>
> <pluginExecutionFilter>
> <groupId>org.kie</groupId>
> <artifactId>
> kie-maven-plugin
> </artifactId>
> <versionRange>
> [7.14.0.Final,)
> </versionRange>
> <goals>
> <goal>build</goal>
> <goal>generateDMNModel</goal>
> </goals>
> </pluginExecutionFilter>
> <action>
> <ignore></ignore>
> </action>
> </pluginExecution>
> </pluginExecutions>
> </lifecycleMappingMetadata>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> This is not necessary on other IDEs
> This will also affect customer which use workbench to start they project and pull this to eclipse later on.
> JBoss Developer Studio engineer pointed out this problem is an Issue is with the invalid M2E metadata in the downstream kie-maven-plugin as you can see in the jira below
> https://issues.jboss.org/browse/JBDS-4745
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3370) Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
by Marek Novotny (Jira)
[ https://issues.jboss.org/browse/DROOLS-3370?page=com.atlassian.jira.plugi... ]
Marek Novotny closed DROOLS-3370.
---------------------------------
Fix Version/s: 7.14.0.Final
Resolution: Duplicate Issue
> Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
> -------------------------------------------------------------------------
>
> Key: DROOLS-3370
> URL: https://issues.jboss.org/browse/DROOLS-3370
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.14.0.Final, 7.15.0.Final
> Environment: JBoss Developer Studio 12.0 and Eclipse 12
> Reporter: Mister PM
> Assignee: Ant Stephenson
> Priority: Minor
> Fix For: 7.14.0.Final
>
>
> When you try to use the quick start from the catalog or create any kjar project the kie-maven-plugin is not recognised therefore project is not building by Eclipse, even if you try to build from command line and refresh, eclipse don't pick up forcing you to include a workaround in the pom file.
> <pluginManagement>
> <plugins>
> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
> <plugin>
> <groupId>org.eclipse.m2e</groupId>
> <artifactId>lifecycle-mapping</artifactId>
> <version>1.0.0</version>
> <configuration>
> <lifecycleMappingMetadata>
> <pluginExecutions>
> <pluginExecution>
> <pluginExecutionFilter>
> <groupId>org.kie</groupId>
> <artifactId>
> kie-maven-plugin
> </artifactId>
> <versionRange>
> [7.14.0.Final,)
> </versionRange>
> <goals>
> <goal>build</goal>
> <goal>generateDMNModel</goal>
> </goals>
> </pluginExecutionFilter>
> <action>
> <ignore></ignore>
> </action>
> </pluginExecution>
> </pluginExecutions>
> </lifecycleMappingMetadata>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> This is not necessary on other IDEs
> This will also affect customer which use workbench to start they project and pull this to eclipse later on.
> JBoss Developer Studio engineer pointed out this problem is an Issue is with the invalid M2E metadata in the downstream kie-maven-plugin as you can see in the jira below
> https://issues.jboss.org/browse/JBDS-4745
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3236) Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
by Marek Novotny (Jira)
[ https://issues.jboss.org/browse/DROOLS-3236?page=com.atlassian.jira.plugi... ]
Marek Novotny updated DROOLS-3236:
----------------------------------
Fix Version/s: 7.14.0.Final
> Unable to open KJAR project in eclipse due to "Missing parameter for pluginExecutionFilter"
> -------------------------------------------------------------------------------------------
>
> Key: DROOLS-3236
> URL: https://issues.jboss.org/browse/DROOLS-3236
> Project: Drools
> Issue Type: Bug
> Components: tools
> Affects Versions: 7.10.0.Final, 7.11.0.Final, 7.12.0.Final, 7.13.0.Final
> Environment: Eclipse photon, Eclipse 2018 09, no special plugin
> m2eclipse configured to do-not-manage/ignore any unknown plugin goal (easiest choice)
> Reporter: Matteo Mortari
> Assignee: Massimiliano Dessi
> Priority: Major
> Fix For: 7.14.0.Final
>
> Attachments: image-2018-11-05-10-28-50-255.png
>
>
> Since 7.10.0.Final the following error occurs when opening a KJAR project in Eclipse:
> !image-2018-11-05-10-28-50-255.png!
> Errors occurred during the build.
> Errors running builder 'Maven Project Builder' on project '...'.
> Missing parameter for pluginExecutionFilter. groupId, artifactId, versionRange and goals must be specificed, but found: groupId = 'org.kie'
> artifactId = 'kie-maven-plugin'
> versionRange = '7.10.0.Final'
> goals = '[]'
> Please notice kie-maven-plugin 7.9.0.Final and earlier do NOT exhibit this issue.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3370) Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
by Matteo Mortari (Jira)
[ https://issues.jboss.org/browse/DROOLS-3370?page=com.atlassian.jira.plugi... ]
Matteo Mortari commented on DROOLS-3370:
----------------------------------------
[~anstephe] I believe this JIRA can be closed, as it's solved on [DROOLS-3236]. Can you kindly verify.
> Issue is with the invalid M2E metadata in the downstream kie-maven-plugin
> -------------------------------------------------------------------------
>
> Key: DROOLS-3370
> URL: https://issues.jboss.org/browse/DROOLS-3370
> Project: Drools
> Issue Type: Bug
> Components: build
> Affects Versions: 7.14.0.Final, 7.15.0.Final
> Environment: JBoss Developer Studio 12.0 and Eclipse 12
> Reporter: Mister PM
> Assignee: Ant Stephenson
> Priority: Minor
>
> When you try to use the quick start from the catalog or create any kjar project the kie-maven-plugin is not recognised therefore project is not building by Eclipse, even if you try to build from command line and refresh, eclipse don't pick up forcing you to include a workaround in the pom file.
> <pluginManagement>
> <plugins>
> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
> <plugin>
> <groupId>org.eclipse.m2e</groupId>
> <artifactId>lifecycle-mapping</artifactId>
> <version>1.0.0</version>
> <configuration>
> <lifecycleMappingMetadata>
> <pluginExecutions>
> <pluginExecution>
> <pluginExecutionFilter>
> <groupId>org.kie</groupId>
> <artifactId>
> kie-maven-plugin
> </artifactId>
> <versionRange>
> [7.14.0.Final,)
> </versionRange>
> <goals>
> <goal>build</goal>
> <goal>generateDMNModel</goal>
> </goals>
> </pluginExecutionFilter>
> <action>
> <ignore></ignore>
> </action>
> </pluginExecution>
> </pluginExecutions>
> </lifecycleMappingMetadata>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> This is not necessary on other IDEs
> This will also affect customer which use workbench to start they project and pull this to eclipse later on.
> JBoss Developer Studio engineer pointed out this problem is an Issue is with the invalid M2E metadata in the downstream kie-maven-plugin as you can see in the jira below
> https://issues.jboss.org/browse/JBDS-4745
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months