[JBoss JIRA] (DROOLS-5367) Fixing model name/package name management during kiepmmlmodel generation/instantiation
by Gabriele Cardosi (Jira)
[ https://issues.redhat.com/browse/DROOLS-5367?page=com.atlassian.jira.plug... ]
Gabriele Cardosi updated DROOLS-5367:
-------------------------------------
Description:
Current code is written with the assumption that model name is provided by all model definitions.
Beside that, verify if for every model there must be a specific package, or if it is fine to have one package for all the models defined in the same file.
Code-generate kmodule.xml
was:
Current code is written with the assumption that model name is provided by all model definitions.
That is not enforced by the specification itself, so we need to provide a way to generate a predictable model name.
Beside that, verify if for every model there must be a specific package, or if it is fine to have one package for all the models defined in the same file.
Code-generate kmodule.xml
> Fixing model name/package name management during kiepmmlmodel generation/instantiation
> --------------------------------------------------------------------------------------
>
> Key: DROOLS-5367
> URL: https://issues.redhat.com/browse/DROOLS-5367
> Project: Drools
> Issue Type: Task
> Reporter: Gabriele Cardosi
> Assignee: Gabriele Cardosi
> Priority: Major
> Labels: TrustyAI
>
> Current code is written with the assumption that model name is provided by all model definitions.
> Beside that, verify if for every model there must be a specific package, or if it is fine to have one package for all the models defined in the same file.
> Code-generate kmodule.xml
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13438) Database Timers: instances sporadically fail to start in a cluster
by Marcos Scholtz (Jira)
[ https://issues.redhat.com/browse/WFLY-13438?page=com.atlassian.jira.plugi... ]
Marcos Scholtz commented on WFLY-13438:
---------------------------------------
[~cfang]: thanks for your feedback!
Yes, READ_COMMITTED is the default transaction isolation level in Postgres. I also tried to set it explicitly (to READ-COMMITTED and to SERIALIZABLE). This didn't solve the problem.
I upgraded my test to Wildfly 20, and unfortunately I can still reproduce the error. It took me three restarts of a server-group with three instances. Sometimes it takes longer. This is in a VirtualBox-Vagrant with Wildfly 20 in domain mode and postgres 9.4.26. On our production environment with a domain-controller and many remote instances (each in it's own machine), the problem happens much more frequently. Perhaps because there the communication between Domain-Controller and Instance takes longer...
If I can help you somehow to narrow the error down, or if I can send you more configuration or anything else, just tell me what you need and I'd be happy to help.
> Database Timers: instances sporadically fail to start in a cluster
> ------------------------------------------------------------------
>
> Key: WFLY-13438
> URL: https://issues.redhat.com/browse/WFLY-13438
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 19.1.0.Final
> Reporter: Marcos Scholtz
> Assignee: Cheng Fang
> Priority: Major
>
> We use a postgresql database for persistent timers, to control the execution of scheduled tasks in a cluster. It mainly works, but when operating in a cluster and when a server-group is restarted, sometimes individual instances in the cluster fail to start because of an error when reinstating persistent timers.
> Configuration of the Datasource:
> {code}
> <xa-datasource jndi-name="java:/datasources/MonitoringDS" pool-name="MonitoringDS" enabled="true">
> <xa-datasource-property name="ServerName">
> appserver.local
> </xa-datasource-property>
> <xa-datasource-property name="PortNumber">
> 5432
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> monitoringdb
> </xa-datasource-property>
> <xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
> <driver>postgresql</driver>
> <security>
> <user-name>xxx</user-name>
> <password>xxx</password>
> </security>
> </xa-datasource>
> {code}
> Configuration of the timer service:
> {code}
> <timer-service thread-pool-name="default" default-data-store="batch-clustered-store">
> <data-stores>
> <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/>
> <database-data-store name="batch-clustered-store" datasource-jndi-name="java:/datasources/MonitoringDS" database="'postgresql'" partition="${batch.partition}" refresh-interval="60000" allow-execution="true"/>
> </data-stores>
> </timer-service>
> {code}
> Note we use a system-property on the server-group to determine the partition name.
> Also, we made NO changes to the SQL statements in "timer-sql.properties".
> The timer is generated by a `@Schedule` annotation in an EJB like this:
> {code}
> @Schedule(
> dayOfMonth = "${manual.scheduler.dayofmonth:*}",
> dayOfWeek = "${manual.scheduler.dayofweek:*}",
> hour = "${manual.scheduler.hour:2/6}",
> minute = "${manual.scheduler.minute:2}"
> )
> @TransactionAttribute(TransactionAttributeType.NEVER)
> void doPostboxImport() {
> log.info("Starting Postbox Import");
> BatchRuntime.getJobOperator().start("PostboxImportBatchlet", null);
> }
> {code}
> The error we sporadically get when starting more than one instance at the same time (when all instances try to reinstate timers) is like this:
> {code}
> 14:48:28,117 WARN [com.arjuna.ats.arjuna] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} ARJUNA012078: Abort called illegaly on atomic action 0:ffff7f000001:-27f2652e:5eb2b20f:f
> 14:48:28,118 WARN [org.jboss.as.ejb3.timer] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} WFLYEJB0161: Failed to reinstate timer 'postbox-integration-service.postbox-integration-service.PostboxImport' (id=unavailable) from its persistent state: javax.transaction.NotSupportedException: WFTXN0001: A transaction is already in progress
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:60)
> at org.wildfly.transaction.client@1.1.9.Final//org.wildfly.transaction.client.ContextTransactionManager.begin(ContextTransactionManager.java:54)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.getActivePersistentTimers(TimerServiceImpl.java:984)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:712)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> 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)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> 14:48:28,153 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 69) {"tenant": "", "clientId": ""} MSC000001: Failed to start service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: org.jboss.msc.service.StartException in service jboss.deployment.unit."postbox-integration-service-E-SNAPSHOT.war".component.PostboxImport.START: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:57)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> 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)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:626)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.createCalendarTimer(TimerServiceImpl.java:537)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.loadAutoTimer(TimerServiceImpl.java:388)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.restoreTimers(TimerServiceImpl.java:774)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.activate(TimerServiceImpl.java:223)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.EJBComponent.init(EJBComponent.java:595)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent.init(StatelessSessionComponent.java:110)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.BasicComponent.start(BasicComponent.java:222)
> at org.jboss.as.ee@19.1.0.Final//org.jboss.as.ee.component.ComponentStartService$1.run(ComponentStartService.java:54)
> ... 8 more
> Caused by: java.lang.NullPointerException
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.addTimer(DatabaseTimerPersistence.java:336)
> at org.jboss.as.ejb3@19.1.0.Final//org.jboss.as.ejb3.timerservice.TimerServiceImpl.persistTimer(TimerServiceImpl.java:607)
> ... 16 more
> {code}
> The error seems similar to the one described in WFLY-13386, but the stack trace and the steps to reproduce it seem different to me, so I'm not sure if it's the same problem. The problem also existed in Wildfly 14 , we just updated to 19.1 (also hoping that his error would be corrected).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13641) WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
by Matěj Novotný (Jira)
[ https://issues.redhat.com/browse/WFLY-13641?page=com.atlassian.jira.plugi... ]
Matěj Novotný commented on WFLY-13641:
--------------------------------------
Would you be willing to cobble together a minimal reproducer project for this?
Meanwhile, looking at WFLY docs, I only found little about [{{jboss-deploymet-structure}}|https://docs.wildfly.org/16/Developer_Guide.html#jboss-deployment-structure-file]. And from that text it's not obvious how it should behave. But in theory, the issue is either not being able to found existing jandex for given URL (because I thought all deployments on WFLY will be indexed?) or not being able to index it on the fly. [~brian.stansberry] do you happen to know or point me to whoever is the jandex guru within WFLY? :-)
The reason why discovery mode {{all}} gives you access to all beans and no error is because we can fully avoid trying to access the index (we needn't check if every class meets the criteria of having bean defining annotation which is what we use jandex for in this case).
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13641
> URL: https://issues.redhat.com/browse/WFLY-13641
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld
> Affects Versions: 20.0.0.Final
> Reporter: Jens Viebig
> Assignee: Matěj Novotný
> Priority: Major
>
> When referencing a jar with CDI scan mode "annotaded" inside an ear from an external war via jboss-deployment-structure.xml a warning will be printed for every class:
> WFLYWELD0055: Could not index class [Someclass] from an external bean archive: vfs:/somepath/myear.ear/myejb-0.0.1.jar/META-INF/beans.xml
> Seems VFS cannot get hold of the classes.
> The warning is logged in ExternalBeanArchiveProcessor which catches an EOFException from the inputstream loading the class. (Line 284). Seems the input stream is not able to load a single byte from the class
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13648) Add a new legacy-security artefact / module
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13648?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFLY-13648:
------------------------------------
Description:
Where components in WildFly Core depend on PicketBox we should make sure this is via a module which they can optional depend upon so avoid components in WildFly Core having hard dependencies on PicketBox APIs.
Initially this will hold the PicketBox JACC PolicyContextHandler integrations exposed for ServiceLoader discovery so they can be removed from WildFly.
was:Where components in WildFly Core depend on PicketBox we should make sure this is via a module which they can optional depend upon so avoid components in WildFly Core having hard dependencies on PicketBox APIs.
> Add a new legacy-security artefact / module
> -------------------------------------------
>
> Key: WFLY-13648
> URL: https://issues.redhat.com/browse/WFLY-13648
> Project: WildFly
> Issue Type: Task
> Components: Build System, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Where components in WildFly Core depend on PicketBox we should make sure this is via a module which they can optional depend upon so avoid components in WildFly Core having hard dependencies on PicketBox APIs.
>
> Initially this will hold the PicketBox JACC PolicyContextHandler integrations exposed for ServiceLoader discovery so they can be removed from WildFly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13648) Add a new legacy-security artefact / module
by Darran Lofthouse (Jira)
[ https://issues.redhat.com/browse/WFLY-13648?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved WFCORE-5035 to WFLY-13648:
-------------------------------------------------
Project: WildFly (was: WildFly Core)
Key: WFLY-13648 (was: WFCORE-5035)
Component/s: Build System
Security
(was: Build System)
(was: Security)
Fix Version/s: 21.0.0.Beta1
(was: 13.0.0.Beta2)
> Add a new legacy-security artefact / module
> -------------------------------------------
>
> Key: WFLY-13648
> URL: https://issues.redhat.com/browse/WFLY-13648
> Project: WildFly
> Issue Type: Task
> Components: Build System, Security
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> Where components in WildFly Core depend on PicketBox we should make sure this is via a module which they can optional depend upon so avoid components in WildFly Core having hard dependencies on PicketBox APIs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13647) Annotation processing error sun.reflect.annotation.TypeNotPresentExceptionProxy does not indicate issue
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-13647?page=com.atlassian.jira.plugi... ]
Lin Gao updated WFLY-13647:
---------------------------
Labels: downstream_dependency (was: )
> Annotation processing error sun.reflect.annotation.TypeNotPresentExceptionProxy does not indicate issue
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13647
> URL: https://issues.redhat.com/browse/WFLY-13647
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Major
> Labels: downstream_dependency
>
> In this case, of an EJB class, we are able to see that it is something in the EJB class, though it would be useful to indicate the annotation or class that is missing:
>
> {code:java}
> 14:50:45,052 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."test.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "test.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> 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: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0466: Failed to process business interfaces for EJB class class test.TestSingleton
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:93)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
> at java.lang.Class.createAnnotationData(Class.java:3521)
> at java.lang.Class.annotationData(Class.java:3510)
> at java.lang.Class.getAnnotation(Class.java:3415)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:156)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:124)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:91)
> ... 9 more {code}
>
> There are other errors where it does not indicate anything:
> {code:java}
> 2020-05-30 19:34:48,267 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit.”test2.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.”test2.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment “test2.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> 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:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
> at java.lang.Class.createAnnotationData(Class.java:3521)
> at java.lang.Class.annotationData(Class.java:3510)
> at java.lang.Class.getAnnotation(Class.java:3415)
> at java.lang.reflect.AnnotatedElement.isAnnotationPresent(AnnotatedElement.java:258)
> at java.lang.Class.isAnnotationPresent(Class.java:3425)
> at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:150)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more {code}
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13647) Annotation processing error sun.reflect.annotation.TypeNotPresentExceptionProxy does not indicate issue
by Lin Gao (Jira)
[ https://issues.redhat.com/browse/WFLY-13647?page=com.atlassian.jira.plugi... ]
Lin Gao moved JBEAP-19830 to WFLY-13647:
----------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-13647 (was: JBEAP-19830)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Server
(was: Server)
Affects Version/s: (was: 7.3.1.GA)
(was: 7.2.8.GA)
Fix Version/s: (was: 7.3.3.GA)
> Annotation processing error sun.reflect.annotation.TypeNotPresentExceptionProxy does not indicate issue
> -------------------------------------------------------------------------------------------------------
>
> Key: WFLY-13647
> URL: https://issues.redhat.com/browse/WFLY-13647
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Major
>
> In this case, of an EJB class, we are able to see that it is something in the EJB class, though it would be useful to indicate the annotation or class that is missing:
>
> {code:java}
> 14:50:45,052 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."test.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."test.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "test.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:183)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> 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: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0466: Failed to process business interfaces for EJB class class test.TestSingleton
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:93)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176)
> ... 8 more
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
> at java.lang.Class.createAnnotationData(Class.java:3521)
> at java.lang.Class.annotationData(Class.java:3510)
> at java.lang.Class.getAnnotation(Class.java:3415)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.getRemoteBusinessInterfaces(BusinessViewAnnotationProcessor.java:156)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.processViewAnnotations(BusinessViewAnnotationProcessor.java:124)
> at org.jboss.as.ejb3.deployment.processors.BusinessViewAnnotationProcessor.deploy(BusinessViewAnnotationProcessor.java:91)
> ... 9 more {code}
>
> There are other errors where it does not indicate anything:
> {code:java}
> 2020-05-30 19:34:48,267 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit.”test2.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.”test2.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment “test2.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:151)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> 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:1363)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
> at sun.reflect.annotation.AnnotationParser.parseClassArray(AnnotationParser.java:724)
> at sun.reflect.annotation.AnnotationParser.parseArray(AnnotationParser.java:531)
> at sun.reflect.annotation.AnnotationParser.parseMemberValue(AnnotationParser.java:355)
> at sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:286)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:120)
> at sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:72)
> at java.lang.Class.createAnnotationData(Class.java:3521)
> at java.lang.Class.annotationData(Class.java:3510)
> at java.lang.Class.getAnnotation(Class.java:3415)
> at java.lang.reflect.AnnotatedElement.isAnnotationPresent(AnnotatedElement.java:258)
> at java.lang.Class.isAnnotationPresent(Class.java:3425)
> at org.wildfly.extension.undertow.deployment.ServletContainerInitializerDeploymentProcessor.deploy(ServletContainerInitializerDeploymentProcessor.java:150)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:144)
> ... 8 more {code}
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years