August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ] Richard Opalka updated WFLY-12063: ---------------------------------- Labels: blocker-WF18 jdk13 (was: blocker-WF18) > ClassFormatError on JDK13 > ------------------------- > > Key: WFLY-12063 > URL: https://issues.jboss.org/browse/WFLY-12063 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Richard Opalka > Assignee: Scott Marlow > Priority: Critical > Labels: blocker-WF18, jdk13 > Attachments: server.log, test.log > > > The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly. > Affected tests are: > --- > [ERROR] Errors: > [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment > [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment > [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment > [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment > [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment > [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy... > [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment > [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment > [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment > [INFO] > [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14 > --- -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4629) Upgrade JBoss MSC to 1.4.9.Final

by Richard Opalka (Jira)

Richard Opalka created WFCORE-4629: -------------------------------------- Summary: Upgrade JBoss MSC to 1.4.9.Final Key: WFCORE-4629 URL: https://issues.jboss.org/browse/WFCORE-4629 Project: WildFly Core Issue Type: Component Upgrade Components: Server Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 10.0.0.Beta5 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4628) Upgrade jboss-jboss-interceptors-api_spec from 1.0.1.Final to 2.0.0.Final

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFCORE-4628?page=com.atlassian.jira.plugi... ] Yeray Borges moved WFLY-12388 to WFCORE-4628: --------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4628 (was: WFLY-12388) Component/s: Build System (was: EE) > Upgrade jboss-jboss-interceptors-api_spec from 1.0.1.Final to 2.0.0.Final > ------------------------------------------------------------------------- > > Key: WFCORE-4628 > URL: https://issues.jboss.org/browse/WFCORE-4628 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Upgrade Interceptors API JSR-318 to Jakarta EE > Fork: https://github.com/jboss/jboss-jakarta-interceptors-api_spec > Working branch: [JBEE-206 | https://github.com/jboss/jboss-jakarta-interceptors-api_spec/tree/JBEE-206] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12388) Upgrade jboss-jboss-interceptors-api_spec from 1.0.1.Final to 2.0.0.Final

by Yeray Borges (Jira)

[ https://issues.jboss.org/browse/WFLY-12388?page=com.atlassian.jira.plugin... ] Yeray Borges updated WFLY-12388: -------------------------------- Parent: (was: WFLY-12300) Issue Type: Task (was: Sub-task) > Upgrade jboss-jboss-interceptors-api_spec from 1.0.1.Final to 2.0.0.Final > ------------------------------------------------------------------------- > > Key: WFLY-12388 > URL: https://issues.jboss.org/browse/WFLY-12388 > Project: WildFly > Issue Type: Task > Components: EE > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > > Upgrade Interceptors API JSR-318 to Jakarta EE > Fork: https://github.com/jboss/jboss-jakarta-interceptors-api_spec > Working branch: [JBEE-206 | https://github.com/jboss/jboss-jakarta-interceptors-api_spec/tree/JBEE-206] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11218) IIOP call does not work with transaction started on client side when run on IBM JDK

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-11218?page=com.atlassian.jira.plugin... ] Tomasz Adamski commented on WFLY-11218: --------------------------------------- This issue can be solved by explicitly tell IBM JVM to use sun's Util class. In order to do this, each client/server that runs on it should set following system property: -Djavax.rmi.CORBA.UtilClass=com.sun.corba.se.impl.javax.rmi.CORBA.Util Ivan Straka could you please confirm/double-check in your reproducer. > IIOP call does not work with transaction started on client side when run on IBM JDK > ----------------------------------------------------------------------------------- > > Key: WFLY-11218 > URL: https://issues.jboss.org/browse/WFLY-11218 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 14.0.0.Final, 15.0.0.Beta1 > Environment: IBM JDK 8 > Reporter: Ivan Straka > Assignee: Tomasz Adamski > Priority: Blocker > Labels: blocker-WF18 > > Issue is valid only for IBM JDK 8...scenario works on oracle jdk 8 and 11 and openjdk 8. > Scenario (using CORBA): > # start transaction > # lookup > # IIOP call > # EJB perform a basic operation and return (no failure is expected) > IIOP call fails with following exception: > {code:java} > java.lang.NullPointerException: null > at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.sentFullMessage(CorbaMessageMediatorImpl.java:429) > at com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.sendCancelRequestIfFinalFragmentNotSent(CorbaMessageMediatorImpl.java:394) > at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.endRequest(CorbaClientRequestDispatcherImpl.java:895) > at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.releaseReply(CorbaClientDelegateImpl.java:167) > at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:253) > at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:139) > at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:91) > at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:408) > at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:274) > at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:132) > at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:61) > at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:695) > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:324) > at javax.naming.InitialContext.init(InitialContext.java:255) > at javax.naming.InitialContext.<init>(InitialContext.java:227) > at org.jboss.as.test.jbossts.client.utils.TxUtil.lookupIIOP(TxUtil.java:93) > at org.jboss.as.test.jbossts.client.utils.TxUtil.lookupIIOP(TxUtil.java:103) > at org.jboss.as.test.jbossts.crashrec.test.JMSCrashRecoveryTestCase.lookupCrashBeanOverIIOP(JMSCrashRecoveryTestCase.java:164) > at org.jboss.as.test.jbossts.crashrec.test.JMSCrashRecoveryTestCase.callCrashTest(JMSCrashRecoveryTestCase.java:126) > {code} > When transaction is not started on client side, IIOP call works smoothly. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8124) Unify arquillian defaultProtocol in TS

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-8124?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka commented on WFLY-8124: ---------------------------------------- hi [~jamezp] , would you be so kind and give me some guidance if the expected protocol for WFLY Arquillian extension (https://github.com/wildfly/wildfly-arquillian) is {{jmx-as7}} or different one? And in case what is the recommended protocol for WFLY testsuite. The {{rts}} and {{xts }} modules are the only one with definition of the protocol {{Servlet 3.0}} currently (probably they were used just from history) > Unify arquillian defaultProtocol in TS > -------------------------------------- > > Key: WFLY-8124 > URL: https://issues.jboss.org/browse/WFLY-8124 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, XTS > Reporter: Marek Kopecky > Assignee: Ondrej Chaloupka > Priority: Major > > Unify arquillian defaultProtocol in TS > xts a rts module use servlet protocol. Jmx protocol is standard protocol: > {noformat} > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -i servlet > testsuite/integration/rts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> > testsuite/integration/xts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -iv servlet | wc -l > 13 > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8124) Unify arquillian defaultProtocol in TS

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-8124?page=com.atlassian.jira.plugin.... ] Ondrej Chaloupka reassigned WFLY-8124: -------------------------------------- Assignee: Ondrej Chaloupka > Unify arquillian defaultProtocol in TS > -------------------------------------- > > Key: WFLY-8124 > URL: https://issues.jboss.org/browse/WFLY-8124 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite, XTS > Reporter: Marek Kopecky > Assignee: Ondrej Chaloupka > Priority: Major > > Unify arquillian defaultProtocol in TS > xts a rts module use servlet protocol. Jmx protocol is standard protocol: > {noformat} > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -i servlet > testsuite/integration/rts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> > testsuite/integration/xts/src/test/config/arq/arquillian.xml: <defaultProtocol type="Servlet 3.0" /> > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ git grep defaultProtocol | grep -iv servlet | wc -l > 13 > [mkopecky@dhcp-10-40-5-170 base] (7.x)$ > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12418) Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/WFLY-12418?page=com.atlassian.jira.plugin... ] Darran Lofthouse commented on WFLY-12418: ----------------------------------------- Had a chat with [~emmartins] this morning, it sounds like there are lot of changes flying around the boms so Eduardo will sync the boms with the component upgrades. > Move to jakarta.security.enterprise:jakarta.security.enterprise-api and org.glassfish.soteria:jakarta.security.enterprise > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12418 > URL: https://issues.jboss.org/browse/WFLY-12418 > Project: WildFly > Issue Type: Sub-task > Components: EE, Security > Reporter: Diana Vilkolakova > Assignee: Diana Vilkolakova > Priority: Major > Fix For: 18.0.0.Beta1 > > > This is simple component upgrade to jakarta since we will not be forking EE security for now. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12433) Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12433?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-12433: ----------------------------------- Fix Version/s: 18.0.0.Final > Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final > ----------------------------------------------- > > Key: WFLY-12433 > URL: https://issues.jboss.org/browse/WFLY-12433 > Project: WildFly > Issue Type: Sub-task > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12433) Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final

by Alessio Soldano (Jira)

[ https://issues.jboss.org/browse/WFLY-12433?page=com.atlassian.jira.plugin... ] Alessio Soldano updated WFLY-12433: ----------------------------------- Component/s: REST > Upgrade jboss-jaxrs-api_2.1_spec to 2.0.0.Final > ----------------------------------------------- > > Key: WFLY-12433 > URL: https://issues.jboss.org/browse/WFLY-12433 > Project: WildFly > Issue Type: Sub-task > Components: REST > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Priority: Major > Fix For: 18.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019