August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1696) Events that are already expired at insert time, doesn't always produce activations

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1696?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1696: --------------------------------------- PR with a reproducer here: https://github.com/kiegroup/drools/pull/1410 > Events that are already expired at insert time, doesn't always produce activations > ---------------------------------------------------------------------------------- > > Key: DROOLS-1696 > URL: https://issues.jboss.org/browse/DROOLS-1696 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Fix For: 7.2.0.Final > > > When inserting events that have timestamp in the past and don't have expiration defined (@expires), the events don't always produce activations. See a test example [1]. This test fails "randomly". > I will create a PR with a reproducer. > [1] https://gist.github.com/baldimir/fb9808ce1e6d49c83dc24570b3cb6093 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1696) Events that are already expired at insert time, doesn't always produce activations

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-1696: ------------------------------------- Summary: Events that are already expired at insert time, doesn't always produce activations Key: DROOLS-1696 URL: https://issues.jboss.org/browse/DROOLS-1696 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.1.0.Final Reporter: Tibor Zimányi Assignee: Mario Fusco Fix For: 7.2.0.Final When inserting events that have timestamp in the past and don't have expiration defined (@expires), the events don't always produce activations. See a test example [1]. This test fails "randomly". I will create a PR with a reproducer. [1] https://gist.github.com/baldimir/fb9808ce1e6d49c83dc24570b3cb6093 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-9195: ------------------------------ Affects Version/s: 11.0.0.Beta1 > Quickstart guide: helloworld is not working > ------------------------------------------- > > Key: WFLY-9195 > URL: https://issues.jboss.org/browse/WFLY-9195 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 11.0.0.Beta1 > Reporter: Julien Dore > Assignee: Tomaz Cerar > Priority: Minor > > I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. > With my wildfly server running i'm launching (from quickstart-11.x/helloworld): > {code:java} > package wildfly:deploy > {code} > as describe in the doc but this fail with the following stack: > {code:java} > [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] > {code} > Adding the following code in pom.xml solve the issue: > {code:java} > <plugin> > <groupId>org.wildfly.plugins</groupId> > <artifactId>wildfly-maven-plugin</artifactId> > <version>1.1.0.Final</version> > </plugin> > {code} > Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. > Note also that these links are not working: > * Installing and starting the JBoss server on Linux, Unix or Mac OS X > * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-9195: ------------------------------ Component/s: Quickstarts (was: Documentation) > Quickstart guide: helloworld is not working > ------------------------------------------- > > Key: WFLY-9195 > URL: https://issues.jboss.org/browse/WFLY-9195 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Julien Dore > Priority: Minor > > I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. > With my wildfly server running i'm launching (from quickstart-11.x/helloworld): > {code:java} > package wildfly:deploy > {code} > as describe in the doc but this fail with the following stack: > {code:java} > [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] > {code} > Adding the following code in pom.xml solve the issue: > {code:java} > <plugin> > <groupId>org.wildfly.plugins</groupId> > <artifactId>wildfly-maven-plugin</artifactId> > <version>1.1.0.Final</version> > </plugin> > {code} > Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. > Note also that these links are not working: > * Installing and starting the JBoss server on Linux, Unix or Mac OS X > * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9195?page=com.atlassian.jira.plugin.... ] Tomaz Cerar reassigned WFLY-9195: --------------------------------- Assignee: Tomaz Cerar > Quickstart guide: helloworld is not working > ------------------------------------------- > > Key: WFLY-9195 > URL: https://issues.jboss.org/browse/WFLY-9195 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Reporter: Julien Dore > Assignee: Tomaz Cerar > Priority: Minor > > I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. > With my wildfly server running i'm launching (from quickstart-11.x/helloworld): > {code:java} > package wildfly:deploy > {code} > as describe in the doc but this fail with the following stack: > {code:java} > [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] > {code} > Adding the following code in pom.xml solve the issue: > {code:java} > <plugin> > <groupId>org.wildfly.plugins</groupId> > <artifactId>wildfly-maven-plugin</artifactId> > <version>1.1.0.Final</version> > </plugin> > {code} > Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. > Note also that these links are not working: > * Installing and starting the JBoss server on Linux, Unix or Mac OS X > * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9143) Don't override global operations unless operation transformer was actually defined

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9143?page=com.atlassian.jira.plugin.... ] Paul Ferraro closed WFLY-9143. ------------------------------ Resolution: Out of Date > Don't override global operations unless operation transformer was actually defined > ---------------------------------------------------------------------------------- > > Key: WFLY-9143 > URL: https://issues.jboss.org/browse/WFLY-9143 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > This was requested by [~ctomc]. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9192) InfinispanLogger executorIgnored() has no effect

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-9192?page=com.atlassian.jira.plugin.... ] Paul Ferraro reassigned WFLY-9192: ---------------------------------- Assignee: Radoslav Husar (was: Paul Ferraro) > InfinispanLogger executorIgnored() has no effect > ------------------------------------------------ > > Key: WFLY-9192 > URL: https://issues.jboss.org/browse/WFLY-9192 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Brian Stansberry > Assignee: Radoslav Husar > > The method isn't an @LogMessage method and its return value is unused. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9195) Quickstart guide: helloworld is not working

by Julien Dore (JIRA)

Julien Dore created WFLY-9195: --------------------------------- Summary: Quickstart guide: helloworld is not working Key: WFLY-9195 URL: https://issues.jboss.org/browse/WFLY-9195 Project: WildFly Issue Type: Bug Components: Documentation Reporter: Julien Dore Priority: Minor I'm following the [quickstart guide|https://github.com/wildfly/quickstart/blob/10.x/guide/HelloworldQui...] and i have downloaded the quickstart-11.x. With my wildfly server running i'm launching (from quickstart-11.x/helloworld): {code:java} package wildfly:deploy {code} as describe in the doc but this fail with the following stack: {code:java} [ERROR] No plugin found for prefix 'wildfly' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (C:\Users\PC\.m2\repository), jboss-enterprise-maven-repository (https://maven.repository.redhat.com/ga/), jboss-enterprise-maven-repository-ea (https://maven.repository.redhat.com/earlyaccess/all/), jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/), central (https://repo.maven.apache.org/maven2)] -> [Help 1] {code} Adding the following code in pom.xml solve the issue: {code:java} <plugin> <groupId>org.wildfly.plugins</groupId> <artifactId>wildfly-maven-plugin</artifactId> <version>1.1.0.Final</version> </plugin> {code} Note that the application is then accessible at _http://localhost:8080/helloworld/HelloWorld_ and not _http://localhost:8080/wildfly-helloworld/HelloWorld_ as written in the documentation. Note also that these links are not working: * Installing and starting the JBoss server on Linux, Unix or Mac OS X * Installing and starting the JBoss server on Windows -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9194) WeldLogger.componentInterceptorSupportNotAvailable returns an Exception that is never used

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9194?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9194: ----------------------------------- Description: Most likely the caller is forgetting to throw the exception. WeldLogger.componentInterceptorSupportNotAvailable WeldEjbLogger.ejbHashBeenRemoved was:Most likely the caller is forgetting to throw the exception. > WeldLogger.componentInterceptorSupportNotAvailable returns an Exception that is never used > ------------------------------------------------------------------------------------------ > > Key: WFLY-9194 > URL: https://issues.jboss.org/browse/WFLY-9194 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > Most likely the caller is forgetting to throw the exception. > WeldLogger.componentInterceptorSupportNotAvailable > WeldEjbLogger.ejbHashBeenRemoved -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9194) WeldLogger and WeldEjbLogger return an Exception that is never used

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9194?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9194: ----------------------------------- Summary: WeldLogger and WeldEjbLogger return an Exception that is never used (was: WeldLogger.componentInterceptorSupportNotAvailable returns an Exception that is never used) > WeldLogger and WeldEjbLogger return an Exception that is never used > ------------------------------------------------------------------- > > Key: WFLY-9194 > URL: https://issues.jboss.org/browse/WFLY-9194 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Brian Stansberry > Assignee: Stuart Douglas > > Most likely the caller is forgetting to throw the exception. > WeldLogger.componentInterceptorSupportNotAvailable > WeldEjbLogger.ejbHashBeenRemoved -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 August 2017