February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11697) WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFLY-11697?page=com.atlassian.jira.plugin... ] Diana Vilkolakova updated WFLY-11697: ------------------------------------- Summary: WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL (was: Revisit WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL) > WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > -------------------------------------------------------------------------------------------- > > Key: WFLY-11697 > URL: https://issues.jboss.org/browse/WFLY-11697 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security, Web Services > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This feature request is about making use of authentication configuration on the client side of the WS / REST deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11670) Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-11670?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-11670: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/12039, https://github.com/wildfly/wildfly/pull/12058 (was: https://github.com/wildfly/wildfly/pull/12058) > Intermittent failures in EJBClientXidTransactionTestCase.testServerSuspension > ----------------------------------------------------------------------------- > > Key: WFLY-11670 > URL: https://issues.jboss.org/browse/WFLY-11670 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Brian Stansberry > Assignee: Yeray Borges > Priority: Major > > Test started failing fairly frequently on Jan 11: > https://ci.wildfly.org/project.html?projectId=WildFlyCore_PullRequest&bui... > https://ci.wildfly.org/project.html?projectId=WF&buildTypeId=&tab=testDet... > Perhaps that was related to https://github.com/wildfly/wildfly/pull/11913 which at a glance was the PR being tested in the first failure and may have been merged that day. So, [~yersan] I'm assigning to you to have a quick look. > I'll @Ignore the test. > For the record, this is the relevant error trace logged by the failed tests: > {noformat} > multinode.transaction.ClientEjb.testSameTransactionEachCall() throws java.rmi.RemoteException,javax.transaction.SystemException,javax.transaction.NotSupportedException,javax.naming.NamingException: javax.ejb.EJBException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed > at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:471) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.lambda$handleDone$0(RemoteEJBReceiver.java:91) > at org.xnio.FinishedIoFuture.addNotifier(FinishedIoFuture.java:79) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:76) > at org.jboss.ejb.protocol.remote.RemoteEJBReceiver$1.handleDone(RemoteEJBReceiver.java:74) > at org.xnio.IoFuture$HandlingNotifier.notify(IoFuture.java:208) > at org.xnio.AbstractIoFuture$NotifierRunnable.run(AbstractIoFuture.java:720) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: javax.transaction.SystemException: EJBCLIENT000082: Cannot outflow the remote transaction "Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000101:-39b44114:5c59a6ad:10 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider)" as its timeout elapsed > at org.jboss.ejb.protocol.remote.EJBClientChannel.writeTransaction(EJBClientChannel.java:581) > at org.jboss.ejb.protocol.remote.EJBClientChannel.processInvocation(EJBClientChannel.java:367) > ... 12 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4324) CommandTimeoutHandlerTestCase.testComandExecutor random failure

by Jean-Francois Denise (Jira)

Jean-Francois Denise created WFCORE-4324: -------------------------------------------- Summary: CommandTimeoutHandlerTestCase.testComandExecutor random failure Key: WFCORE-4324 URL: https://issues.jboss.org/browse/WFCORE-4324 Project: WildFly Core Issue Type: Bug Components: CLI, Test Suite Reporter: Jean-Francois Denise Assignee: Jean-Francois Denise -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3634) [DMN Designer] Decision Table: OutputClause improvements

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3634: -------------------------------------- Summary: [DMN Designer] Decision Table: OutputClause improvements Key: DROOLS-3634 URL: https://issues.jboss.org/browse/DROOLS-3634 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Michael Anstis Assignee: Michael Anstis The {{Name}} and {{TypeRef}} of {{OutputClauses}} should be components of the parents {{TypeRef}. For example a {{Decision}} has a {{TypeRef}} of {{tPerson}} that is a structure with fields {{age}}/{{number}} and {{name}}/{{string}}. {{OutputClause}}'s should be defined for {{age}}/{{number}} and {{name}}/{{string}} by default. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11697) Revisit WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFLY-11697?page=com.atlassian.jira.plugin... ] Diana Vilkolakova updated WFLY-11697: ------------------------------------- Description: This feature request is about making use of authentication configuration on the client side of the WS / REST deployment. (was: This feature request is about being able to make use of authentication configuration on the client side of the WS / REST deployment. ) > Revisit WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL > ---------------------------------------------------------------------------------------------------- > > Key: WFLY-11697 > URL: https://issues.jboss.org/browse/WFLY-11697 > Project: WildFly > Issue Type: Feature Request > Components: REST, Security, Web Services > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > > This feature request is about making use of authentication configuration on the client side of the WS / REST deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11697) Revisit WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL

by Diana Vilkolakova (Jira)

Diana Vilkolakova created WFLY-11697: ---------------------------------------- Summary: Revisit WS and Rest integration with WildFly Elytron - AuthenticationClient for Authentication / SSL Key: WFLY-11697 URL: https://issues.jboss.org/browse/WFLY-11697 Project: WildFly Issue Type: Feature Request Components: REST, Security, Web Services Reporter: Diana Vilkolakova Assignee: Diana Vilkolakova This feature request is about being able to make use of authentication configuration on the client side of the WS / REST deployment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3574) executable-model: compilation fails if there are multiple update() for the same object in RHS.

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3574?page=com.atlassian.jira.plugi... ] Luca Molteni closed DROOLS-3574. -------------------------------- Resolution: Done > executable-model: compilation fails if there are multiple update() for the same object in RHS. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-3574 > URL: https://issues.jboss.org/browse/DROOLS-3574 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.14.0.Final > Environment: - RHDM 7.2.0 > Reporter: Hiroko Miura > Assignee: Luca Molteni > Priority: Minor > Labels: support > Attachments: HelloWorld.zip > > > compilation fails with the following DRL. > {noformat} > package com.sample; > //generated from Decision Table > import com.sample.Message; > // rule values at C11, header at C6 > rule "HelloWorldXLS_11" > when > m:Message(status == Message.HELLO) > then > System.out.println(m.getMsg()); > m.setMsg("Goodbye cruel world");update(m); > m.setStatus(Message.GOODBYE);update(m); > end > // rule values at C12, header at C6 > rule "HelloWorldXLS_12" > when > m:Message(status == Message.GOODBYE) > then > System.out.println(m.getMsg()); > end > {noformat} > Here is an ERROR. > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile-1) on project HelloWorld: Compilation failure > [ERROR] /tmp/HelloWorld/target/generated-sources/drools-model-compiler/main/java/com/sample/Rules47274848713b466c9cc49fe299a57c35RuleMethods0.java:[76,40] variable mask_m is already defined in method rule_HelloWorldXLS__11() > and problematic source which is generated. > {noformat} > public static org.drools.model.Rule rule_HelloWorldXLS__11() { > final org.drools.model.Variable<com.sample.Message> var_m = D.declarationOf(com.sample.Message.class, > "m"); > final org.drools.model.BitMask mask_m = org.drools.model.BitMask.getPatternMask(com.sample.Message.class, > "msg"); > final org.drools.model.BitMask mask_m = org.drools.model.BitMask.getPatternMask(com.sample.Message.class, > "msg", > "status"); > org.drools.model.Rule rule = D.rule("com.sample", > "HelloWorldXLS_11").build(D.pattern(var_m).expr("$expr$1$", > (_this) -> _this.getStatus() == Message.HELLO, > D.reactOn("status")), > D.on(var_m).execute((drools, m) -> { > System.out.println(m.getMsg()); > m.setMsg("Goodbye cruel world"); > drools.update(m, > mask_m); > m.setStatus(Message.GOODBYE); > drools.update(m, > mask_m); > })); > return rule; > } > {noformat} > If first update() (which is just after m.setMsg()) is removed, compilation works. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3574) executable-model: compilation fails if there are multiple update() for the same object in RHS.

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-3574?page=com.atlassian.jira.plugi... ] Luca Molteni updated DROOLS-3574: --------------------------------- Sprint: 2019 Week 05-07 > executable-model: compilation fails if there are multiple update() for the same object in RHS. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-3574 > URL: https://issues.jboss.org/browse/DROOLS-3574 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.14.0.Final > Environment: - RHDM 7.2.0 > Reporter: Hiroko Miura > Assignee: Luca Molteni > Priority: Minor > Labels: support > Attachments: HelloWorld.zip > > > compilation fails with the following DRL. > {noformat} > package com.sample; > //generated from Decision Table > import com.sample.Message; > // rule values at C11, header at C6 > rule "HelloWorldXLS_11" > when > m:Message(status == Message.HELLO) > then > System.out.println(m.getMsg()); > m.setMsg("Goodbye cruel world");update(m); > m.setStatus(Message.GOODBYE);update(m); > end > // rule values at C12, header at C6 > rule "HelloWorldXLS_12" > when > m:Message(status == Message.GOODBYE) > then > System.out.println(m.getMsg()); > end > {noformat} > Here is an ERROR. > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile-1) on project HelloWorld: Compilation failure > [ERROR] /tmp/HelloWorld/target/generated-sources/drools-model-compiler/main/java/com/sample/Rules47274848713b466c9cc49fe299a57c35RuleMethods0.java:[76,40] variable mask_m is already defined in method rule_HelloWorldXLS__11() > and problematic source which is generated. > {noformat} > public static org.drools.model.Rule rule_HelloWorldXLS__11() { > final org.drools.model.Variable<com.sample.Message> var_m = D.declarationOf(com.sample.Message.class, > "m"); > final org.drools.model.BitMask mask_m = org.drools.model.BitMask.getPatternMask(com.sample.Message.class, > "msg"); > final org.drools.model.BitMask mask_m = org.drools.model.BitMask.getPatternMask(com.sample.Message.class, > "msg", > "status"); > org.drools.model.Rule rule = D.rule("com.sample", > "HelloWorldXLS_11").build(D.pattern(var_m).expr("$expr$1$", > (_this) -> _this.getStatus() == Message.HELLO, > D.reactOn("status")), > D.on(var_m).execute((drools, m) -> { > System.out.println(m.getMsg()); > m.setMsg("Goodbye cruel world"); > drools.update(m, > mask_m); > m.setStatus(Message.GOODBYE); > drools.update(m, > mask_m); > })); > return rule; > } > {noformat} > If first update() (which is just after m.setMsg()) is removed, compilation works. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4323) Improve the suspend-timeout test cases

by Yeray Borges (Jira)

Yeray Borges created WFCORE-4323: ------------------------------------ Summary: Improve the suspend-timeout test cases Key: WFCORE-4323 URL: https://issues.jboss.org/browse/WFCORE-4323 Project: WildFly Core Issue Type: Task Components: Test Suite Reporter: Yeray Borges Assignee: Yeray Borges Right now we are not covering all test cases available when we are using suspend-timeout attributes for the server lifecycle operations. Discussions about the existing test cases concluded that we should be using the following strategy to test them effectively: - A test case using suspend-timeout <0 -> We can unlock the web application manually. That means test the SuspendController.listeners.complete () event path. - A test case using suspend-timeout> 0 -> We should not unlock manually the web application, and we should wait for the timeout, that means to test the SuspendController.listeners.timeout () event path. - A test case using suspend-timeout = 0 -> That could become a redundant bit with the previous case because the event will be the SuspendController.listeners.timeout (), but we will not be included in the test that the event is fired as a result of a TimerTask (). In order to allow the inflight tasks being stopped in our test suite, we need to change the way we are enabling Undertow in wildfly-core. Right now our TestSuspendServiceActivator is activating Undertow without using the IO worker threads, that means when the server is shutdown/stopped, the tasks created by Undertow are not automatically terminated. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-594) Jenkins Jobs Hung

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-594?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-594: ------------------------------------- INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? was visible before upgrade too > Jenkins Jobs Hung > ----------------- > > Key: SWSQE-594 > URL: https://issues.jboss.org/browse/SWSQE-594 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Filip Brychta > Priority: Major > Attachments: image-2019-02-11-16-35-41-783.png > > > Jenkins jobs hung in the following state: > !image-2019-02-11-16-35-41-783.png|thumbnail! > After nearly 30 min, restarting the Jenkins service cleared the issue and the jobs ran fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 7 months

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 February 2019