January 2019 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-4160) Test failure of WSProviderTestCaseForked on JDK11+Windows

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4160?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4160: ----------------------------------- Because I wasn't able to find the difference on JBossWS/CXF side I started to dig deeper on JDK side. I was able to locate the place after which RHEL execution continues without error but Win execution reports some number of errors (log.nerrors counter > 0) at http://hg.openjdk.java.net/jdk/jdk11/file/jdk-11+28/src/jdk.compiler/shar... I was not able to find the root cause at alocated time, but still I would say the problem comes probably sooner on JBossWS/CXF side and I missed it somewhere. Also there might be problem with the test as it is rather complicated scenario and all other tests with ws-provide* and ws-consume* stuff works on all OS/JVM... > Test failure of WSProviderTestCaseForked on JDK11+Windows > --------------------------------------------------------- > > Key: JBWS-4160 > URL: https://issues.jboss.org/browse/JBWS-4160 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Priority: Major > > We are seeing failing test org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory > https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... > The error message is: > {code:java} > java.lang.reflect.InvocationTargetException > at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) > Caused by: java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse > at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) > {code} > During the test this is called https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/" should contain both *.java and *.class files but it does not on Win+JDK11. The cause of the test error message is then the fact there are no *.class files in tested directory. > In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler is used which then calls JDK internal compiler task https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... which should create these files. > When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there seems to be no relevant difference at what parameters are passed to methods up to this point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4160) Test failure of WSProviderTestCaseForked on JDK11+Windows

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4160?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4160: ------------------------------ Description: We are seeing failing test org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... The error message is: {code:java} java.lang.reflect.InvocationTargetException at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) Caused by: java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) {code} During the test this is called https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/" should contain both *.java and *.class files but it does not on Win+JDK11. The cause of the test error message is then the fact there are no *.class files in tested directory. In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler is used which then calls JDK internal compiler task https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... which should create these files. When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there seems to be no relevant difference at what parameters are passed to methods up to this point. was: We are seeing failing test org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... The error message is: {code:java} java.lang.reflect.InvocationTargetException at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) Caused by: java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) {code} During the test this is called https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/" should contain both *.java and *.class files but it does not on Win+JDK11. The cause of the test error message is then the fact there are no *.class files in tested directory. In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler which then calls JDK internal compiler task https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... which should create these files. When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there seems to be no difference up to this point. > Test failure of WSProviderTestCaseForked on JDK11+Windows > --------------------------------------------------------- > > Key: JBWS-4160 > URL: https://issues.jboss.org/browse/JBWS-4160 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Priority: Major > > We are seeing failing test org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory > https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... > The error message is: > {code:java} > java.lang.reflect.InvocationTargetException > at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) > Caused by: java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse > at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) > {code} > During the test this is called https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/" should contain both *.java and *.class files but it does not on Win+JDK11. The cause of the test error message is then the fact there are no *.class files in tested directory. > In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler is used which then calls JDK internal compiler task https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... which should create these files. > When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there seems to be no relevant difference at what parameters are passed to methods up to this point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4160) Test failure of WSProviderTestCaseForked on JDK11+Windows

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4160: --------------------------------- Summary: Test failure of WSProviderTestCaseForked on JDK11+Windows Key: JBWS-4160 URL: https://issues.jboss.org/browse/JBWS-4160 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.2.4.Final Reporter: Jan Blizňák We are seeing failing test org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked#testOutputDirectory https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... The error message is: {code:java} java.lang.reflect.InvocationTargetException at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) Caused by: java.lang.ClassNotFoundException: org.jboss.test.ws.jaxws.smoke.tools.jaxws.AddResponse at org.jboss.test.ws.jaxws.smoke.tools.WSProviderTestCaseForked.testOutputDirectory(WSProviderTestCaseForked.java:105) {code} During the test this is called https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... after which "target/wsprovide/java/org/jboss/test/ws/jaxws/smoke/tools/jaxws/" should contain both *.java and *.class files but it does not on Win+JDK11. The cause of the test error message is then the fact there are no *.class files in tested directory. In case of JDK11 the Jdk9PlusJBossModulesAwareCompiler which then calls JDK internal compiler task https://github.com/jbossws/jbossws-cxf/blob/jbossws-cxf-5.2.4.Final/modul... which should create these files. When I was trying to debug it on both Win and RHEL with JDK11 and compare results, there seems to be no difference up to this point. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4157) Move to EJB API 3.2 dependency (sync with WildFly)

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4157?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4157: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/95 PR sent https://github.com/jbossws/jbossws-cxf/pull/95 > Move to EJB API 3.2 dependency (sync with WildFly) > -------------------------------------------------- > > Key: JBWS-4157 > URL: https://issues.jboss.org/browse/JBWS-4157 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > JBossWS project is using JBoss EJB API 3.1 while current WildFly release (and also few previous ones) uses JBoss EJB API 3.2. We could sync that, ie. use the same version in JBossWS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4158) Move to Servlet API 4.0 dependency (sync with WildFly)

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4158?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4158: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/96 PR sent https://github.com/jbossws/jbossws-cxf/pull/96 > Move to Servlet API 4.0 dependency (sync with WildFly) > ------------------------------------------------------ > > Key: JBWS-4158 > URL: https://issues.jboss.org/browse/JBWS-4158 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > JBossWS project is using JBoss Servlet API 3.1 while current WildFly release (and also few previous ones) uses JBoss Servlet API 4.0. We could sync that, ie. use the same version in JBossWS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4159) Upgrade LittleProxy in TS to 1.1.2

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4159?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4159: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/94 PR sent https://github.com/jbossws/jbossws-cxf/pull/94 > Upgrade LittleProxy in TS to 1.1.2 > ---------------------------------- > > Key: JBWS-4159 > URL: https://issues.jboss.org/browse/JBWS-4159 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > We are using very old version of org.littleshoot:littleproxy, we could update it to the latest stable version so we could remove one more workaround from our TS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4159) Upgrade LittleProxy in TS to 1.1.2

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4159?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4159: ------------------------------ Description: We are using very old version of org.littleshoot:littleproxy, we could update it to the latest stable version so we could remove one more workaround from our TS. (was: We are using very old version of org.littleshoot:littleproxy, we could update it to the latest stable version.) > Upgrade LittleProxy in TS to 1.1.2 > ---------------------------------- > > Key: JBWS-4159 > URL: https://issues.jboss.org/browse/JBWS-4159 > Project: JBoss Web Services > Issue Type: Task > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > We are using very old version of org.littleshoot:littleproxy, we could update it to the latest stable version so we could remove one more workaround from our TS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4159) Upgrade LittleProxy in TS to 1.1.2

by Jan Blizňák (Jira)

Jan Blizňák created JBWS-4159: --------------------------------- Summary: Upgrade LittleProxy in TS to 1.1.2 Key: JBWS-4159 URL: https://issues.jboss.org/browse/JBWS-4159 Project: JBoss Web Services Issue Type: Task Affects Versions: jbossws-cxf-5.2.4.Final Reporter: Jan Blizňák Assignee: Jan Blizňák We are using very old version of org.littleshoot:littleproxy, we could update it to the latest stable version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4158) Move to Servlet API 4.0 dependency (sync with WildFly)

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4158?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4158: ------------------------------ Assignee: Jan Blizňák > Move to Servlet API 4.0 dependency (sync with WildFly) > ------------------------------------------------------ > > Key: JBWS-4158 > URL: https://issues.jboss.org/browse/JBWS-4158 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Major > > JBossWS project is using JBoss Servlet API 3.1 while current WildFly release (and also few previous ones) uses JBoss Servlet API 4.0. We could sync that, ie. use the same version in JBossWS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4158) Move to Servlet API 4.0 dependency (sync with WildFly)

by Jan Blizňák (Jira)

[ https://issues.jboss.org/browse/JBWS-4158?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4158: ----------------------------------- See WFLY-11573 Also this should be safe as no methods were removed from 3.1 vs 4.0, see https://abi-laboratory.pro/?view=archives_report&lang=java&l=javax.servle... > Move to Servlet API 4.0 dependency (sync with WildFly) > ------------------------------------------------------ > > Key: JBWS-4158 > URL: https://issues.jboss.org/browse/JBWS-4158 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.4.Final > Reporter: Jan Blizňák > Priority: Major > > JBossWS project is using JBoss Servlet API 3.1 while current WildFly release (and also few previous ones) uses JBoss Servlet API 4.0. We could sync that, ie. use the same version in JBossWS. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues January 2019