August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3205: --------------------------------------- [~emmartins] IMO a user shouldn't have to configure the log manager in order for the embedded server to work. In most cases I would guess that the embedded server is not being launched in a modular environment. That is one of the main issues and why the log manager gets loaded twice on the class path. Adding it to the system package would only work in a modular environment. > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3205: --------------------------------------- [~ge0ffrey] Currently excluding the jboss-logmanager dependency would likely be the easiest solution. The only other solution I can think of would require changes before the the embedded server is started. Offline CLI does this and it's really kind of complex IMO. > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

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

by Giovanni Lovato (JIRA)

[ https://issues.jboss.org/browse/WFLY-9053?page=com.atlassian.jira.plugin.... ] Giovanni Lovato commented on WFLY-9053: --------------------------------------- Thank you [~sannegrinovero] for the update. Just to make this clear: the exception reported by this issue happens when ORM 5.2 modules are unpacked as described at https://docs.jboss.org/hibernate/orm/5.2/topical/html_single/wildfly/Wild... in WildFly 11. I see in your PR that only the classifier has changed, thus not resolving the exception. Maybe another PR is involved? > 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, 8 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 closed WFLY-9053. --------------------------------- > 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, 8 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 all, we will not update WildFly 11 to Hibernate ORM 5.2.x, but we will be making Hibernate ORM 5.2.x releases which people can unpack on WF11 to use it as an alternative. The latest ORM releases were meant for WildFly 10, so I patched it to target WildFly 11 instead. This should work fine with the next release Hibernate ORM 5.2.11.Final : HHH-11950 > 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, 8 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 updated WFLY-9053: ---------------------------------- Affects Version/s: (was: 11.0.0.Alpha1) > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9275) wildfly naming api(on ear/war) lookup remote SessionBean on multi server fail, all request recieved by one server(client)

by Loren Chang (JIRA)

Loren Chang created WFLY-9275: --------------------------------- Summary: wildfly naming api(on ear/war) lookup remote SessionBean on multi server fail, all request recieved by one server(client) Key: WFLY-9275 URL: https://issues.jboss.org/browse/WFLY-9275 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 10.0.0.Final Reporter: Loren Chang -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] Eduardo Martins edited comment on WFCORE-3205 at 8/29/17 9:03 AM: ------------------------------------------------------------------ Honestly I don't see any bug here, just lacking proper documentation about the class loading specifics? was (Author: emmartins): Honestly I don't see any bug here, just proper documentation about the class loading specifics? > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFCORE-3205: ----------------------------------------- Honestly I don't see any bug here, just proper documentation about the class loading specifics? > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3205) Logging does not work in the embedded server

by Eduardo Martins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3205?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFCORE-3205: ----------------------------------------- [~ge0ffrey] create the embedded as the migration tool does above, pass "org.jboss.logmanager" as system package. > Logging does not work in the embedded server > -------------------------------------------- > > Key: WFCORE-3205 > URL: https://issues.jboss.org/browse/WFCORE-3205 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > > When using the {{EmbeddedProcessFactory}} logging does not appear to work. Debugging shows a different {{LogContext}} associated with the loggers than the one associated with the logging subsystem. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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