October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4131) Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4131?page=com.atlassian.jira.plugi... ] James Perkins closed WFCORE-4131. --------------------------------- Resolution: Duplicate Issue > Upgrade jboss-logmanager from 2.1.4.Final to 2.1.5.Final > -------------------------------------------------------- > > Key: WFCORE-4131 > URL: https://issues.jboss.org/browse/WFCORE-4131 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4156) Add missing KernelAPIVersion for WildFly 14

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4156?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4156: ------------------------------------- Issue Type: Bug (was: Component Upgrade) > Add missing KernelAPIVersion for WildFly 14 > ------------------------------------------- > > Key: WFCORE-4156 > URL: https://issues.jboss.org/browse/WFCORE-4156 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Priority: Major > > When WFCORE-4109 and WFCORE-4137 have been done following the release of WildFly 14.0.0.Final, the KernelAPIVersion which is used by domain transformers has not been updated. > We need to add a value for WildFly 14.0.0.Final: VERSION_8_0(8, 0, 0) > In addition, KernelAPIVersion and HostExcludeResourceDefinition.KnownRelease should be tied together as both express model versions using ints which leads to inconsistencies such as highlighted by this issue. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10945) JDK11 ws testsuite SSL failures

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/WFLY-10945?page=com.atlassian.jira.plugin... ] Jan Blizňák commented on WFLY-10945: ------------------------------------ JBWS is not registering BC as a global security provider but it is using dynamic loading mechanism via special interceptors which load the BC provider to exchange of the message being processed to use if needed, check https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.3.Final/modul... Anyway these tests should not require BC to run, however, given the mechanism above, BC might be involved. So I tried to explicitly disable BC loading by -Dorg.jboss.ws.cxf.noLocalBC=true added to both client and server side, the result is the same as before - without the {{System.setProperty("https.protocols", "TLSv1.1");}} workaround the tests are failing. > JDK11 ws testsuite SSL failures > ------------------------------- > > Key: WFLY-10945 > URL: https://issues.jboss.org/browse/WFLY-10945 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Fix For: 15.0.0.Alpha1 > > > ws testsuite failures on JDK-11: > * missing local IP in SubjectAlternativeNamesExtension > * TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 + TLS1.2 seems buggy on JDK-11: Invalid ECDH ServerKeyExchange signature > * not issue after switching to TLS1.1 or to ciphersuite TLS_RSA_WITH_AES_256_CBC_SHA256 -> JDK bug -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ] Alessio Soldano reassigned WFLY-11128: -------------------------------------- Assignee: R Searls (was: Alessio Soldano) > wsconsume failure on wildfly14 + JDK 11 > --------------------------------------- > > Key: WFLY-11128 > URL: https://issues.jboss.org/browse/WFLY-11128 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Environment: Windows 7 64bits > JDK 11 > Wildfly 14 > Reporter: mazen mahmoud > Assignee: R Searls > Priority: Minor > Attachments: log.txt > > > running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file) > the service is very simple. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11128) wsconsume failure on wildfly14 + JDK 11

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-11128?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-11128: ----------------------------------- Priority: Major (was: Minor) > wsconsume failure on wildfly14 + JDK 11 > --------------------------------------- > > Key: WFLY-11128 > URL: https://issues.jboss.org/browse/WFLY-11128 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 14.0.0.Final > Environment: Windows 7 64bits > JDK 11 > Wildfly 14 > Reporter: mazen mahmoud > Assignee: R Searls > Priority: Major > Attachments: log.txt > > > running wsconsume on a single jax-ws service with JDK 11 failes. (see attached log.txt file) > the service is very simple. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11129) Temporary files not cleaned up after build

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11129?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11129: ------------------------------------ Component/s: Build System > Temporary files not cleaned up after build > ------------------------------------------ > > Key: WFLY-11129 > URL: https://issues.jboss.org/browse/WFLY-11129 > Project: WildFly > Issue Type: Bug > Components: Build System > Affects Versions: 14.0.1.Final > Environment: Solaris SPARC 10, Oracle JDK 1.80,0_181 > Reporter: Frank Langelage > Assignee: Jason Greene > Priority: Major > Labels: maven > > After building WildFly 14 from sources I have a lot of files in /var/tmp folder under a unique folder. > {{sb2000.[neu2l]/mbi/mbi2e_all. ls -l /var/tmp > total 5356 > drwxr-xr-x 3 jboss informix 512 Oct 6 14:47 1397ea75-a91c-490a-9860-0041c101ef3a > drwxr-xr-x 3 jboss informix 512 Oct 6 13:47 23d28bb9-0bdd-4991-aa9b-8805d613e720 > drwxr-xr-x 3 jboss informix 512 Oct 5 23:34 2c3bd18e-8b83-46d3-b06f-18378e1cb12d > drwxr-xr-x 3 jboss informix 512 Oct 6 14:56 396f75f7-45b0-4b50-9607-9060cabf018b > drwxr-xr-x 3 jboss informix 512 Oct 6 13:48 521e2a76-764c-4f5a-8a6e-282dd5978991 > drwxr-xr-x 3 jboss informix 512 Oct 5 23:35 5430e295-1afa-4257-a2e0-e08b980b7e35 > drwxr-xr-x 3 jboss informix 512 Oct 6 14:53 5a265551-8f04-48c9-8945-abf830e54852 > drwxr-xr-x 3 jboss informix 512 Oct 6 13:46 70a1f863-7e84-40df-9206-23690bcf3ef6 > drwxr-xr-x 3 jboss informix 512 Oct 5 22:02 7186627a-5a89-4334-bdc2-8bfb944e3841 > drwxr-xr-x 3 jboss informix 512 Oct 6 14:52 85663b19-7e4e-48e9-8988-bd24c11fe4d4 > drwxr-xr-x 3 jboss informix 512 Oct 5 23:39 8842f374-85b7-4018-a1fc-6274cb704785 > drwxr-xr-x 3 jboss informix 512 Oct 5 22:05 973d7e32-efe5-4ffa-8f02-079cb7f29e71 > drwxr-x--- 3 oracle dba 2560 Aug 30 00:00 CVU_18.0.0.0.0_oracle > drwxr-xr-x 3 jboss informix 512 Oct 5 22:06 b8975817-9381-41a3-a512-e8fc6596fa7a > drwxr-xr-x 3 jboss informix 512 Oct 6 13:40 bd0c1dd7-e8c6-413d-b658-f3c5236bba34 > drwxr-xr-x 3 jboss informix 512 Oct 6 14:54 c3aa3f01-66df-4066-bb35-fed4bd0ad559 > drwxr-xr-x 3 jboss informix 512 Oct 5 23:32 c66c2972-ad28-49e9-a7ff-a7ceed5b7ea3 > drwxr-xr-x 3 jboss informix 512 Oct 5 23:24 ca8816d8-ad10-4860-a18b-0c09b37ed88b > drwxr-xr-x 3 jboss informix 512 Oct 6 13:50 cc799f82-ed02-4dc4-b56e-ffe0d8eeab75 > drwx------ 2 langfr staff 512 Nov 15 2006 orbit-lafr > -rw-rw-rw- 1 langfr staff 2383862 Oct 5 03:17 patchdiag.xref > -rw------- 1 root root 314461 Oct 6 15:32 wscon-:0-5saqic}} > {{sb2000.[neu2l]/var/tmp. ls -l 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/*/current > 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-core/current: > total 2 > drwxr-xr-x 7 jboss informix 512 Oct 6 14:55 6.0.2.Final > 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly-servlet/current: > total 2 > drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final > 396f75f7-45b0-4b50-9607-9060cabf018b/maven/org.jboss.universe_community-universe/wildfly/current: > total 2 > drwxr-xr-x 6 jboss informix 512 Oct 6 14:55 14.0.1.Final}} > Created by galleon feature pack build (galleon-pack/wildfly-feature-pack-build.xml). -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2890) [DMN Designer] DMNDiagram properties

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-2890?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2890: -------------------------------- Sprint: 2018 Week 42-44 (was: 2018 Week 39-41) > [DMN Designer] DMNDiagram properties > ------------------------------------ > > Key: DROOLS-2890 > URL: https://issues.jboss.org/browse/DROOLS-2890 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.10.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > Fix For: 7.10.0.Final > > > The {{DMNDiagram}} node needs to expose the following properties (from [~tirelli] on DROOLS-[2870|https://issues.jboss.org/browse/DROOLS-2870?focusedCommentId...) > {quote} > The Definitions properties that I think we need to expose are: > * Id (probably read only) > * name (needs to be editable; can default to the file name but should remain editable) > * namespace > * Also, the "description" element should probably be exposed somehow, although with lower priority. If you want just the minimal set, then the above. > {quote} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11112) WildFly intermittently fails to add pooled-connection-factory but it still got registered after

by ehsavoie Hugonnet (Jira)

[ https://issues.jboss.org/browse/WFLY-11112?page=com.atlassian.jira.plugin... ] ehsavoie Hugonnet commented on WFLY-11112: ------------------------------------------ [~istraka][~msvehla] What is the WF15 build ? There were some changes on JNDI registration in WF15 for pcf. > WildFly intermittently fails to add pooled-connection-factory but it still got registered after > ----------------------------------------------------------------------------------------------- > > Key: WFLY-11112 > URL: https://issues.jboss.org/browse/WFLY-11112 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 14.0.0.Final, 15.0.0.Alpha1 > Reporter: Ivan Straka > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: server.log, standalone-full.xml > > > We see following error in log of WildFly (master): > {code} > 2018-10-03 22:28:02,503 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default"), > ("pooled-connection-factory" => "activemq-ra") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.JmsXA-bkp"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.JmsXA-bkp]"] > } > {code} > Factory is defined: > {code:java} > <pooled-connection-factory name="activemq-ra" entries="java:/JmsXA-bkp java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/> > {code} > However factory is registered after and deployment is able to use it. Error is logged intermittently. > Log file and xml configuration file are enclosed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10945) JDK11 ws testsuite SSL failures

by Martin Choma (Jira)

[ https://issues.jboss.org/browse/WFLY-10945?page=com.atlassian.jira.plugin... ] Martin Choma commented on WFLY-10945: ------------------------------------- Regarding TLSv1.2 issue this looks similar https://markmail.org/message/5ckezyfj5vj2v63r . [~jbliznak] Is bouncy castle provider involved in test? It is not obvious at first glance, but is it possible Bouncy Castle is registred before JSSE on client side or server side? > JDK11 ws testsuite SSL failures > ------------------------------- > > Key: WFLY-10945 > URL: https://issues.jboss.org/browse/WFLY-10945 > Project: WildFly > Issue Type: Sub-task > Components: Test Suite > Affects Versions: 14.0.0.Beta2 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Blocker > Fix For: 15.0.0.Alpha1 > > > ws testsuite failures on JDK-11: > * missing local IP in SubjectAlternativeNamesExtension > * TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 + TLS1.2 seems buggy on JDK-11: Invalid ECDH ServerKeyExchange signature > * not issue after switching to TLS1.1 or to ciphersuite TLS_RSA_WITH_AES_256_CBC_SHA256 -> JDK bug -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AG-96) Exception sorter functionality

by Jesper Pedersen (Jira)

Jesper Pedersen created AG-96: --------------------------------- Summary: Exception sorter functionality Key: AG-96 URL: https://issues.jboss.org/browse/AG-96 Project: Agroal Issue Type: Enhancement Components: pool Reporter: Jesper Pedersen Assignee: Luis Barreiro It should be possible to register an exception sorter that determines if a SQLException is fatal for the connection, and hence should be flushed upon return to the pool -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 7 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 October 2018