May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3816) ExtensionIndexService throws NPE while reading extensions on the IBM jdk

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3816?page=com.atlassian.jira.plugi... ] Stuart Douglas commented on WFCORE-3816: ---------------------------------------- What does the stack trace look like? I are you sure it is that the manifest is null? > ExtensionIndexService throws NPE while reading extensions on the IBM jdk > ------------------------------------------------------------------------ > > Key: WFCORE-3816 > URL: https://issues.jboss.org/browse/WFCORE-3816 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 5.0.0.Alpha7 > Environment: {noformat} > java version "1.8.0_161" > Java(TM) SE Runtime Environment (build 8.0.5.11 - pxa6480sr5fp11-20180326_01(SR5 FP11)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64 Compressed References 20180309_380776 (JIT enabled, AOT enabled) > OpenJ9 - 49fcaf39 > OMR - 5cbbadf > IBM - 4453dac) > JCL - 20180319_01 based on Oracle jdk8u161-b12 > {noformat} > Reporter: Petr Kremensky > Assignee: Petr Kremensky > > https://github.com/wildfly/wildfly-core/blob/5.0.0.Alpha7/server/src/main... reads extensions from jars manifest like: > {code:java} > File jar = new File(<jar>) > final JarFile jarFile = new JarFile(jar); > final Manifest manifest = jarFile.getManifest(); > final Attributes mainAttributes = manifest.getMainAttributes(); > ... > {code} > The latest [IBM jdk 8.0-5.11|https://developer.ibm.com/javasdk/downloads/sdk8/] (and possible some of previous releases) contains some jars \[1\] where {{manifest.getMainAttributes();}} throws NPE, causing deploy operation of archive with Extension-List to fail, see WFLY-10349. > \[1\] > ibm-java-8.0-5.11/jre/lib/ext/traceformat.jar: java.lang.NullPointerException > ibm-java-8.0-5.11/jre/lib/ext/dtfj.jar: java.lang.NullPointerException > ibm-java-8.0-5.11/jre/lib/ext/dtfjview.jar: java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3834) Upgrade WildFly Discovery to 1.1.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3834?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3834: ---------------------------------------- Assignee: David Lloyd (was: Brian Stansberry) > Upgrade WildFly Discovery to 1.1.1.Final > ---------------------------------------- > > Key: WFCORE-3834 > URL: https://issues.jboss.org/browse/WFCORE-3834 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Discovery > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 5.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3834) Upgrade WildFly Discovery to 1.1.1.Final

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3834?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-3834: ---------------------------------------- Assignee: Brian Stansberry (was: David Lloyd) > Upgrade WildFly Discovery to 1.1.1.Final > ---------------------------------------- > > Key: WFCORE-3834 > URL: https://issues.jboss.org/browse/WFCORE-3834 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Discovery > Reporter: David Lloyd > Assignee: Brian Stansberry > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-206) Investegate b21 & b12 Docker Failures

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-206?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-206: ------------------------------------------ Sprint: Kiali QE Sprint 5 (was: Kiali Sprint #5) > Investegate b21 & b12 Docker Failures > ------------------------------------- > > Key: SWSQE-206 > URL: https://issues.jboss.org/browse/SWSQE-206 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > Priority: Minor > > Docker periodical needs to be restarted, which is causing pod failures. This issue appears to have started when clusters were upgraded to OS3.9. > Investigate reason for failures. Resolve if at all possible. > Temp work-around: > 1) Restart docker service > 2) Reboot instance if #1 failed -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10238) Wsprovide tool doesn't generate/keep class files on JDK10

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10238?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-10238. ------------------------------- Resolution: Done > Wsprovide tool doesn't generate/keep class files on JDK10 > --------------------------------------------------------- > > Key: WFLY-10238 > URL: https://issues.jboss.org/browse/WFLY-10238 > Project: WildFly > Issue Type: Bug > Components: Web Services > Reporter: Marek Kopecký > Assignee: R Searls > Priority: Blocker > Fix For: 13.0.0.Beta1 > > Attachments: classes.zip > > > Wsprovide tool doesn't keep class files on JDK10 > Example: > {noformat} > [mkopecky@localhost bin]$ jdk8 > [mkopecky@localhost bin]$ java -version > java version "1.8.0_111" > Java(TM) SE Runtime Environment (build 1.8.0_111-b14) > Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode) > [mkopecky@localhost bin]$ ./wsprovide.sh -k -c ~/erase10/classes -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > Could not find log4j.properties or log4j.xml configuration, logging to console. > java2ws -s /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -classdir /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -d /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -verbose -cp /home/mkopecky/erase10/classes/: -wrapperbean -createxsdimports org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > java2ws - Apache CXF 3.2.4 > [mkopecky@localhost bin]$ find out/ | grep class > out/org/jboss/as/testsuite/integration/scripts/test/tools/jaxws/EchoPlus1.class > out/org/jboss/as/testsuite/integration/scripts/test/tools/jaxws/EchoPlus1Response.class > [mkopecky@localhost bin]$ jdk10 > [mkopecky@localhost bin]$ rm -rf out > [mkopecky@localhost bin]$ java -version > java version "10" 2018-03-20 > Java(TM) SE Runtime Environment 18.3 (build 10+46) > Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10+46, mixed mode) > [mkopecky@localhost bin]$ ./wsprovide.sh -k -c ~/erase10/classes -o out org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > Could not find log4j.properties or log4j.xml configuration, logging to console. > java2ws -s /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -classdir /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -d /home/mkopecky/playground/wf/wfly.22/wfly.22/bin/out -verbose -cp /home/mkopecky/erase10/classes/: -wrapperbean -createxsdimports org.jboss.as.testsuite.integration.scripts.test.tools.Echo1Impl > java2ws - Apache CXF 3.2.4 > [mkopecky@localhost bin]$ find out/ | grep class > [mkopecky@localhost bin]$ > {noformat} > I attached input class files. I see this issue on WF with latest WS. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10205) Upgrade apache-cxf from 3.2.4 to 3.2.4-jbossorg-1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10205?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-10205. ------------------------------- Resolution: Done > Upgrade apache-cxf from 3.2.4 to 3.2.4-jbossorg-1 > ------------------------------------------------- > > Key: WFLY-10205 > URL: https://issues.jboss.org/browse/WFLY-10205 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Lin Gao > Assignee: Alessio Soldano > Priority: Blocker > Labels: downstream_dependency > Fix For: 13.0.0.Beta1 > > > apache-cxf needs to be upgraded to include fixes for: > * https://issues.apache.org/jira/browse/CXF-7682 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-214) Update Cluster Selinux Policy to Disabled and Update Packages on Openshift Clusters

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-214?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-214. ------------------------------------------- Resolution: Done > Update Cluster Selinux Policy to Disabled and Update Packages on Openshift Clusters > ----------------------------------------------------------------------------------- > > Key: SWSQE-214 > URL: https://issues.jboss.org/browse/SWSQE-214 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > - Cluster 1 Configurations stills uses Permissive by setenforce command, which means if the node needs to be restarted for any reason, when it returns, it will return with enforcing policy. > Also taking the opportunity to update the packages -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10203) Upgrade JBossWS to 5.2.1.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-10203?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-10203. ------------------------------- Resolution: Done > Upgrade JBossWS to 5.2.1.Final > ------------------------------ > > Key: WFLY-10203 > URL: https://issues.jboss.org/browse/WFLY-10203 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-213) Add B13 to Openshift cluster 3

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-213?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-213: ------------------------------------------ Summary: Add B13 to Openshift cluster 3 (was: Add B13 to Openshift cluster 2) Description: Because SWSQE-200, it is better moving b13 to openshift cluster 3 than openshift cluster 1. Team: (was: Infrastructure) > Add B13 to Openshift cluster 3 > ------------------------------ > > Key: SWSQE-213 > URL: https://issues.jboss.org/browse/SWSQE-213 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > > Because SWSQE-200, it is better moving b13 to openshift cluster 3 than openshift cluster 1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-213) Add B13 to Openshift cluster 2

by Guilherme Baufaker Rêgo (JIRA)

[ https://issues.jboss.org/browse/SWSQE-213?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-213: ------------------------------------------ Summary: Add B13 to Openshift cluster 2 (was: Re-add B13 to Openshift cluster 1) > Add B13 to Openshift cluster 2 > ------------------------------ > > Key: SWSQE-213 > URL: https://issues.jboss.org/browse/SWSQE-213 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > -- 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 May 2018