[jboss-jira] [JBoss JIRA] (WFLY-5102) Intermittent error Unresolved compilation problems when deploying MDB
Ondřej Chaloupka (JIRA)
issues at jboss.org
Fri Aug 14 09:23:02 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ondřej Chaloupka updated WFLY-5102:
-----------------------------------
Description:
It happened to me that deploy of MDB ends with {{java.lang.Error: Unresolved compilation problems}} [1].
My scenario is to start server, does some changes with cli, deploy application, then restart server to get all configuration changes being refreshed and start some testing.
After the server restart (it means the deployment was on its place before server start up) I've experienced this exception. As intermittent failure I have no much idea how to get it reproduced.
The exception talks about {{MessageHelper}} and {{CrashBeanCommon}} which are helper classes that are used in MDB. My first suggestion was that they could not be bundled in the jar but as deployment was successfully processed it does not seem to me being the case.
[1]
{code}
INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "crashrecovery-jms-mdb.jar" (runtime-name : "crashrecovery-jms-mdb.jar")
WARN [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ152005: Failure in broker activation org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): java.lang.Error: Unresolved compilation problems:
The import org.jboss.as.test.jbossts.common cannot be resolved
The import org.jboss.as.test.jbossts.crashrec.common cannot be resolved
The import org.jboss.as.test.jbossts.crashrec.jms.MessageHelper cannot be resolved
CrashBeanCommon cannot be resolved to a type
MessageHelper cannot be resolved to a type
MessageHelper cannot be resolved to a type
The method beforeEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
JMSQueueProperties cannot be resolved to a variable
The method afterEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean.<init>(JMSCrashMessageDrivenBean.java:33)
at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean$$$view4.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at java.lang.Class.newInstance(Class.java:442)
at org.jboss.invocation.proxy.AbstractClassFactory.newInstance(AbstractClassFactory.java:225)
at org.jboss.invocation.proxy.ProxyFactory.newInstance(ProxyFactory.java:272)
at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:281)
at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:197)
at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:178)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.access$400(MessageDrivenComponent.java:61)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$3.obtain(MessageDrivenComponent.java:166)
at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:68)
at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:63)
at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.setup(ActiveMQMessageHandler.java:204)
at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:340)
at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:819)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:226)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
{code}
was:
It happened to me that deploy of MDB ends with {{java.lang.Error: Unresolved compilation problems}} [1].
My scenario is to start server, does some changes with cli, deploy application, then restart server to get all configuration changes being refreshed and start some testing.
After the server restart (it means the deployment was on its place before server start up) I've experienced this exception. As intermittent failure I have no much idea how to get it reproduced.
[1]
{code}
INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "crashrecovery-jms-mdb.jar" (runtime-name : "crashrecovery-jms-mdb.jar")
WARN [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ152005: Failure in broker activation org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): java.lang.Error: Unresolved compilation problems:
The import org.jboss.as.test.jbossts.common cannot be resolved
The import org.jboss.as.test.jbossts.crashrec.common cannot be resolved
The import org.jboss.as.test.jbossts.crashrec.jms.MessageHelper cannot be resolved
CrashBeanCommon cannot be resolved to a type
MessageHelper cannot be resolved to a type
MessageHelper cannot be resolved to a type
The method beforeEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
JMSQueueProperties cannot be resolved to a variable
The method afterEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean.<init>(JMSCrashMessageDrivenBean.java:33)
at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean$$$view4.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at java.lang.Class.newInstance(Class.java:442)
at org.jboss.invocation.proxy.AbstractClassFactory.newInstance(AbstractClassFactory.java:225)
at org.jboss.invocation.proxy.ProxyFactory.newInstance(ProxyFactory.java:272)
at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:281)
at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:197)
at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:178)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.access$400(MessageDrivenComponent.java:61)
at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$3.obtain(MessageDrivenComponent.java:166)
at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:68)
at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:63)
at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.setup(ActiveMQMessageHandler.java:204)
at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:340)
at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:819)
at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:226)
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
{code}
> Intermittent error Unresolved compilation problems when deploying MDB
> ---------------------------------------------------------------------
>
> Key: WFLY-5102
> URL: https://issues.jboss.org/browse/WFLY-5102
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Beta1
> Environment: fedora 22, x86_64
> Reporter: Ondřej Chaloupka
> Assignee: Jeff Mesnil
>
> It happened to me that deploy of MDB ends with {{java.lang.Error: Unresolved compilation problems}} [1].
> My scenario is to start server, does some changes with cli, deploy application, then restart server to get all configuration changes being refreshed and start some testing.
> After the server restart (it means the deployment was on its place before server start up) I've experienced this exception. As intermittent failure I have no much idea how to get it reproduced.
> The exception talks about {{MessageHelper}} and {{CrashBeanCommon}} which are helper classes that are used in MDB. My first suggestion was that they could not be bundled in the jar but as deployment was successfully processed it does not seem to me being the case.
> [1]
> {code}
> INFO [org.jboss.as.server] (management-handler-thread - 4) WFLYSRV0010: Deployed "crashrecovery-jms-mdb.jar" (runtime-name : "crashrecovery-jms-mdb.jar")
> WARN [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ152005: Failure in broker activation org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): java.lang.Error: Unresolved compilation problems:
> The import org.jboss.as.test.jbossts.common cannot be resolved
> The import org.jboss.as.test.jbossts.crashrec.common cannot be resolved
> The import org.jboss.as.test.jbossts.crashrec.jms.MessageHelper cannot be resolved
> CrashBeanCommon cannot be resolved to a type
> MessageHelper cannot be resolved to a type
> MessageHelper cannot be resolved to a type
> The method beforeEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
> JMSQueueProperties cannot be resolved to a variable
> The method afterEntityUpdate() is undefined for the type JMSCrashMessageDrivenBean
>
> at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean.<init>(JMSCrashMessageDrivenBean.java:33)
> at org.jboss.as.test.jbossts.crashrec.jms.mdb.JMSCrashMessageDrivenBean$$$view4.<init>(Unknown Source)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at java.lang.Class.newInstance(Class.java:442)
> at org.jboss.invocation.proxy.AbstractClassFactory.newInstance(AbstractClassFactory.java:225)
> at org.jboss.invocation.proxy.ProxyFactory.newInstance(ProxyFactory.java:272)
> at org.jboss.as.ee.component.ViewService$DefaultViewInstanceFactory.createViewInstance(ViewService.java:281)
> at org.jboss.as.ee.component.ViewService$View.createInstance(ViewService.java:184)
> at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:197)
> at org.jboss.as.ejb3.component.EJBComponent.createViewInstanceProxy(EJBComponent.java:178)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent.access$400(MessageDrivenComponent.java:61)
> at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponent$3.obtain(MessageDrivenComponent.java:166)
> at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:68)
> at org.jboss.as.ejb3.inflow.JBossMessageEndpointFactory.createEndpoint(JBossMessageEndpointFactory.java:63)
> at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.setup(ActiveMQMessageHandler.java:204)
> at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation.setup(ActiveMQActivation.java:340)
> at org.apache.activemq.artemis.ra.inflow.ActiveMQActivation$SetupActivation.run(ActiveMQActivation.java:819)
> at org.jboss.jca.core.workmanager.WorkWrapper.run(WorkWrapper.java:226)
> at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33)
> at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:808)
> at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45)
> at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:828)
> at java.lang.Thread.run(Thread.java:745)
> at org.jboss.threads.JBossThread.run(JBossThread.java:320)
>
> INFO [org.apache.activemq.artemis.ra] (default-threads - 1) AMQ151001: Attempting to reconnect org.apache.activemq.artemis.ra.inflow.ActiveMQActivationSpec(ra=org.apache.activemq.artemis.ra.ActiveMQResourceAdapter at 608ca9bd destination=MDBTriggerQueue destinationType=javax.jms.Queue ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list