[
https://issues.jboss.org/browse/WFLY-7101?page=com.atlassian.jira.plugin....
]
Stuart Douglas commented on WFLY-7101:
--------------------------------------
This is not a bug, but actually required by the EJB spec, in 4.8.1 it says "the
container must initialize the singleton session bean instance during the application
startup sequence. The container must initialize all such startup-time singleton session
beans before any external client requests (that is, client requests originating outside of
the application) are delivered to any enterprise bean components in the application"
Wildfly 10.1.0 blocks calls to Singleton EJBs in PostConstruct
--------------------------------------------------------------
Key: WFLY-7101
URL:
https://issues.jboss.org/browse/WFLY-7101
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.1.0.Final
Environment: Wildfly 10.1.0 running under Windows 10 with Java 1.8.0_91
Reporter: Dietrich Schmidt
Assignee: Jason Greene
Attachments: Verklemmung.zip
Wildfly 8.2.0 and 10.0.0 work fine with a Singleton Bean, which has a @Postconstruct
method and in this method several threads are created with the ManagedExecutorService.
These threads call a method in another Singleton EJB, which has been injected.
This call is blocked in Wildfly 10.1.0 until the Prostconstruct thread has ended.
I assume that the behaviour of Wildfly 8.2.0 + 10.0.0 is correct and the behaviour of
Wildfly 10.1.0 is a bug.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)