April 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-140) Kiali-UI Test Framework Using kiali-python-client

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-140?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-140: --------------------------------- Team: Automation (was: Infrastructure) > Kiali-UI Test Framework Using kiali-python-client > ------------------------------------------------- > > Key: SWSQE-140 > URL: https://issues.jboss.org/browse/SWSQE-140 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-141) Service Details - Info Tab automation

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-141?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan updated SWSQE-141: --------------------------------- Team: Automation (was: Infrastructure) > Service Details - Info Tab automation > ------------------------------------- > > Key: SWSQE-141 > URL: https://issues.jboss.org/browse/SWSQE-141 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10246) Required services that are not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10246?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10246: ----------------------------------------- Do you have a problem with WildFly 12? If not, with WildFly 11? If it works on WildFly, then WildFly Swarm has their own issue tracker at [1]. But you may be better off starting with a discussion on IRC or their google group-- see [2]. Swarm evolves rapidly but from my understanding of it I don't think packaging multiple ears is meant to work. [1] https://issues.jboss.org/projects/SWARM [2] http://wildfly-swarm.io/community/ > Required services that are not installed > ---------------------------------------- > > Key: WFLY-10246 > URL: https://issues.jboss.org/browse/WFLY-10246 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: migrating wildfly 10.1.0 to widfly-swarm 2017.11.0 > Reporter: Zakaria mh > Assignee: Jason Greene > Labels: Swarm > > ERROR [org.jboss.as.controller.management-operation] (main) WFLYCTL0013: Operation ("add") failed - address: (("deployment" => "module1-3.3.0-SNAPSHOT.war")) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"] > } > [0m [31m2018-04-16 12:13:59,010 ERROR [org.jboss.as.server] (main) WFLYSRV0021: Deploy of deployment "module1-3.3.0-SNAPSHOT.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"] > } > [0m [0m2018-04-16 12:13:59,789 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment module1-3.3.0-SNAPSHOT.war (runtime-name: module1-3.3.0-SNAPSHOT.war) in 779ms > [0m [0m2018-04-16 12:13:59,790 INFO [org.jboss.as.controller] (main) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.deployment.unit."module2D-3.3.0-SNAPSHOT.ear".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."module1-3.3.0-SNAPSHOT.war".PARSE] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1355) set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1355?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBJCA-1355: ------------------------------------------------ Jan Kurik <jkurik(a)redhat.com> changed the Status of [bug 1497591|https://bugzilla.redhat.com/show_bug.cgi?id=1497591] from VERIFIED to CLOSED > set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second > ---------------------------------------------------------------------------------------------------- > > Key: JBJCA-1355 > URL: https://issues.jboss.org/browse/JBJCA-1355 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Reporter: Masafumi Miura > Assignee: Stefano Maestri > > {{set-tx-query-timeout}} setting does not work when the remaining transaction timeout is shorter than one second (between 0-999 millis) due to incorrect round-up in IronJacamar {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}}. > --- > {{WrappedConnection#checkConfiguredQueryTimeout()}} checks the returned value from {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}} and set the value to query timeout if it's larger than 0. If it's not larger than 0, the configured query timeout ({{query-timeout}} in datasource setting) is used. This behavior itself is ok. > However, {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}} incorrectly rounds up the returned value from transaction manager's {{TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()}}. And it results in returning 0 when the remaining transaction timeout is between 0-999 millis. This causes the issue. > Here's the related code from 1.3.7.Final (It's same in the latest 1.3 branch and 1.4 branch): > - https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.7.Final/a... > {code} > 2022 /** > 2023 * Check configured query timeout > 2024 * @param ws The statement > 2025 * @param explicitTimeout An explicit timeout value set > 2026 * @exception SQLException Thrown if an error occurs > 2027 */ > 2028 void checkConfiguredQueryTimeout(WrappedStatement ws, int explicitTimeout) throws SQLException > 2029 { > 2030 if (mc == null || dataSource == null) > 2031 return; > 2032 > 2033 int timeout = 0; > 2034 > 2035 // Use the transaction timeout > 2036 if (mc.isTransactionQueryTimeout()) > 2037 { > 2038 timeout = dataSource.getTimeLeftBeforeTransactionTimeout(); > 2039 if (timeout > 0 && explicitTimeout > 0 && timeout > explicitTimeout) > 2040 timeout = explicitTimeout; > 2041 } > 2042 > 2043 // Look for a configured value > 2044 if (timeout <= 0 && explicitTimeout <= 0) > 2045 timeout = mc.getQueryTimeout(); > 2046 > 2047 if (timeout > 0) > 2048 ws.setQueryTimeout(timeout); > 2049 } > {code} > - https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.7.Final/a... > {code} > 190 /** > 191 * Get the time left before a transaction timeout > 192 * @return The amount in seconds; <code>-1</code> if no timeout > 193 * @exception SQLException Thrown if an error occurs > 194 */ > 195 protected int getTimeLeftBeforeTransactionTimeout() throws SQLException > 196 { > 197 try > 198 { > 199 if (cm instanceof TransactionTimeoutConfiguration) > 200 { > 201 long timeout = ((TransactionTimeoutConfiguration) cm).getTimeLeftBeforeTransactionTimeout(true); > 202 // No timeout > 203 if (timeout == -1) > 204 return -1; > 205 // Round up to the nearest second > 206 long result = timeout / 1000; > 207 if ((result % 1000) != 0) > 208 ++result; > 209 return (int) result; > 210 } > 211 else > 212 return -1; > 213 } > 214 catch (RollbackException e) > 215 { > 216 throw new SQLException(e); > 217 } > 218 } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10246) Required services that are not installed

by Zakaria mh (JIRA)

[ https://issues.jboss.org/browse/WFLY-10246?page=com.atlassian.jira.plugin... ] Zakaria mh updated WFLY-10246: ------------------------------ Security: (was: Red Hat Internal) > Required services that are not installed > ---------------------------------------- > > Key: WFLY-10246 > URL: https://issues.jboss.org/browse/WFLY-10246 > Project: WildFly > Issue Type: Bug > Affects Versions: 10.1.0.Final > Environment: migrating wildfly 10.1.0 to widfly-swarm 2017.11.0 > Reporter: Zakaria mh > Assignee: Jason Greene > Labels: Swarm > > ERROR [org.jboss.as.controller.management-operation] (main) WFLYCTL0013: Operation ("add") failed - address: (("deployment" => "module1-3.3.0-SNAPSHOT.war")) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"] > } > [0m [31m2018-04-16 12:13:59,010 ERROR [org.jboss.as.server] (main) WFLYSRV0021: Deploy of deployment "module1-3.3.0-SNAPSHOT.war" was rolled back with the following failure message: > { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"module1-3.3.0-SNAPSHOT.war\".PARSE is missing [jboss.deployment.unit.\"module2D-3.3.0-SNAPSHOT.ear\".deploymentCompleteService]"] > } > [0m [0m2018-04-16 12:13:59,789 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment module1-3.3.0-SNAPSHOT.war (runtime-name: module1-3.3.0-SNAPSHOT.war) in 779ms > [0m [0m2018-04-16 12:13:59,790 INFO [org.jboss.as.controller] (main) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.deployment.unit."module2D-3.3.0-SNAPSHOT.ear".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."module1-3.3.0-SNAPSHOT.war".PARSE] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10245) Mod_cluster requires Advertise but Multicast interface is not available

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-10245?page=com.atlassian.jira.plugin... ] Radoslav Husar commented on WFLY-10245: --------------------------------------- Was the test actually using multicast for discovery? [~jkasik] maybe or can you direct this to whoever picked up after Bogdan? > Mod_cluster requires Advertise but Multicast interface is not available > ----------------------------------------------------------------------- > > Key: WFLY-10245 > URL: https://issues.jboss.org/browse/WFLY-10245 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Final > Reporter: Bogdan Sikora > Assignee: Radoslav Husar > Priority: Minor > Attachments: standalone-ha.xml, standalone.xml > > > This error message has probably no impact to mod-cluster functionality as tests successfully finished even with this message in workers log. Balancer (standalone.xml) has no error messages. > [^standalone-ha.xml] (worker) > [^standalone.xml] (balancer) > Issue: > {noformat} > 2016-10-24 03:51:18,393 ERROR [org.wildfly.extension.mod_cluster] (ServerService Thread Pool -- 64) WFLYMODCLS0004: Mod_cluster requires Advertise but Multicast interface is not available > {noformat} > Environment: > Windows machine with Tunnel adapter Teredo Tunneling Pseudo-Interface > Scenario: > 1. Start Eap (standalone-ha.xml) on Ipv6 address with prefix 2001 (Teredo Tunneling) > 2. Look for Mod_cluster Advertising error > Error from ContainerEventHandlerService class > {code} > // Read node to set configuration. > if (config.getAdvertise()) { > // There should be a socket-binding.... Well no it needs an advertise socket :-( > final SocketBinding binding = this.binding.getOptionalValue(); > if (binding != null) { > config.setAdvertiseSocketAddress(binding.getMulticastSocketAddress()); > config.setAdvertiseInterface(binding.getSocketAddress().getAddress()); > if (!isMulticastEnabled(bindingManager.getValue().getDefaultInterfaceBinding().getNetworkInterfaces())) { > ROOT_LOGGER.multicastInterfaceNotAvailable(); > } > } > } > ... > private boolean isMulticastEnabled(Collection<NetworkInterface> ifaces) { > for (NetworkInterface iface : ifaces) { > try { > if (iface.isUp() && (iface.supportsMulticast() || iface.isLoopback())) { > return true; > } > } catch (SocketException e) { > // Ignore > } > } > return false; > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2481) Stateless sessions aren't under control of KieBase coordination during an incremental update

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-2481: ----------------------------------- Summary: Stateless sessions aren't under control of KieBase coordination during an incremental update Key: DROOLS-2481 URL: https://issues.jboss.org/browse/DROOLS-2481 Project: Drools Issue Type: Bug Components: core engine Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2468) Stateless sessions aren't under control of KieBase coordination during an incremental update

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2468?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-2468: -------------------------------- Sprint: RHPAM7-Iteration12 > Stateless sessions aren't under control of KieBase coordination during an incremental update > -------------------------------------------------------------------------------------------- > > Key: DROOLS-2468 > URL: https://issues.jboss.org/browse/DROOLS-2468 > Project: Drools > Issue Type: Bug > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10242) Unify secmgr JAVA_OPTS behaviour in WF scripts

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10242?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10242: -------------------------------------- I don't think we should allow {{-secmgr}} in the {{JAVA_OPTS}}. It's not a valid JVM argument. There is a {{SECMGR=true}} environment variable that can be used in the {{*.conf}} files. We've supported the {{SECMGR}} environment variable from the introduction of the {{-secmgr}} flag and I think we should unify around the current configuration options. > Unify secmgr JAVA_OPTS behaviour in WF scripts > ---------------------------------------------- > > Key: WFLY-10242 > URL: https://issues.jboss.org/browse/WFLY-10242 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Kabir Khan > > Unify secmgr JAVA_OPTS behaviour in WF scripts. > standalone&&domain&&appclient scripts doesn't allow to use secmgr by JAVA_OPTS definition. wsconsume&&wsprovide scripts allow that (see [this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...] and [this|https://github.com/wildfly/wildfly/blob/master/feature-pack/src/main...]) > All scripts should be unified. > cc: [~asoldano], [~jamezp], [~jbliznak], [~msvehla] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10199) Using jboss-modules loading outside WildFly 12 is broken

by Martin Perina (JIRA)

[ https://issues.jboss.org/browse/WFLY-10199?page=com.atlassian.jira.plugin... ] Martin Perina commented on WFLY-10199: -------------------------------------- It seems that using jboss-modules-1.8.1 fixes the issue (although oVirt cannot still be deployed on WildFly 12 due to other errors which I'm currently investigating). Thanks! > Using jboss-modules loading outside WildFly 12 is broken > -------------------------------------------------------- > > Key: WFLY-10199 > URL: https://issues.jboss.org/browse/WFLY-10199 > Project: WildFly > Issue Type: Bug > Affects Versions: 12.0.0.Final > Reporter: Martin Perina > Assignee: David Lloyd > > oVirt is using jboss-modules not only for dependencies inside WildFly, but also when executing command line tools outside WildFly process. We are using following method which worked fine from JBoss 7 to WildFly11: > export JAVA_MODULEPATH="<PATH TO OUR MODULES>" > exec "${JAVA_HOME}/bin/java" \ > -jar "${JBOSS_HOME}/jboss-modules.jar" \ > -dependencies org.ovirt.engine.core.tools \ > -class org.ovirt.engine.core.cryptotool.Main \ > "$@" > where "org.ovirt.engine.core.tools" is one of our existing module and in class we have standard Java class with main() method executing logic of specific command line tool. > When I try to execute this code with WildFly 12.0.0.FINAL I receive following exception: > Exception in thread "main" java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:460) > at java.util.Properties.setProperty(Properties.java:166) > at java.lang.System.setProperty(System.java:796) > at org.jboss.modules.PropertyWriteAction.run(PropertyWriteAction.java:40) > at org.jboss.modules.PropertyWriteAction.run(PropertyWriteAction.java:28) > at java.security.AccessController.doPrivileged(Native Method) > at org.jboss.modules.Main.main(Main.java:390) > When I tried to replace jboss-modules.jar provided by WildFly 12.0.0.FINAL with manuall build using latest code in 1.7 branch (commit a52a323c5c3d71cf9597f06951155e4639cbb707) I receive different error: > org.jboss.modules.ModuleNotFoundException: org.ovirt.engine.core.tools > at org.jboss.modules.Module.addPaths(Module.java:1221) > at org.jboss.modules.Module.link(Module.java:1577) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1605) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:426) > I haven't found any documentation describing such incompatible between 1.6 and 1.7, so is there any way how to have above execution compatible with both jboss-modules versions? > Thanks > Martin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 April 2018