October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-475) Bookinfo installation fails on B12

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-475?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-475: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > Bookinfo installation fails on B12 > ---------------------------------- > > Key: SWSQE-475 > URL: https://issues.jboss.org/browse/SWSQE-475 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Guilherme Baufaker Rêgo > Priority: Blocker > > Hi Guilherme, > Could you please take a look into this failure: > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/install-bookinfo... > Thanks, > Hayk -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11265) wildfly-feature-pack -- Dependency Error

by Dennis Gesker (Jira)

Dennis Gesker created WFLY-11265: ------------------------------------ Summary: wildfly-feature-pack -- Dependency Error Key: WFLY-11265 URL: https://issues.jboss.org/browse/WFLY-11265 Project: WildFly Issue Type: Bug Affects Versions: 14.0.0.Final Environment: Ubuntu 18.10 JDK 11 WildFly 14.0.1.Final Reporter: Dennis Gesker Assignee: Jason Greene Fix For: 14.0.0.Final In my gradle build I've added: * providedCompile "org.wildfly:wildfly-feature-pack:14.0.1.Final"* But, I'm getting: *> Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. Required by: project : > org.wildfly:wildfly-feature-pack:14.0.1.Final > org.glassfish.soteria:javax.security.enterprise:1.0* > Could not resolve javax.security.enterprise:javax.security.enterprise-api:1.1-b01-SNAPSHOT. > Unable to load Maven meta-data from https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu.... > Could not get resource 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > Could not GET 'https://repository.jboss.org/nexus/content/groups/public-jboss/javax/secu...'. > extension (10) should not be presented in server_hello Presently I have the following repositories in my build: jcenter() mavenCentral() maven { name "Gradle Repository" url "https://plugins.gradle.org/m2/" } maven { name "JBoss Public Maven Repository Group" url "https://repository.jboss.org/nexus/content/groups/public-jboss/" } maven { name "JBoss Public Maven Repository Group" url "http://repository.jboss.org/nexus/content/groups/public/" } But, I suspect I am missing a repository specific to WildFly. Or, maybe there is a bad entry in the POM? Thanks, Dennis -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3214: ----------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type > - Function parameter is simple data type > - Multiple parameters -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-10654) In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container.

by Chao Wang (Jira)

[ https://issues.jboss.org/browse/WFLY-10654?page=com.atlassian.jira.plugin... ] Chao Wang reassigned WFLY-10654: -------------------------------- Assignee: (was: Chao Wang) > In WFLY 13 when you deploy a simple Jar file , WFLY 13 treats the jar as the EJB and starts the "ejb" cache container. > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-10654 > URL: https://issues.jboss.org/browse/WFLY-10654 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 13.0.0.Final > Reporter: Chao Wang > Priority: Major > > Deployment(from management console) of a simple Jar file in EAP 7.1.x causes the ejb cache container to start , which should not be the case . > From EAP 7.1.x onwards @clustered annotation has been depricated and EJB application is required to start clustering , but in contradiction to this even if we deploy ant jar file (let's say ojdbc6.jar ) the container treats it as an EJB application and starts the EJB cache container as seen in the logs below : > ~~~~ > 1,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-1) ISPN000078: Starting JGroups channel ejb > 22:14:21,640 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000078: Starting JGroups channel ejb > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,673 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [plohia|0] (1) [plohia] > 22:14:21,676 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > 22:14:21,678 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-8) ISPN000079: Channel ejb local address is plohia, physical addresses are [192.168.122.1:55200] > ~~~~ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3106) Create a start.drools.org website

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-3106?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-3106: ------------------------------------- poker: 8 > Create a start.drools.org website > --------------------------------- > > Key: DROOLS-3106 > URL: https://issues.jboss.org/browse/DROOLS-3106 > Project: Drools > Issue Type: Task > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > > Create a start website for Drools similar to what has been done for jBPM here: https://start.jbpm.org/ > Source code of jbpm web site are available here: https://start.jbpm.org/ -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type - Function parameter is simple data type - Multiple parameters was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type > - Function parameter is simple data type > - Multiple parameters -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] - Function parameter is custom data type was: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] > - Function parameter is custom data type -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3214) [DMN Designer] Function: Add parameter data-types

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3214?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3214: -------------------------------- Description: Our "Function Grid" does not support data-types for parameters... it should! h2. Acceptance test - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] was:Our "Function Grid" does not support data-types for parameters... it should! > [DMN Designer] Function: Add parameter data-types > ------------------------------------------------- > > Key: DROOLS-3214 > URL: https://issues.jboss.org/browse/DROOLS-3214 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Our "Function Grid" does not support data-types for parameters... it should! > h2. Acceptance test > - Create model like used in [PR|https://github.com/kiegroup/drools/pull/2123] -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11264) The BatchJobExecutionResource.hasChild() needs to be reviewed for purged jobs

by James Perkins (Jira)

James Perkins created WFLY-11264: ------------------------------------ Summary: The BatchJobExecutionResource.hasChild() needs to be reviewed for purged jobs Key: WFLY-11264 URL: https://issues.jboss.org/browse/WFLY-11264 Project: WildFly Issue Type: Bug Components: Batch Reporter: James Perkins Assignee: Cheng Fang The {{BatchJobExecutionResource.hasChild()}} invokes the {{hasJobExecution()}} method which does not by default refresh the children. This could mean that a purged job returns {{true}} when it should be {{false}}. This was originally done for performance reasons however there is a bug (WFLY-11261) which causes issues when a job is purged. In general this resource should be reviewed and performance tested to ensure purged jobs no longer show up. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11146) org.apache.activemq.artemis.journal module should not depend on org.apache.activemq.artemis

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11146?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet reassigned WFLY-11146: ---------------------------------------- Assignee: ehsavoie Hugonnet (was: Jeff Mesnil) > org.apache.activemq.artemis.journal module should not depend on org.apache.activemq.artemis > ------------------------------------------------------------------------------------------- > > Key: WFLY-11146 > URL: https://issues.jboss.org/browse/WFLY-11146 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final > Reporter: Jeff Mesnil > Assignee: ehsavoie Hugonnet > Priority: Major > > While looking at Weld dependency, Jean-Francois found the dependency chain: > /org.jboss.as.weld/org.jboss.weld.core/javax.ejb.api/javax.rmi.api/javax.orb.api/org.wildfly.iiop-openjdk/org.jboss.jts/org.apache.activemq.artemis.journal/org.apache.activemq.artemis > org.jboss.jts dependency to org.apache.activemq.artemis.journal is correct as Naryana uses Artemis journal for its transaction log. > However org.apache.activemq.artemis.journal should not depend on org.apache.activemq.artemis. It depends on it for the artemis-commons jar (as explained in https://github.com/wildfly/wildfly/blob/47b1db08fadb745706df7ba411db4f725... but code should be refactored so that this dependency is no longer required). -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018