[jboss-jira] [JBoss JIRA] (WFLY-9443) Random deploy error with @Startup @Singleton EJB

Juan Martin Runge (JIRA) issues at jboss.org
Tue Oct 17 08:53:02 EDT 2017


    [ https://issues.jboss.org/browse/WFLY-9443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478072#comment-13478072 ] 

Juan Martin Runge edited comment on WFLY-9443 at 10/17/17 8:52 AM:
-------------------------------------------------------------------

Hi Martin, you were completely right. Changing {code:java}<type>jar</type>{code} to {code:java}<scope>provided</scope>{code} on {code:java}wftest-vaadin{code} pom.xml for the ejb jar dependency did the trick. My pom was autogenerated by netbeans, I never thougth it could be wrong.  10 deployments in a row and no a single fail.

Many thanks! I think we may close this issue now...

Kind Regards, 

Juan Martin


was (Author: jmrunge):
Hi Martin, you were completely right. Changing {code:java}<type>jar</type>{code} to {code:java}<scope>provided</scope>{code} on {code:java}wftest-vaadin{code} pom.xml for the ejb jar dependency did the trick. My pom was autogenerated by netbeans, I never thougth it could be wrong.  10 deployments in a row and no a single fail.

Many thanks! I think we may close this issue now...

Kina Regards, 

Juan Martin

> Random deploy error with @Startup @Singleton EJB
> ------------------------------------------------
>
>                 Key: WFLY-9443
>                 URL: https://issues.jboss.org/browse/WFLY-9443
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, Class Loading, EJB
>    Affects Versions: 11.0.0.CR1
>         Environment: Wildfly 11.0CR1 + Vaadin 8.1.4 
> Tested on Debian 9.1 and Windows 10
>            Reporter: Juan Martin Runge
>            Assignee: Martin Kouba
>              Labels: regression
>         Attachments: error.log, success.log, wftest-ear-0.1.0.ear.tar.gz, wftest.tar.gz
>
>
> Simple EAR project with an EJB Module and a WAR Module.  War uses Vaadin (think is not relevant but mention it anyway). On the EJB Module I have a @Singleton @Startup bean which has injected a at LocalBean @Stateless bean via @Inject annotation (tested with @EJB annotation with same results).  The UI on the WAR side also calls this @LocalBean @Stateless bean.  Randomly, when I deploy, redeploy or restart the server, the EAR refuses to deploy do java.lang.IllegalStateException because it cannot inject the @Stateless bean inside the @Startup bean. 
> Attached sample app, project, log with error and log with success.
> If you check the success log, you will see the @Startup @Singleton bean gets instanciated twice.. Quite strange.
> Also, this didnt happened with Wildfly 9 (same app deployed perfectly)



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list