September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9053) AbstractMethodError with Hibernate 5.2

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9053?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-9053: ------------------------------------ [~heruan] if you have made changes to WildFly, you could push your branch to github and link it here, so others can see your changes. Did you include any CDI/Weld jars in your EAR? Perhaps you could also show us the contents of your ear lib folder (jar tf vaadin-sessions-demo-1.0.0.ear). Are there any other exceptions previous to the "AbstractMethodError: org.jboss.weld.metadata.ScanningPredicate.test"? > AbstractMethodError with Hibernate 5.2 > -------------------------------------- > > Key: WFLY-9053 > URL: https://issues.jboss.org/browse/WFLY-9053 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Giovanni Lovato > Assignee: Scott Marlow > > I'm deploying an EAR specifying in its {{persistence.xml}} to use Hibernate 5.2 as JPA provider: > {code:xml} > <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2" /> > {code} > Hibernate 5.2 modules are placed in the {{modules}} directory. > This configuration works in 10.1.0.Final but in 11.0.0.Alpha1 I get this error at deployment: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "oss-application-ear-1.0.0.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.AbstractMethodError: org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.beanManagerLifeCycle(Ljavax/enterprise/inject/spi/BeanManager;)Ljava/lang/Object; > at org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.<init>(PhaseOnePersistenceUnitServiceImpl.java:89) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:485) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:279) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135) > at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Update testsuite to use EAP70 enum values and not just api versions

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-9307: ---------------------------- Steps to Reproduce: See core jira: (was: See attached configs. Mgmt user is eap70-host password: password 1. Start EAP7.1 DC with attached [^domain.xml] (download it to {{jboss-eap-7.1/domain/configuration}}). {code}./jboss-eap-7.1/bin/domain.sh -b 127.0.0.1 -bmanagement 127.0.0.1{code} 2. Start EAP7.0 HC with attached [^host-slave.xml] (download it to {{jboss-eap-7.0/domain/configuration}}), pointing it to discover the already started up DC bound to loopback. {code}./jboss-eap-7.0/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -b <NON_LOOPBACK_IP_ADDR> -bmanagement <NON_LOOPBACK_IP_ADDR>{code}) > Update testsuite to use EAP70 enum values and not just api versions > ------------------------------------------------------------------- > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 > The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Update testsuite to use EAP70 enum values and not just api versions

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-9307: ---------------------------- Steps to Reproduce: See core jira: https://issues.jboss.org/browse/WFCORE-3226 (was: See core jira: ) > Update testsuite to use EAP70 enum values and not just api versions > ------------------------------------------------------------------- > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 > The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Update testsuite to use EAP70 enum values and not just api versions

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-9307: ---------------------------- Git Pull Request: (was: https://github.com/jbossas/wildfly-core-eap/pull/405) > Update testsuite to use EAP70 enum values and not just api versions > ------------------------------------------------------------------- > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 > The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Legacy slaves can't understand new enum version values

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-9307: ---------------------------- Description: The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 The existing tests in mixed-domain should be updated to use this enum value. was: [Host Controller] 10:53:50,342 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 2) WFLYCTL0013: Operation ("add") failed - address: ([("host-exclude" => "EAP70")]) - failure description: "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]" [Host Controller] 10:53:50,366 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 2) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]"}} [Host Controller] 10:53:50,448 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://192.168.122.71:9999 -- 1-$- [Host Controller] 10:53:50,449 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain. [Host Controller] 10:53:50,451 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect > Legacy slaves can't understand new enum version values > ------------------------------------------------------ > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 > The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Update testsuite to use EAP70 enum values and not just api versions

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills updated WFLY-9307: ---------------------------- Summary: Update testsuite to use EAP70 enum values and not just api versions (was: Legacy slaves can't understand new enum version values) > Update testsuite to use EAP70 enum values and not just api versions > ------------------------------------------------------------------- > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > The associated issue in wildfly-core is: https://issues.jboss.org/browse/WFCORE-3226 > The existing tests in mixed-domain should be updated to use this enum value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9307) Legacy slaves can't understand new enum version values

by Ken Wills (JIRA)

[ https://issues.jboss.org/browse/WFLY-9307?page=com.atlassian.jira.plugin.... ] Ken Wills moved JBEAP-13030 to WFLY-9307: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9307 (was: JBEAP-13030) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management Test Suite (was: Domain Management) Affects Version/s: 11.0.0.CR1 (was: 7.1.0.CR1) > Legacy slaves can't understand new enum version values > ------------------------------------------------------ > > Key: WFLY-9307 > URL: https://issues.jboss.org/browse/WFLY-9307 > Project: WildFly > Issue Type: Bug > Components: Domain Management, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Blocker > > [Host Controller] 10:53:50,342 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 2) WFLYCTL0013: Operation ("add") failed - address: ([("host-exclude" => "EAP70")]) - failure description: "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]" > [Host Controller] 10:53:50,366 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 2) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "WFLYCTL0248: Invalid value EAP7.0 for host-release; legal values are [EAP6.3, EAP6.2, WildFly10.0, EAP6.4]"}} > [Host Controller] 10:53:50,448 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://192.168.122.71:9999 -- 1-$- > [Host Controller] 10:53:50,449 WARN [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain. > [Host Controller] 10:53:50,451 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9053) AbstractMethodError with Hibernate 5.2

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/WFLY-9053?page=com.atlassian.jira.plugin.... ] Sanne Grinovero commented on WFLY-9053: --------------------------------------- Hi [~heruan], yes that's a similar exception but it's not the same one. It seems related to CDI .. are you sure that's caused by the Hibernate upgrade? > AbstractMethodError with Hibernate 5.2 > -------------------------------------- > > Key: WFLY-9053 > URL: https://issues.jboss.org/browse/WFLY-9053 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Giovanni Lovato > Assignee: Scott Marlow > > I'm deploying an EAR specifying in its {{persistence.xml}} to use Hibernate 5.2 as JPA provider: > {code:xml} > <property name="jboss.as.jpa.providerModule" value="org.hibernate:5.2" /> > {code} > Hibernate 5.2 modules are placed in the {{modules}} directory. > This configuration works in 10.1.0.Final but in 11.0.0.Alpha1 I get this error at deployment: > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."oss-application-ear-1.0.0.ear".FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "oss-application-ear-1.0.0.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.AbstractMethodError: org.jboss.as.jpa.hibernate5.HibernatePersistenceProviderAdaptor.beanManagerLifeCycle(Ljavax/enterprise/inject/spi/BeanManager;)Ljava/lang/Object; > at org.jboss.as.jpa.service.PhaseOnePersistenceUnitServiceImpl.<init>(PhaseOnePersistenceUnitServiceImpl.java:89) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deployPersistenceUnitPhaseOne(PersistenceUnitServiceHandler.java:485) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.addPuService(PersistenceUnitServiceHandler.java:279) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.handleEarDeployment(PersistenceUnitServiceHandler.java:228) > at org.jboss.as.jpa.processor.PersistenceUnitServiceHandler.deploy(PersistenceUnitServiceHandler.java:135) > at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:52) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9251) Security context is not thread safe

by Rémy Delerue (JIRA)

[ https://issues.jboss.org/browse/WFLY-9251?page=com.atlassian.jira.plugin.... ] Rémy Delerue commented on WFLY-9251: ------------------------------------ I'm not pretty sure yet but it seams changing the configuration that way: <security-domain name="TestSecurityDomain" cache-type="*default*"> => <security-domain name="TestSecurityDomain" cache-type="*none*"> can workaround our issue. I'll check the implication of that tomorrow (is it better than using a synchronized block containing the logout and the login for example ?). > Security context is not thread safe > ----------------------------------- > > Key: WFLY-9251 > URL: https://issues.jboss.org/browse/WFLY-9251 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 10.1.0.Final > Environment: Windows, LInux > Reporter: charles ghislain > Assignee: Darran Lofthouse > Labels: jaas, security, security-context, thread-safety, threads > Attachments: wildfly-auth-overloader.js, wildflytestauthcontext-2.zip, wildflytestauthcontext.zip > > > Using a custom JAAS login module, we sometimes fail to obtain the authenticated subject from the 'javax.security.auth.Subject.container' policy context. This appear to be related to the worker threads. > See the reproduction steps below. When a wildfly instance attempts to authenticate 500 requests coming simultaneously, a bunch of them fail. If you configure wildfly to only use a single worker thread and a single task thread, this issue disappears. > The issue is as follow: > I login using HttpServletRequest#login. > Right after that, login.getUserPrincipal return the correct principal. > However, sometimes, PolicyContext.getContext("javax.security.auth.Subject.container") returns null. Right after the login. > In our production app, PolicyContext.getContext("javax.security.auth.Subject.container") returns null during some EJB call, throwing random exceptions from various parts of the application. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-179) UI crash monitoring/utilzation for JMS Queue - Sprint-68

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-179?page=com.atlassian.jira.pl... ] Matt Mahoney reassigned HAWKULARQE-179: --------------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > UI crash monitoring/utilzation for JMS Queue - Sprint-68 > -------------------------------------------------------- > > Key: HAWKULARQE-179 > URL: https://issues.jboss.org/browse/HAWKULARQE-179 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Sunil kondkar > > UI crash when viewing the monitoring/utilzation for JMS Queue or JMS Topic > Issue: https://github.com/ManageIQ/manageiq-ui-classic/issues/1880 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017