December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4011) Resource adapter config properties cannot be changed without two reloads

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4011?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4011: ----------------------------- Fix Version/s: 9.0.0.Final > Resource adapter config properties cannot be changed without two reloads > ------------------------------------------------------------------------ > > Key: WFLY-4011 > URL: https://issues.jboss.org/browse/WFLY-4011 > Project: WildFly > Issue Type: Enhancement > Components: JCA > Affects Versions: 8.1.0.Final > Environment: Ubuntu 14.0.4 64-bit; JDK 1.8.0_25; Wildfly 8.1.0.Final standalone > Reporter: Scott Van Wart > Assignee: Stefano Maestri > Priority: Minor > Labels: cli, resource-adapter > Fix For: 9.0.0.Final > > Attachments: remove-add.txt, remove-reload-add.txt > > > I have a RAR deployed within an EAR file and it defines a config property "host" in the resource-adapter subsystem. I followed the binding instructions here: > https://docs.jboss.org/author/display/WFLY8/Resource+adapters > If I want to change the "host" configuration property, I need to do the following: > 1. Remove the configuration property. > 2. Reload > 3. Add the configuration property back. > 4. Reload > The "value" attribute of the config property isn't writable (JCA doesn't communicate config property changes during runtime): https://issues.jboss.org/browse/WFLY-3729 > Trying to add the property again after removal results in an error as Wildfly believes the attribute still exists if you haven't reloaded since removal. > This makes scripting a resource adapter property change difficult, as the "reload" command returns immediately and a script must wait an unknown amount of time for the management interface to become available before it can issue new commands. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3023) JDR CommandLineMain defaults to port 9999

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3023?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3023: ----------------------------- Fix Version/s: 9.0.0.Final > JDR CommandLineMain defaults to port 9999 > ----------------------------------------- > > Key: WFLY-3023 > URL: https://issues.jboss.org/browse/WFLY-3023 > Project: WildFly > Issue Type: Bug > Components: JDR > Affects Versions: 8.0.0.Final > Reporter: Brian Stansberry > Assignee: Jesse Jaggars > Fix For: 9.0.0.Final > > > If the user doesn't provide a port, CommandLineMain defaults to 9999, but with protocol http-remoting. That combo won't work. It should use 9990 since that will be the default management port. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4207) Migrate Quickstarts to Java EE 7

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4207?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4207: ----------------------------- Fix Version/s: 9.0.0.Final > Migrate Quickstarts to Java EE 7 > -------------------------------- > > Key: WFLY-4207 > URL: https://issues.jboss.org/browse/WFLY-4207 > Project: WildFly > Issue Type: Sub-task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > Update WildFly Quickstart's code to take advantage of the technologies with major updates on Java EE 7, for instance JAX-RS and JMS. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4060) Intermittent failures on SendMessage testcase when running with JTS

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4060?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4060: ----------------------------- Fix Version/s: 9.0.0.Final > Intermittent failures on SendMessage testcase when running with JTS > ------------------------------------------------------------------- > > Key: WFLY-4060 > URL: https://issues.jboss.org/browse/WFLY-4060 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 9.0.0.Final > > > During testing EAP I was hitting intermittent failures on SendMessageTestscase which was caused by timing issues. > There is a bit more explanation of reasons at bz: https://bugzilla.redhat.com/show_bug.cgi?id=1160761 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2403) Cannot disable Datasource or XADatasource in standalone and domain modes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2403?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2403: ----------------------------- Fix Version/s: 9.0.0.Final > Cannot disable Datasource or XADatasource in standalone and domain modes > ------------------------------------------------------------------------ > > Key: WFLY-2403 > URL: https://issues.jboss.org/browse/WFLY-2403 > Project: WildFly > Issue Type: Bug > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Final > > > Description of problem: > Cannot disable a Datasource or XADatasource in standalone mode. It's back to enabled state after server reload. > Version-Release number of selected component (if applicable): > 6.1 > How reproducible: > Always > Steps to Reproduce: > Use the http management interface or the CLI > 1.Create a Datasource of XADatasource > 2.Disable it > 3.The response indicates a server reload is required > 4.Execute the reload operation > Actual results: > The datasource is back to enabled state > Expected results: > The datasource should be in disabled state -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3042) There should be a warning logged if the default value of node identifier has not been changed.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3042?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3042: ----------------------------- Fix Version/s: 9.0.0.Final > There should be a warning logged if the default value of node identifier has not been changed. > ------------------------------------------------------------------------------------------------ > > Key: WFLY-3042 > URL: https://issues.jboss.org/browse/WFLY-3042 > Project: WildFly > Issue Type: Enhancement > Components: Transactions > Affects Versions: 8.0.0.Final > Environment: JBoss EAP 6.x > Reporter: Tom Ross > Assignee: Gytis Trikleris > Fix For: 9.0.0.Final > > > JBoss EAP instance is using the value of node identifier to identify XA transactions that belong to it. By default this value is set to 1. Now days in most environments there will be multiple JBoss instances sharing XA resources there for it is necessary to set the value of node identifier to a unique value for each instance. This is something that most end users fail to perform. Therefor it would be helpful if a warning message was logged at startup telling the user to do it. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4521) Deployment does not see / cannot access the cdi interceptor if the latter is loaded inside a module from a DUP.

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4521?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4521: ----------------------------- Fix Version/s: 9.0.0.Final > Deployment does not see / cannot access the cdi interceptor if the latter is loaded inside a module from a DUP. > ---------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4521 > URL: https://issues.jboss.org/browse/WFLY-4521 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 9.0.0.Beta2 > Reporter: Panagiotis Sotiropoulos > Assignee: Jozef Hartinger > Fix For: 9.0.0.Final > > Attachments: interceptorExample.jar, interceptorExample.zip > > > The cdi interceptor is not accessible via the deployment, if it is loaded from a Deployment Unit Processor as a module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1454) When logging into the management console with no servers defined an error is thrown

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1454?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1454: ----------------------------- Fix Version/s: 9.0.0.Final > When logging into the management console with no servers defined an error is thrown > ------------------------------------------------------------------------------------ > > Key: WFLY-1454 > URL: https://issues.jboss.org/browse/WFLY-1454 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Heiko Braun > Assignee: Harald Pehl > Labels: console_1.5.3, merged > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4289) Authentication bug on one-way JAX-WS methods

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4289?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4289: ----------------------------- Fix Version/s: 9.0.0.Final > Authentication bug on one-way JAX-WS methods > -------------------------------------------- > > Key: WFLY-4289 > URL: https://issues.jboss.org/browse/WFLY-4289 > Project: WildFly > Issue Type: Bug > Components: Security, Web Services > Affects Versions: 8.2.0.Final > Reporter: Jakub Grabowski > Assignee: Jim Ma > Fix For: 9.0.0.Final > > > 1. For two-way methods basic authentication and autorization works fine. User is authenticated with LDAP module and gets proper role that autorizes invocation. It works just fine. By two-way method I mean method with input and output message defined in WSDL. > 2. For one-way methods (return type void) user is not authenticated properly. It results in denial of method invocation. > 3. When I remove @RolesAllowed declaration I can see that for two-way methods authentication is correct (pricipal is set to logged user), but for one-way it's not - I get "anonymous" as principal. > 4. When I change one-way method to have input and output messages defined in WSDL and update implementation accordingly it suprisingly starts to work as expected. > It's quite serious issue, because currently there's no way to have authorized access to oneway webservice methods. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2383) resource-adapter id attribute has to match ra name otherwise MDB is not deployed

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2383?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2383: ----------------------------- Fix Version/s: 9.0.0.Final > resource-adapter id attribute has to match ra name otherwise MDB is not deployed > -------------------------------------------------------------------------------- > > Key: WFLY-2383 > URL: https://issues.jboss.org/browse/WFLY-2383 > Project: WildFly > Issue Type: Bug > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Fix For: 9.0.0.Final > > > The resource-adapter id has to have the same name as the ra archive has. Otherwise the the MDB is not deployed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

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