-
15. Re: Wildfly 10: @TransactionAttribute exception on startup
philmagno Apr 4, 2016 7:29 PM (in response to smarlow)I can't see the jira report.
"Permission Violation"
It seems that you have tried to perform an operation which you are not permitted to perform.
If you think this message is wrong, please contact your JIRA administrators.
Do you know what's happening ?
-
16. Re: Wildfly 10: @TransactionAttribute exception on startup
jonesbusy Apr 6, 2016 4:34 AM (in response to philmagno)I can't see the Jira issue either.
My workaround is to not use @TransactionAttribute anymore on generics method
-
17. Re: Wildfly 10: @TransactionAttribute exception on startup
smarlow Apr 6, 2016 9:21 AM (in response to jonesbusy)I think that the jira was probably mistakenly hidden but I am not really sure (it is still hidden). Sorry about that.
-
18. Re: Wildfly 10: @TransactionAttribute exception on startup
marks1900 Apr 27, 2016 4:28 PM (in response to philmagno)While you cannot access https://issues.jboss.org/browse/WFLY-6430, there was a linked task that might provide more insight: [JANDEX-35] Failure to resolve method type variable when using class-level bounded wildcard generics - JBoss Issue Track…
Which in turn links to what I think is the issue: [WFLY-6113] TransactionAttributeMergingProcessor fails when using generics - JBoss Issue Tracker
Description:
Deployment fails when using type safe generics on session beans with transaction attributes. See reproducer. Works with 9.0.2.Final.
Example Stack Trace:
https://issues.jboss.org/secure/attachment/12397417/log.txt 2016-02-02 10:28:31,558 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."AbstractTransactionAttributeMergeError.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."AbstractTransactionAttributeMergeError.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "AbstractTransactionAttributeMergeError.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final.jar:1.2.6.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_72]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_72]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_72]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEJB0264: Could not merge data for SomethingStateful
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]
... 5 more
Caused by: java.lang.RuntimeException: WFLYEE0034: Could not resolve method Method transactionalMethod(java.lang.Object) on class class Stateful.AbstractStateful with annotations [REQUIRES_NEW]
at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:79)
at org.jboss.as.ejb3.deployment.processors.merging.TransactionAttributeMergingProcessor.processTransactionAttributeAnnotation(TransactionAttributeMergingProcessor.java:90)
at org.jboss.as.ejb3.deployment.processors.merging.TransactionAttributeMergingProcessor.handleAnnotations(TransactionAttributeMergingProcessor.java:73)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.processComponentConfig(AbstractMergingProcessor.java:92)
at org.jboss.as.ejb3.deployment.processors.merging.AbstractMergingProcessor.deploy(AbstractMergingProcessor.java:74)
... 6 more