March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-656) Migrate repos from kiali-qe group to istio

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-656?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-656: ------------------------------------- jenkins repo migrated: https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-jenkins-dsl > Migrate repos from kiali-qe group to istio > ------------------------------------------ > > Key: SWSQE-656 > URL: https://issues.jboss.org/browse/SWSQE-656 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > We want to move https://gitlab.cee.redhat.com/kiali-qe repos to https://gitlab.cee.redhat.com/istio/kiali-qe -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in constraint

by Hiroko Miura (Jira)

[ https://issues.jboss.org/browse/DROOLS-3800?page=com.atlassian.jira.plugi... ] Hiroko Miura updated DROOLS-3800: --------------------------------- Summary: Parser error with executable-model on Map literal expression in constraint (was: Parser error with executable-model on Map literal expression in costraint) > Parser error with executable-model on Map literal expression in constraint > -------------------------------------------------------------------------- > > Key: DROOLS-3800 > URL: https://issues.jboss.org/browse/DROOLS-3800 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.18.0.Final > Environment: 7.18.0.Final > 7.18.0.Final-redhat-00002 (RHDM7.3.0) > 7.14.0.Final-redhat-00004 (RHDM7.1.2) > Reporter: Hiroko Miura > Assignee: Luca Molteni > Priority: Major > Labels: support > Attachments: MapLiteralTest.zip > > > When MAP literal expression is used in LHS like the following > {noformat} > when > $fact: Fact( > calc(["src":name, "target":"TEST"]) > ) > ... > {noformat} > KieBase build as Executable Model fails with parser error like: > {noformat} > org.drools.javaparser.ParseProblemException: > Encountered unexpected token: "[" "[" > at line 1, column 6. > Was expecting one of: > ")" > {noformat} > This error does not happen when building this rule as normal kjar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3801) Parser error with executable-model on Map literal expression in costraint

by Hiroko Miura (Jira)

Hiroko Miura created DROOLS-3801: ------------------------------------ Summary: Parser error with executable-model on Map literal expression in costraint Key: DROOLS-3801 URL: https://issues.jboss.org/browse/DROOLS-3801 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.18.0.Final Environment: 7.18.0.Final 7.18.0.Final-redhat-00002 (RHDM7.3.0) 7.14.0.Final-redhat-00004 (RHDM7.1.2) Reporter: Hiroko Miura Assignee: Luca Molteni Attachments: MapLiteralTest.zip When MAP literal expression is used in LHS like the following {noformat} when $fact: Fact( calc(["src":name, "target":"TEST"]) ) ... {noformat} KieBase build as Executable Model fails with parser error like: {noformat} org.drools.javaparser.ParseProblemException: Encountered unexpected token: "[" "[" at line 1, column 6. Was expecting one of: ")" {noformat} This error does not happen when building this rule as normal kjar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11911) Remove READ_TIMEOUT from cannel configuration options

by Teresa Miyar Gil (Jira)

[ https://issues.jboss.org/browse/WFLY-11911?page=com.atlassian.jira.plugin... ] Teresa Miyar Gil updated WFLY-11911: ------------------------------------ Description: The only configuration options allowed on the channel by the ultimate consumer of the options org.jboss.remoting3.remote.RemoteReadListener are: RemotingOptions.TRANSMIT_WINDOW_SIZE, RemotingOptions.MAX_OUTBOUND_MESSAGES RemotingOptions.RECEIVE_WINDOW_SIZE RemotingOptions.MAX_INBOUND_MESSAGES RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE RemotingOptions.MAX_INBOUND_MESSAGE_SIZE. Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed. was: The only configuration options allowed on the channel are RemotingOptions.TRANSMIT_WINDOW_SIZE, RemotingOptions.MAX_OUTBOUND_MESSAGES RemotingOptions.RECEIVE_WINDOW_SIZE RemotingOptions.MAX_INBOUND_MESSAGES RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE RemotingOptions.MAX_INBOUND_MESSAGE_SIZE. Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed. > Remove READ_TIMEOUT from cannel configuration options > ----------------------------------------------------- > > Key: WFLY-11911 > URL: https://issues.jboss.org/browse/WFLY-11911 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 16.0.0.Final > Reporter: Teresa Miyar Gil > Assignee: Teresa Miyar Gil > Priority: Major > > The only configuration options allowed on the channel by the ultimate consumer of the options org.jboss.remoting3.remote.RemoteReadListener are: > RemotingOptions.TRANSMIT_WINDOW_SIZE, > RemotingOptions.MAX_OUTBOUND_MESSAGES > RemotingOptions.RECEIVE_WINDOW_SIZE > RemotingOptions.MAX_INBOUND_MESSAGES > RemotingOptions.MAX_OUTBOUND_MESSAGE_SIZE > RemotingOptions.MAX_INBOUND_MESSAGE_SIZE. > Standalone.xml/domain.xml file show READ_TIMEOUT as an example option and should be removed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3800) Parser error with executable-model on Map literal expression in costraint

by Hiroko Miura (Jira)

Hiroko Miura created DROOLS-3800: ------------------------------------ Summary: Parser error with executable-model on Map literal expression in costraint Key: DROOLS-3800 URL: https://issues.jboss.org/browse/DROOLS-3800 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.18.0.Final Environment: 7.18.0.Final 7.18.0.Final-redhat-00002 (RHDM7.3.0) 7.14.0.Final-redhat-00004 (RHDM7.1.2) Reporter: Hiroko Miura Assignee: Luca Molteni Attachments: MapLiteralTest.zip When MAP literal expression is used in LHS like the following {noformat} when $fact: Fact( calc(["src":name, "target":"TEST"]) ) ... {noformat} KieBase build as Executable Model fails with parser error like: {noformat} org.drools.javaparser.ParseProblemException: Encountered unexpected token: "[" "[" at line 1, column 6. Was expecting one of: ")" {noformat} This error does not happen when building this rule as normal kjar. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11914) Upgrade wildfly-http-client to 1.0.14.Final

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-11914: --------------------------------------- Summary: Upgrade wildfly-http-client to 1.0.14.Final Key: WFLY-11914 URL: https://issues.jboss.org/browse/WFLY-11914 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: Brian Stansberry Assignee: Brian Stansberry Depend on a release that depends on JBoss Marshalling 2.0.6 -- See WEJBHTTP-24 and WFLY-11720 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3787) executable-model build failed because trying to resolve test case in Windows

by Toshiya Kobayashi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3787?page=com.atlassian.jira.plugi... ] Toshiya Kobayashi commented on DROOLS-3787: ------------------------------------------- Confirmed that it works with the latest 7.20.0-SNAPSHOT. Thanks! [~volothamp] > executable-model build failed because trying to resolve test case in Windows > ---------------------------------------------------------------------------- > > Key: DROOLS-3787 > URL: https://issues.jboss.org/browse/DROOLS-3787 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.18.0.Final, 7.19.0.Final > Environment: - Windows 2012 > - Windows 7 > Confirmed with some tags > - 7.14.0.Final-redhat-00004 > - 7.18.0.Final > - 7.19.0.Final > - 7.20.0-SNAPSHOT > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > Labels: support > Attachments: with-test-sources-reproducer.zip > > > Under the condition: > - Windows > - executable-model build (mvn clean install -DgenerateModel=YES -DskipTests) > The build tries to resolve java source under "src/test/java" then failed with the error > {noformat} > [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.20.0-SNAPSHOT:generateModel (default-generateModel) on project > with-test-sources: Execution default-generateModel of goal org.kie:kie-maven-plugin:7.20.0-SNAPSHOT:generateModel faile > d: Unable to get KieModule, Errors Existed: Error Messages: > [ERROR] Message [id=1, level=ERROR, path=src/test/java/com/sample/SampleTest.java, line=15, column=372 > [ERROR] text=Only a type can be imported. org.mockito.Mockito resolves to a package] > [ERROR] Message [id=2, level=ERROR, path=src/test/java/com/sample/SampleTest.java, line=22, column=563 > [ERROR] text=Mockito cannot be resolved] > [ERROR] --- > {noformat} > It doesn't happen in MacOS/RHEL7 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11913) JGroups client sockets are not registered with the socket binding manager

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-11913: ----------------------------------- Summary: JGroups client sockets are not registered with the socket binding manager Key: WFLY-11913 URL: https://issues.jboss.org/browse/WFLY-11913 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 16.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Because the JGroups subsystem does not expose a socket-binding for client sockets, these sockets are not registered with the socket binding manager. Currently, TCP, TCP_NIO2, FD_SOCK use the same bind address for server vs client sockets and use a random ephemeral port for configuring the client socket. For environment with strict networking rules, this is not ideal, and requires overriding adhoc JGroups properties. Unfortunately, overriding the client_bind_port in this way does not recognize the port-offset of the associated socket binding group. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4392) Migrate CapabilityServiceTarget to new MSC API

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4392: -------------------------------------- Summary: Migrate CapabilityServiceTarget to new MSC API Key: WFCORE-4392 URL: https://issues.jboss.org/browse/WFCORE-4392 Project: WildFly Core Issue Type: Enhancement Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 9.0.0.Beta2 -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4357) Support new MSC Service API for deployment dependency

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFCORE-4357?page=com.atlassian.jira.plugi... ] Richard Opalka updated WFCORE-4357: ----------------------------------- Fix Version/s: 9.0.0.Beta2 > Support new MSC Service API for deployment dependency > ----------------------------------------------------- > > Key: WFCORE-4357 > URL: https://issues.jboss.org/browse/WFCORE-4357 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jan Stourac > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta2 > > > When org.jboss.as.server.deployment.DeploymentPhaseContextImpl#addDeploymentDependency is used, it is expecting the service to be old-API org.jboss.msc.service.Service and use its getValue() method. > This needs to be fixed so that using new MSC Service API works too. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 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 March 2019