October 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1326) Stateful working memory regression OCT-2016: nurserostering long_hint01.xml

by Jiri Locker (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1326?page=com.atlassian.jira.plugi... ] Jiri Locker commented on DROOLS-1326: ------------------------------------- [~ge0ffrey], I can't reproduce locally with current master. I invoke {noformat} mvn test -DrunTurtleTests -Dtest=NurseRosteringSolveAllTurtleTest {noformat} I also checked out commits from the date when the failed Jenkins build was launched and it didn't help. I suggest re-running the job. If it fails again, either I or the job does something wrong. Any other ideas? > Stateful working memory regression OCT-2016: nurserostering long_hint01.xml > --------------------------------------------------------------------------- > > Key: DROOLS-1326 > URL: https://issues.jboss.org/browse/DROOLS-1326 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta2 > Reporter: Geoffrey De Smet > Assignee: Mario Fusco > Priority: Blocker > > Something regressed in Drools master between 27-SEP and 11-OCT. > See: > https://kie-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/optaplanner-turtl... > I 'll ask [~jlocker] to isolate. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7313) Impossible to use environment variables or system properties in permissions.xml

by Adrian Boangiu (JIRA)

Adrian Boangiu created WFLY-7313: ------------------------------------ Summary: Impossible to use environment variables or system properties in permissions.xml Key: WFLY-7313 URL: https://issues.jboss.org/browse/WFLY-7313 Project: WildFly Issue Type: Feature Request Affects Versions: 10.1.0.Final Reporter: Adrian Boangiu Assignee: Jason Greene Priority: Blocker Fix For: 10.2.0.Final, 10.1.0.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1330) Events already expired at insertion time don't have a chance to produce a match

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1330: ----------------------------------- Summary: Events already expired at insertion time don't have a chance to produce a match Key: DROOLS-1330 URL: https://issues.jboss.org/browse/DROOLS-1330 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco When flushing the insertion of an event that is already expired at processing (firing) time it is required that the event should however have at least a chance to produce joins and activations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1329) Events already expired at insertion time don't have a chance to produce a match

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-1329: ----------------------------------- Summary: Events already expired at insertion time don't have a chance to produce a match Key: DROOLS-1329 URL: https://issues.jboss.org/browse/DROOLS-1329 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco When flushing the insertion of an event that is already expired at processing (firing) time it is required that the event should however have at least a chance to produce joins and activations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-661) Add ability to match URI path by pattern or other partial match

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-661?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-661. ----------------------------- Resolution: Rejected Actually the current path matcher is already a prefix matcher. Reopen if we want to add in an exact-only matcher. > Add ability to match URI path by pattern or other partial match > --------------------------------------------------------------- > > Key: ELY-661 > URL: https://issues.jboss.org/browse/ELY-661 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta11 > > > Path matching in the authentication client only matches the whole path which is not ideal. We need the ability to match paths by prefix and/or wildcard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-661) Add ability to match URI path by pattern or other partial match

by David Lloyd (JIRA)

David Lloyd created ELY-661: ------------------------------- Summary: Add ability to match URI path by pattern or other partial match Key: ELY-661 URL: https://issues.jboss.org/browse/ELY-661 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.1.0.Beta11 Path matching in the authentication client only matches the whole path which is not ideal. We need the ability to match paths by prefix and/or wildcard. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1328) CEP KieSession deserialization NullPointerException with Timer and expiration

by andrea tarocchi (JIRA)

andrea tarocchi created DROOLS-1328: --------------------------------------- Summary: CEP KieSession deserialization NullPointerException with Timer and expiration Key: DROOLS-1328 URL: https://issues.jboss.org/browse/DROOLS-1328 Project: Drools Issue Type: Bug Affects Versions: 7.0.0.Beta2 Reporter: andrea tarocchi Assignee: Mario Fusco Priority: Critical When a Cep KieSession containing events with expiration is serialized and then deserialized there is a NullPointerExceptions is thrown: {code:java} java.lang.NullPointerException at org.drools.core.reteoo.ObjectTypeNode$ExpireJobContextTimerInputMarshaller.deserialize(ObjectTypeNode.java:672) at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readTimer(ProtobufInputMarshaller.java:709) at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:291) at org.drools.core.marshalling.impl.ProtobufInputMarshaller.readSession(ProtobufInputMarshaller.java:162) at org.drools.core.marshalling.impl.ProtobufMarshaller.unmarshall(ProtobufMarshaller.java:116) at org.drools.core.marshalling.impl.ProtobufMarshaller.unmarshall(ProtobufMarshaller.java:52) at org.drools.compiler.integrationtests.CepEspTest$1KieSessionByteArraySerializer.readSession(CepEspTest.java:220) at org.drools.compiler.integrationtests.CepEspTest.testSerializationDeserliaizationWithRectractedExpireFact(CepEspTest.java:253) 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:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.lang.Thread.run(Thread.java:745) {code} you have a reproducer in PR: https://github.com/droolsjbpm/drools/pull/959 Just run: {code:bash} cd drools-compiler mvn clean test -Dtest=CepEspTest#testSerializationDeserliaizationWithRectractedExpireFact {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ] Filippe Spolti updated WFLY-7309: --------------------------------- Description: Actually some tests cases fails when running against a remote eap instance. In this specific case instances running on Openshift v3. In order to get those tests working we have to modify some classes to configure the authentication. Example: org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this: {code:java} private MBeanServerConnection getMBeanServerConnection() throws IOException { final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address)); return connector.getMBeanServerConnection(); } {code} To: {code:java} private MBeanServerConnection getMBeanServerConnection() throws IOException { HashMap<String, String[]> propEnv = new HashMap<String, String[]>(); String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") }; propEnv.put(JMXConnector.CREDENTIALS, credentials); final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv); return connector.getMBeanServerConnection(); } {code} Could these kind of authentication being configurable? It is important to us because this allows the tests to be executed against the docker images running in openshift. was: Actually some tests cases of EAP's testsuite failes when running against a remote eap instance. In this specific case, EAP 6/7 instances running on Openshift v3. In order to get those tests working we have to modify some classes to configure the authentication. Example: org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this: {code:java} private MBeanServerConnection getMBeanServerConnection() throws IOException { final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address)); return connector.getMBeanServerConnection(); } {code} To: {code:java} private MBeanServerConnection getMBeanServerConnection() throws IOException { HashMap<String, String[]> propEnv = new HashMap<String, String[]>(); String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") }; propEnv.put(JMXConnector.CREDENTIALS, credentials); final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv); return connector.getMBeanServerConnection(); } {code} Could these kind of authentication being configurable? It is important to us because this allows the tests to be executed against the docker images running in openshift. > Make the authentication configurable in the eap testsuite > ---------------------------------------------------------- > > Key: WFLY-7309 > URL: https://issues.jboss.org/browse/WFLY-7309 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Filippe Spolti > Assignee: Filippe Spolti > Priority: Optional > > Actually some tests cases fails when running against a remote eap instance. > In this specific case instances running on Openshift v3. > In order to get those tests working we have to modify some classes to configure the authentication. > Example: > org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this: > {code:java} > private MBeanServerConnection getMBeanServerConnection() throws IOException { > final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); > connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address)); > return connector.getMBeanServerConnection(); > } > {code} > To: > {code:java} > private MBeanServerConnection getMBeanServerConnection() throws IOException { > HashMap<String, String[]> propEnv = new HashMap<String, String[]>(); > String[] credentials = { System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") }; > propEnv.put(JMXConnector.CREDENTIALS, credentials); > final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort(); > connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv); > return connector.getMBeanServerConnection(); > } > {code} > Could these kind of authentication being configurable? > It is important to us because this allows the tests to be executed against the docker images running in openshift. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central

by Josef Ludvicek (JIRA)

[ https://issues.jboss.org/browse/WFLY-7312?page=com.atlassian.jira.plugin.... ] Josef Ludvicek updated WFLY-7312: --------------------------------- Description: {{wildfly-parent}} BOM is present in maven central, but itt's {{dependenciesManagement}} section specifies certain dependencies, which were not published to central and hence breaking the build. For example {code:xml} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.fuse.qa</groupId> <artifactId>slf4j-reproducer</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencyManagement> <dependencies> <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-parent</artifactId> <version>10.1.0.Final</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.arquillian.cube</groupId> <artifactId>arquillian-cube-docker</artifactId> <version>1.0.0.Alpha15</version> <scope>test</scope> </dependency> </dependencies> </project> {code} fails: {code} [ERROR] Failed to execute goal on project slf4j-reproducer: Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1: Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] {code} There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/. Shouldn't we publish all required artifacts to central to avoid similar problems in future ? was: {{wildfly-parent}} BOM is present in maven central, but it specifies certain dependencies, which were not published to central and hence breaking the build. For example {code:xml} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.fuse.qa</groupId> <artifactId>slf4j-reproducer</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencyManagement> <dependencies> <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-parent</artifactId> <version>10.1.0.Final</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.arquillian.cube</groupId> <artifactId>arquillian-cube-docker</artifactId> <version>1.0.0.Alpha15</version> <scope>test</scope> </dependency> </dependencies> </project> {code} fails: {code} [ERROR] Failed to execute goal on project slf4j-reproducer: Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1: Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] {code} There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/. Shouldn't we publish all required artifacts to central to avoid similar problems in future ? > wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central > -------------------------------------------------------------------------------------- > > Key: WFLY-7312 > URL: https://issues.jboss.org/browse/WFLY-7312 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Reporter: Josef Ludvicek > Assignee: Jason Greene > > {{wildfly-parent}} BOM is present in maven central, > but itt's {{dependenciesManagement}} section specifies certain dependencies, which were not published to central and hence breaking the build. > For example > {code:xml} > <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.jboss.fuse.qa</groupId> > <artifactId>slf4j-reproducer</artifactId> > <version>0.0.1-SNAPSHOT</version> > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.wildfly</groupId> > <artifactId>wildfly-parent</artifactId> > <version>10.1.0.Final</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > <dependencies> > <dependency> > <groupId>org.arquillian.cube</groupId> > <artifactId>arquillian-cube-docker</artifactId> > <version>1.0.0.Alpha15</version> > <scope>test</scope> > </dependency> > </dependencies> > </project> > {code} > fails: > {code} > [ERROR] Failed to execute goal on project slf4j-reproducer: > Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT: > The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1: > Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1] > [ERROR] > {code} > There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/. > Shouldn't we publish all required artifacts to central to avoid similar problems in future ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central

by Josef Ludvicek (JIRA)

Josef Ludvicek created WFLY-7312: ------------------------------------ Summary: wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central Key: WFLY-7312 URL: https://issues.jboss.org/browse/WFLY-7312 Project: WildFly Issue Type: Bug Reporter: Josef Ludvicek Assignee: Jason Greene {{wildfly-parent}} BOM is present in maven central, but it specifies certain dependencies, which were not published to central and hence breaking the build. For example {code:xml} <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.fuse.qa</groupId> <artifactId>slf4j-reproducer</artifactId> <version>0.0.1-SNAPSHOT</version> <dependencyManagement> <dependencies> <dependency> <groupId>org.wildfly</groupId> <artifactId>wildfly-parent</artifactId> <version>10.1.0.Final</version> <scope>import</scope> <type>pom</type> </dependency> </dependencies> </dependencyManagement> <dependencies> <dependency> <groupId>org.arquillian.cube</groupId> <artifactId>arquillian-cube-docker</artifactId> <version>1.0.0.Alpha15</version> <scope>test</scope> </dependency> </dependencies> </project> {code} fails: {code} [ERROR] Failed to execute goal on project slf4j-reproducer: Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT: The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1: Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1] [ERROR] {code} There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/. Shouldn't we publish all required artifacts to central to avoid similar problems in future ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 3 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 October 2016