March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2328) CLI connect command should accept a --bind parameter

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2328?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2328: ---------------------------------------------- The rewritten connect command on top of Aesh API will offer this bind option. > CLI connect command should accept a --bind parameter > ---------------------------------------------------- > > Key: WFCORE-2328 > URL: https://issues.jboss.org/browse/WFCORE-2328 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Jean-Francois Denise > Priority: Minor > > When you launch the CLI you can pass a --bind=xxx param which then controls the client side bind address used for connections. But you can't specify this with the connect command itself. > This is minor; I just noticed it while experimenting with the fix for WFCORE-2225 when I wanted to confirm the fix was working by using the CLI. > Also, I noticed that if I did a "connect --bind=192.168.1.10" the CLI accepted the invalide command. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8353) Upgrade JBossWS from 5.1.7.Final to 5.1.8.Final

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFLY-8353: ---------------------------------------------- Summary: Upgrade JBossWS from 5.1.7.Final to 5.1.8.Final Key: WFLY-8353 URL: https://issues.jboss.org/browse/WFLY-8353 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Bartosz Spyrko-Śmietanko Assignee: Alessio Soldano -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8354) Upgrade JBossWS from 5.1.7.Final to 5.1.8.Final

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFLY-8354: ---------------------------------------------- Summary: Upgrade JBossWS from 5.1.7.Final to 5.1.8.Final Key: WFLY-8354 URL: https://issues.jboss.org/browse/WFLY-8354 Project: WildFly Issue Type: Component Upgrade Components: Web Services Reporter: Bartosz Spyrko-Śmietanko Assignee: Alessio Soldano -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-21) Automation Testcase

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-21?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-21: ------------------------------------------ Jenkins Job created http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/view/Cloud%20Forms/job/c... > Automation Testcase > ------------------- > > Key: HAWKULARQE-21 > URL: https://issues.jboss.org/browse/HAWKULARQE-21 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: hawkular-qe-automation > > Automate as end-to-end scenario -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-23) Automation Testcase

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-23?page=com.atlassian.jira.plu... ] Hayk Hovsepyan commented on HAWKULARQE-23: ------------------------------------------ Jenkins job created http://jenkins.jonqe.lab.eng.bos.redhat.com:9080/view/Cloud%20Forms/job/c... > Automation Testcase > ------------------- > > Key: HAWKULARQE-23 > URL: https://issues.jboss.org/browse/HAWKULARQE-23 > Project: Hawkular QE > Issue Type: Sub-task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: hawkular-qe-automation > > Automate as end-to-end scenario. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8351) Prepare wildfly for multiply dynamic capability parts in core

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8351: --------------------------------- Summary: Prepare wildfly for multiply dynamic capability parts in core Key: WFLY-8351 URL: https://issues.jboss.org/browse/WFLY-8351 Project: WildFly Issue Type: Task Components: Clustering Reporter: Tomaz Cerar Assignee: Tomaz Cerar Due to some API changes coming with WFCORE-2202we need to modify code a bit in full before we can merge core PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8352) Prepare code for multiply dynamic capability parts in core

by Tomaz Cerar (JIRA)

Tomaz Cerar created WFLY-8352: --------------------------------- Summary: Prepare code for multiply dynamic capability parts in core Key: WFLY-8352 URL: https://issues.jboss.org/browse/WFLY-8352 Project: WildFly Issue Type: Task Components: Clustering Reporter: Tomaz Cerar Assignee: Tomaz Cerar Due to some API changes coming with WFCORE-2202we need to modify code a bit in full before we can merge core PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8275) 2PC Inflow transactions don't work for JTA

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-8275?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-8275: -------------------------------- Labels: Regression (was: ) > 2PC Inflow transactions don't work for JTA > ------------------------------------------ > > Key: WFLY-8275 > URL: https://issues.jboss.org/browse/WFLY-8275 > Project: WildFly > Issue Type: Bug > Components: JCA, Transactions > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Priority: Blocker > Labels: Regression > > Inflow transactions are initiated by an external enterprise information system (EIS). If a message arrive from the EIS in a transaction, the EAP should import the tx context (thru resource adapter (RAR)) and perform the business process on that message in the same transaction. > In our test two participants are part of TM subordinate transaction driven by RAR and two phase commit (2PC) is expected to be processed by TM on those participants. > It seems that since DR12 TM doesn't know about inflow tx and returns XA_RDONLY on prepare call. After that it ends up with XAException on commit call. > {code} > 2017-02-21 10:41:38,265 ERROR [org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceTxnWorkUnit] (default-threads - 1) Can't run javax.resource.spi.XATerminator command based on message 'commit 1' XAException 'null' with error code 'XAER_INVAL'?: javax.transaction.xa.XAException > at com.arjuna.ats.internal.jta.transaction.arjunacore.jca.XATerminatorImple.commit(XATerminatorImple.java:98) > at org.jboss.as.test.jbossts.crashrec.jca.rar.TestResourceTxnWorkUnit.run(Unknown Source) > at org.jboss.jca.core.workmanager.WorkWrapper.runWork(WorkWrapper.java:445) > at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:223) > at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) > at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808) > at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) > at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > Full log attached. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8350) It should not be possible to set negative values to IO worker attributes

by Dmitrii Tikhomirov (JIRA)

Dmitrii Tikhomirov created WFLY-8350: ---------------------------------------- Summary: It should not be possible to set negative values to IO worker attributes Key: WFLY-8350 URL: https://issues.jboss.org/browse/WFLY-8350 Project: WildFly Issue Type: Bug Components: IO Affects Versions: 10.1.0.Final Reporter: Dmitrii Tikhomirov Assignee: Dmitrii Tikhomirov Following IO worker attributes can be set to negative values which in this context doesn't make sense: * {{io-threads}} * {{stack-size}} * {{task-keepalive}} * {{task-max-threads}} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8232) SecurityAuditingTestCase fails with Elytron profile in AS TS

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFLY-8232?page=com.atlassian.jira.plugin.... ] Jan Kalina updated WFLY-8232: ----------------------------- Fix Version/s: 11.0.0.Alpha1 > SecurityAuditingTestCase fails with Elytron profile in AS TS > ------------------------------------------------------------ > > Key: WFLY-8232 > URL: https://issues.jboss.org/browse/WFLY-8232 > Project: WildFly > Issue Type: Bug > Components: Security, Test Suite > Reporter: Josef Cacek > Assignee: Jan Kalina > Fix For: 11.0.0.Alpha1 > > > The {{SecurityAuditingTestCase}} fails when executed with Elytron profile ({{-Delytron}}) in AS TS. > {code} > cd testsuite/integration/basic > mvn clean test -Dtest=SecurityAuditingTestCase -Delytron > ... > Failed tests: > SecurityAuditingTestCase.testSingleMethodAnnotationsUser1Template:181->AnnSBTest.testSingleMethodAnnotationsUser1Template:156->AnnSBTest.lambda$testSingleMethodAnnotationsUser1Template$1:169 EJBAccessException not expected > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 March 2017