[JBoss JIRA] (WFLY-11794) Helloworld-classtransformer incompatibility
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11794?page=com.atlassian.jira.plugin... ]
Eduardo Martins updated WFLY-11794:
-----------------------------------
Affects Version/s: (was: 16.0.0.Beta1)
> Helloworld-classtransformer incompatibility
> -------------------------------------------
>
> Key: WFLY-11794
> URL: https://issues.jboss.org/browse/WFLY-11794
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Eduardo Martins
> Assignee: Eduardo Martins
> Priority: Major
>
> Changes done at server side, wrt JDK12 compatibility, introduced issues when deploying quickstart helloworld-classtransformer post WFLY 16 Beta:
> {code}
> 22:37:27,320 INFO [org.jboss.as.repository] (management-handler-thread - 1) WFLYDR0001: Content added at location /Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/standalone/data/content/23/641c0517f5106bee30dbc931cc7fe8784f52d7/content
> 22:37:27,350 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "helloworld-classfiletransformers.war" (runtime-name: "helloworld-classfiletransformers.war")
> 22:37:28,051 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.helloworld-classfiletransformers.war" is using a private module ("org.javassist") which may be changed or removed in future versions without notice.
> 22:37:28,108 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Instrumenting hello.server.ejb.HelloBean
> 22:37:28,166 INFO [hello.server.transformation.HelloByteCodeManipulator] (MSC service thread 1-8) Successfully instrumented hello.server.ejb.HelloBean
> 22:37:28,206 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment helloworld-classfiletransformers.war
> 22:37:28,449 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 6.0.15.Final
> 22:37:28,699 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'HelloBean' in deployment unit 'deployment "helloworld-classfiletransformers.war"' are as follows:
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.invocation.proxy.AbstractProxyFactory$1 (jar:file:/Users/emmartins/jboss/git/as/wildfly/dist-copy/target/wildfly-16.0.0.CR1-SNAPSHOT/modules/system/layers/base/org/jboss/invocation/main/jboss-invocation-1.5.2.Final.jar!/) to method java.lang.Object.clone()
> WARNING: Please consider reporting this to the maintainers of org.jboss.invocation.proxy.AbstractProxyFactory$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> 22:37:29,062 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."helloworld-classfiletransformers.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "helloworld-classfiletransformers.war"
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
> at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:106)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:460)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:480)
> at org.jboss.modules.ClassDefiner.defineClass(ClassDefiner.java:144)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.ModuleClassFactory.defineClass(ModuleClassFactory.java:56)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.defineInternal(ClassFile.java:299)
> at org.jboss.classfilewriter@1.2.4.Final//org.jboss.classfilewriter.ClassFile.define(ClassFile.java:286)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractClassFactory.defineClass(AbstractClassFactory.java:202)
> at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.proxy.AbstractProxyFactory.getCachedMethods(AbstractProxyFactory.java:162)
> at org.jboss.as.ejb3@16.0.0.CR1-SNAPSHOT//org.jboss.as.ejb3.component.stateless.StatelessComponentDescription$3.configure(StatelessComponentDescription.java:147)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.DefaultComponentViewConfigurator.configure(DefaultComponentViewConfigurator.java:91)
> at org.jboss.as.ee@16.0.0.CR1-SNAPSHOT//org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:92)
> ... 9 more
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:135)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.transform(HelloByteCodeManipulator.java:70)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloBeanClassFileTransformer.transform(HelloBeanClassFileTransformer.java:57)
> at org.jboss.as.server@8.0.0.CR1//org.jboss.as.server.deployment.module.DelegatingClassFileTransformer.transform(DelegatingClassFileTransformer.java:60)
> at org.jboss.modules.JLIClassTransformer.transform(JLIClassTransformer.java:55)
> at org.jboss.modules.ModuleClassLoader.defineClassInternal(ModuleClassLoader.java:458)
> ... 19 more
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> at org.javassist//javassist.ClassPool.get(ClassPool.java:422)
> at deployment.helloworld-classfiletransformers.war//hello.server.transformation.HelloByteCodeManipulator.getCtClass(HelloByteCodeManipulator.java:133)
> ... 24 more
> 22:37:29,154 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.8.Final
> 22:37:29,620 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started client-mappings cache from ejb container
> 22:37:29,695 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "helloworld-classfiletransformers.war")]) - failure description: {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,697 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "helloworld-classfiletransformers.war" was rolled back with the following failure message:
> {
> "WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"helloworld-classfiletransformers.war\".INSTALL" => "WFLYSRV0153: Failed to process phase INSTALL of deployment \"helloworld-classfiletransformers.war\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component HelloBean
> Caused by: java.lang.ClassFormatError: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: java.lang.RuntimeException: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1
> Caused by: javassist.NotFoundException: hello.server.ejb.HelloBean$$$view1"},
> "WFLYCTL0412: Required services that are not installed:" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService"
> ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".WeldStartService, jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]",
> "jboss.deployment.unit.\"helloworld-classfiletransformers.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"helloworld-classfiletransformers.war\".beanmanager]"
> ]
> }
> 22:37:29,727 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment helloworld-classfiletransformers.war (runtime-name: helloworld-classfiletransformers.war) in 29ms
> {code}
> It's not clear the actual QS design is something we want to keep promoting tho:
> * it teaches how to use a private module
> * we use byteman with customers, when intercepting code on the fly
> Assuming incompatibility we should drop the QS from WFLY releases, and we should rethink if we going to fix it, or replace it with a new QS.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop - java.lang.StackOverflowError
by Bruno Maioli Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Bruno Maioli Martins updated WFLY-11793:
----------------------------------------
Summary: JPA EntityManager merge infinite loop - java.lang.StackOverflowError (was: JPA EntityManager merge infinite loop - )
> JPA EntityManager merge infinite loop - java.lang.StackOverflowError
> --------------------------------------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Java EE 8
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Major
> Attachments: teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop - java.lang.StackOverflowError
by Bruno Maioli Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Bruno Maioli Martins updated WFLY-11793:
----------------------------------------
Priority: Critical (was: Major)
> JPA EntityManager merge infinite loop - java.lang.StackOverflowError
> --------------------------------------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Java EE 8
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Critical
> Attachments: teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop - java.lang.StackOverflowError
by Bruno Maioli Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Bruno Maioli Martins updated WFLY-11793:
----------------------------------------
Environment:
MAC OS Mojave
Java 11
Wildfly 15.0.1-Final
Data Base Postgresql
was:
MAC OS Mojave
Java 11
Java EE 8
Wildfly 15.0.1-Final
Data Base Postgresql
> JPA EntityManager merge infinite loop - java.lang.StackOverflowError
> --------------------------------------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Critical
> Attachments: teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop -
by Bruno Maioli Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Bruno Maioli Martins updated WFLY-11793:
----------------------------------------
Description:
Dear,
When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
If the same code runs outside of the Wildfly server context its execution occurs normally.
Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
Attach the source code of my test classes.
was:
Dear,
When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
If the same code runs outside of the Wildfly server context its execution occurs normally.
Attach the source code of my test classes.
> JPA EntityManager merge infinite loop -
> ----------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Java EE 8
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Major
> Attachments: teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Apparently the call getEntityManager.().merge(obj) attempts infinite selects to sync the object with transaction context before doing the merge.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop -
by Bruno Maioli Martins (Jira)
Bruno Maioli Martins created WFLY-11793:
-------------------------------------------
Summary: JPA EntityManager merge infinite loop -
Key: WFLY-11793
URL: https://issues.jboss.org/browse/WFLY-11793
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 15.0.1.Final
Environment: MAC OS Mojave
Java 11
Java EE 8
Wildfly 15.0.1-Final
Reporter: Bruno Maioli Martins
Assignee: Scott Marlow
Attachments: teste.zip
Dear,
When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
If the same code runs outside of the Wildfly server context its execution occurs normally.
Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11793) JPA EntityManager merge infinite loop -
by Bruno Maioli Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11793?page=com.atlassian.jira.plugin... ]
Bruno Maioli Martins updated WFLY-11793:
----------------------------------------
Environment:
MAC OS Mojave
Java 11
Java EE 8
Wildfly 15.0.1-Final
Data Base Postgresql
was:
MAC OS Mojave
Java 11
Java EE 8
Wildfly 15.0.1-Final
> JPA EntityManager merge infinite loop -
> ----------------------------------------
>
> Key: WFLY-11793
> URL: https://issues.jboss.org/browse/WFLY-11793
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 15.0.1.Final
> Environment: MAC OS Mojave
> Java 11
> Java EE 8
> Wildfly 15.0.1-Final
> Data Base Postgresql
> Reporter: Bruno Maioli Martins
> Assignee: Scott Marlow
> Priority: Major
> Attachments: teste.zip
>
>
> Dear,
> When executing the update of a record invoking getEntityManager().merge(obj) the application goes into infinite loop. This behavior only occurs when there is a OneToMany bidirectional mapping of the entity Papel -> PermissaoAtribuida.
> If the same code runs outside of the Wildfly server context its execution occurs normally.
> Attach the source code of my test classes.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11792) Error creating server pooled-connection-factory
by Claudio Miranda (Jira)
Claudio Miranda created WFLY-11792:
--------------------------------------
Summary: Error creating server pooled-connection-factory
Key: WFLY-11792
URL: https://issues.jboss.org/browse/WFLY-11792
Project: WildFly
Issue Type: Bug
Components: JMS
Reporter: Claudio Miranda
Assignee: ehsavoie Hugonnet
Try to add a pooled-connection-factory, it returns as failure caused by a NullPointerException.
To reproduce:
{code}
batch
/subsystem=messaging-activemq/server=srv-foo:add
/subsystem=messaging-activemq/server=srv-foo/path=bindings-directory:add(path=byhmzspzrcxq)
/subsystem=messaging-activemq/server=srv-foo/path=journal-directory:add(path=yghaapgbokdd)
/subsystem=messaging-activemq/server=srv-foo/path=large-messages-directory:add(path=qjaagiljbwjh)
/subsystem=messaging-activemq/server=srv-foo/path=paging-directory:add(path=sbxvhqytamqe)
run-batch
/subsystem=messaging-activemq/server=srv-foo/discovery-group=dg1:add
/subsystem=messaging-activemq/server=srv-foo/pooled-connection-factory=pool1:add(discovery-group=dg1,entries=[foobar])
{code}
{code}
19:21:20,772 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: org.jboss.msc.service.StartException in service jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1: WFLYMSGAMQ0028: Failed to create resource adapter
at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:328)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NullPointerException
at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.createService(PooledConnectionFactoryService.java:381)
at org.wildfly.extension.messaging.activemq.jms.PooledConnectionFactoryService.start(PooledConnectionFactoryService.java:325)
... 8 more
19:21:20,773 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "srv-update-wwavjsiodinh"),
("pooled-connection-factory" => "pool1")
]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.messaging-activemq.srv-update-wwavjsiodinh.jms.pooled-connection-factory.pool1" => "WFLYMSGAMQ0028: Failed to create resource adapter
Caused by: java.lang.NullPointerException"}}
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11720) Cannot invoke EJB over HTTP on JDK 11
by Cheng Fang (Jira)
[ https://issues.jboss.org/browse/WFLY-11720?page=com.atlassian.jira.plugin... ]
Cheng Fang commented on WFLY-11720:
-----------------------------------
Okay, I'll take a closer look. jboss-ejb-client also references the older version of jboss-marshalling, similar to wildfly-http-ejb-client.
> Cannot invoke EJB over HTTP on JDK 11
> -------------------------------------
>
> Key: WFLY-11720
> URL: https://issues.jboss.org/browse/WFLY-11720
> Project: WildFly
> Issue Type: Bug
> Components: EJB, Remoting
> Affects Versions: 16.0.0.Beta1
> Environment: JDK 11
> Reporter: Jan Kašík
> Assignee: Cheng Fang
> Priority: Critical
> Attachments: classes.zip, client-app.zip
>
>
> Run of client app calling EJB over HTTP fails on JDK 11 with following log:
> {noformat}
> Feb 14, 2019 12:49:30 PM org.wildfly.naming.client.Version <clinit>
> INFO: WildFly Naming version 1.0.6.Final
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.wildfly.security.manager.GetAccessibleDeclaredFieldAction (file:/home/hudson/hudson_workspace/mod_cluster/client/wildfly-elytron-1.1.3.Final.jar) to field java.security.AccessControlContext.context
> WARNING: Please consider reporting this to the maintainers of org.wildfly.security.manager.GetAccessibleDeclaredFieldAction
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Feb 14, 2019 12:49:30 PM org.wildfly.security.Version <clinit>
> INFO: ELY00001: WildFly Elytron version 1.1.3.Final
> Feb 14, 2019 12:49:30 PM org.jboss.ejb.client.EJBClient <clinit>
> INFO: JBoss EJB Client version 4.0.2.Final
> Feb 14, 2019 12:49:30 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.6.5.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.Version <clinit>
> INFO: JBoss Threads version 2.3.0.Beta2
> Feb 14, 2019 12:49:30 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 5.0.0.Final
> Feb 14, 2019 12:49:30 PM org.jboss.threads.LoggingUncaughtExceptionHandler uncaughtException
> ERROR: Thread Thread[XNIO-1 task-1,5,main] threw an uncaught exception
> java.lang.ExceptionInInitializerError
> at org.jboss.marshalling.river.RiverMarshaller.<clinit>(RiverMarshaller.java:1335)
> at org.jboss.marshalling.river.RiverMarshallerFactory.createMarshaller(RiverMarshallerFactory.java:54)
> at org.wildfly.httpclient.common.HttpTargetContext.createMarshaller(HttpTargetContext.java:132)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.marshalEJBRequest(HttpEJBReceiver.java:367)
> at org.wildfly.httpclient.ejb.HttpEJBReceiver.lambda$processInvocation$1(HttpEJBReceiver.java:185)
> at org.wildfly.httpclient.common.HttpTargetContext$1.lambda$completed$0(HttpTargetContext.java:338)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1871)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1400)
> at java.base/java.lang.Thread.run(Thread.java:834)
> Caused by: java.lang.IllegalStateException: No standard field found for reverse order comparator!
> at org.jboss.marshalling.river.Protocol.<clinit>(Protocol.java:287)
> ... 9 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (WFLY-11639) mod_cluster and HTTP2 enabled (the default) not working
by Radoslav Husar (Jira)
[ https://issues.jboss.org/browse/WFLY-11639?page=com.atlassian.jira.plugin... ]
Radoslav Husar resolved WFLY-11639.
-----------------------------------
Fix Version/s: 16.0.0.CR1
Resolution: Done
Should be fixed with undertow ugrade.
> mod_cluster and HTTP2 enabled (the default) not working
> -------------------------------------------------------
>
> Key: WFLY-11639
> URL: https://issues.jboss.org/browse/WFLY-11639
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 15.0.1.Final
> Environment: Mac OS X 10.14.3
> Tested on both
> AdoptOpenJDK 1.8.0_202-b08
> AdoptOpenJDK 11.0.1+13
> Reporter: Andreas Asplund
> Assignee: Radoslav Husar
> Priority: Major
> Fix For: 16.0.0.CR1
>
>
> mod cluster and HTTP2 enabled (the default) when using listener default in the modcluster subsystem. When turning off HTTP2 the clustering starts working again. Nothing is printed in the logs by default so DEBUG logging has to be turned on for undertow.
> Steps to reproduce:
> {code}
> unzip wildfly-dist-15.0.1.Final.zip
> # Terminal 1
> cd wildfly-15.0.1.Final/bin/
> ./standalone.sh -c standalone-load-balancer.xml -Djava.net.preferIPv4Stack=true -b 127.0.0.1 -Djboss.modcluster.multicast.address=230.0.0.4
> # Terminal 2
> cd wildfly-15.0.1.Final/bin/
> ./standalone.sh -c standalone-ha.xml -Djboss.node.name=node1 -Djboss.socket.binding.port-offset=100 -Djboss.modcluster.multicast.address=230.0.0.4
> # Terminal 3
> cd wildfly-15.0.1.Final/bin/
> ./standalone.sh -c standalone-ha.xml -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=200 -Djboss.modcluster.multicast.address=230.0.0.4
> # Terminal 4
> cd wildfly-15.0.1.Final/bin/
> ./jboss-cli.sh -c
> /subsystem=logging/logger=io.undertow:add(level=ALL)
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> connect localhost:10090
> /subsystem=logging/logger=io.undertow:add(level=ALL)
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=modcluster/proxy=default:write-attribute(name=listener,value=default)
> reload
> connect localhost:10190
> /subsystem=logging/logger=io.undertow:add(level=ALL)
> /subsystem=logging/console-handler=CONSOLE:write-attribute(name=level, value=ALL)
> /subsystem=modcluster/proxy=default:write-attribute(name=listener,value=default)
> reload
> {code}
> The following can be seen in the logs on the proxied servers:
> {code}
> 16:30:23,409 TRACE [io.undertow.request] (default I/O-7) Opened connection with /127.0.0.1:50002
> 16:30:23,410 DEBUG [io.undertow.request.error-response] (default I/O-7) Setting error code 500 for exchange HttpServerExchange{ OPTIONS * request {HTTP2-Settings=[AAEAABAAAAIAAAABAAQAAP//AAUAAEAA], Connection=[Upgrade, HTTP2-Settings], Upgrade=[h2c], User-Agent=[mod_cluster ping], Host=[127.0.0.1]} response {}}: java.lang.RuntimeException
> at io.undertow.server.HttpServerExchange.setStatusCode(HttpServerExchange.java:1410)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:393)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> 16:30:23,410 DEBUG [io.undertow.request.io] (default I/O-7) UT005013: An IOException occurred: java.io.IOException: Invalid base64 character encountered: 47
> at io.undertow.util.FlexBase64$Decoder.nextByte(FlexBase64.java:1048)
> at io.undertow.util.FlexBase64$Decoder.nextByte(FlexBase64.java:1015)
> at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1277)
> at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1347)
> at io.undertow.util.FlexBase64$Decoder.decode(FlexBase64.java:1413)
> at io.undertow.util.FlexBase64$Decoder.access$500(FlexBase64.java:983)
> at io.undertow.util.FlexBase64.decodeURL(FlexBase64.java:320)
> at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleHttp2Upgrade(Http2UpgradeHandler.java:158)
> at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleUpgradeBody(Http2UpgradeHandler.java:107)
> at io.undertow.server.protocol.http2.Http2UpgradeHandler.handleRequest(Http2UpgradeHandler.java:97)
> at io.undertow.server.handlers.DisallowedMethodsHandler.handleRequest(DisallowedMethodsHandler.java:61)
> at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)
> at io.undertow.server.protocol.http.HttpReadListener.handleEventWithNoRunningRequest(HttpReadListener.java:255)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:136)
> at io.undertow.server.protocol.http.HttpReadListener.handleEvent(HttpReadListener.java:59)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> 16:30:23,411 TRACE [io.undertow.server.HttpServerExchange] (default I/O-7) Starting to write response for HttpServerExchange{ OPTIONS * request {HTTP2-Settings=[AAEAABAAAAIAAAABAAQAAP//AAUAAEAA], Connection=[Upgrade, HTTP2-Settings], Upgrade=[h2c], User-Agent=[mod_cluster ping], Host=[127.0.0.1]} response {Connection=[keep-alive], Content-Length=[0], Date=[Wed, 23 Jan 2019 15:30:23 GMT]}}
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months