December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1560) PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1560?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1560: ----------------------------- Fix Version/s: 9.0.0.Final > PartialObjectActivationJarTestCase fails if ran after any of InflowFlatTestCase or TwoModulesOfDifferentTypeTestCase > -------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1560 > URL: https://issues.jboss.org/browse/WFLY-1560 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha1 > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Fix For: 9.0.0.Final > > Attachments: server_log_snippet.txt > > > PartialObjectActivationJarTestCase fails if it runs after InflowFlatTestCase. It seems that the {{inflow2}} resource adapter is not fully unregistered by InflowFlatTestCase before PartialObjectActivationJarTestCase begins to start its own RA. > Here is the server log snippet (DEBUG level): > http://pastebin.test.redhat.com/147968 > Line 10 of this snippet corresponds to the invocation of {{setConfiguration("basic.xml");}} in PartialObjectActivationJarTestCase. Then, the server is apparently trying to activate {{MultipleConnectionFactory2Impl}} and {{MultipleAdminObject2Impl}} even though these are not involved in {{basic.xml}} of PartialObjectActivationJarTestCase at all. A suspicious exception is on line 19 there. > I tried to put some delay between {{remove(address);}} and {{removeModule(defaultPath);}} in {{AbstractModuleDeploymentTestCaseSetup#tearDown()}} but it did not help. I also tried to put {{@Ignore}} to both test methods in the InflowFlatTestCase which also did not help, so it is evidently related only to the RA deployment/undeployment. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1158) add "remove vault entry" option to vault tool

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1158?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1158: ----------------------------- Fix Version/s: 9.0.0.Final > add "remove vault entry" option to vault tool > ---------------------------------------------- > > Key: WFLY-1158 > URL: https://issues.jboss.org/browse/WFLY-1158 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Gernot P > Assignee: Peter Skopek > Fix For: 9.0.0.Final > > Attachments: patch.diff > > > You cannot remove an entry form vault with the vault tool. You can choose only amog following options "0: Store a password 1: Check whether password exists 2: Exit" > Pleas add "remove password" option to vault tool (vault.sh) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4382) Functionality to allow symbolic links

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4382?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4382: ----------------------------- Fix Version/s: 9.0.0.Final > Functionality to allow symbolic links > ------------------------------------- > > Key: WFLY-4382 > URL: https://issues.jboss.org/browse/WFLY-4382 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Erdal Yildiz > Assignee: Jakub Pýcha > Priority: Minor > Fix For: 9.0.0.Final > > > There should be a possibility to configure that wildfly follows symbolic links. > Example which describes the problem: > $wildflyHome/welcome-content/test/index.html --> localhost:8080/test/index.html ==> works. > $wildflyHome/welcome-content/symlink/index.html --> localhost:8080/symlink/index.html ==> doesn't work. > "symlink" is the symbolic link which is created by > ln -s /path/to/symlink $wildflyHome/welcome-content -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4135) All-in-one Java EE 7 Quickstart

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4135?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4135: ----------------------------- Fix Version/s: 9.0.0.Final > All-in-one Java EE 7 Quickstart > ------------------------------- > > Key: WFLY-4135 > URL: https://issues.jboss.org/browse/WFLY-4135 > Project: WildFly > Issue Type: Sub-task > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Fix For: 9.0.0.Final > > > Introduce a WildFly Quickstart to demo usage of the new/updated technologies introduced by Java EE 7. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2537) Write to wsdl-url attribute for WS endpoint ends with 'Unknown attribute wsdl-url' instead of 'Attribute wsdl-url is not writable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2537?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2537: ----------------------------- Fix Version/s: 9.0.0.Final > Write to wsdl-url attribute for WS endpoint ends with 'Unknown attribute wsdl-url' instead of 'Attribute wsdl-url is not writable > --------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-2537 > URL: https://issues.jboss.org/browse/WFLY-2537 > Project: WildFly > Issue Type: Bug > Components: CLI > Reporter: R Searls > Assignee: R Searls > Priority: Minor > Fix For: 9.0.0.Final > > > for submission of https://bugzilla.redhat.com/show_bug.cgi?id=987898 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-840) jboss.as MBean subtree missing when profiling agent used

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-840?page=com.atlassian.jira.plugin.s... ] Kabir Khan updated WFLY-840: ---------------------------- Fix Version/s: 9.0.0.Final > jboss.as MBean subtree missing when profiling agent used > -------------------------------------------------------- > > Key: WFLY-840 > URL: https://issues.jboss.org/browse/WFLY-840 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: dpocock > Labels: jconsole > Fix For: 9.0.0.Final > > > I've set up JBoss 7.1.0.Final as a fresh installation and started standalone > I can successfully connect with regular jconsole or $JBOSS_HOME/bin/jconsole. In the MBeans tab, I can see various subtrees, including jboss.as > Then I stop JBoss and add the jmxetric monitoring agent, as described here: > http://danielpocock.com/monitoring-jboss-tomcat-and-application-servers-w... > Now, with JBoss running with jmxetric, I connect to it with jconsole (either regular jconsole or $JBOSS_HOME/bin/jconsole) and I can see all the same subtrees, except one, jboss.as is missing. I can see jboss.modules, jboss.ws, jboss.msc, jboss.jta and core JVM subtrees -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3869) Extend test coverage for WFLY-1172

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3869?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3869: ----------------------------- Fix Version/s: 9.0.0.Final > Extend test coverage for WFLY-1172 > ---------------------------------- > > Key: WFLY-3869 > URL: https://issues.jboss.org/browse/WFLY-3869 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Pavel Jelinek > Assignee: Pavel Jelinek > Fix For: 9.0.0.Final > > > Add test scenario with taglib from module only. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2712) Possible NPE in RemoteDeployer from WS tests-integration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2712?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2712: ----------------------------- Fix Version/s: 9.0.0.Final > Possible NPE in RemoteDeployer from WS tests-integration > -------------------------------------------------------- > > Key: WFLY-2712 > URL: https://issues.jboss.org/browse/WFLY-2712 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > Fix For: 9.0.0.Final > > > https://github.com/rsvoboda/wildfly/blob/master/webservices/tests-integra... > Possible NPE, check 'if (options != null)' is present only on line 284. > Or is it intentional to throw exception ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[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)

8 years, 5 months

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)

8 years, 5 months

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