Bug 1393795 - [6.4.z] @EJB injection with Remote Interface fails on @Startup@Singleton
Summary: [6.4.z] @EJB injection with Remote Interface fails on @Startup@Singleton
Keywords:
Status: CLOSED DUPLICATE of bug 1389428
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: CDI/Weld, EJB
Version: 6.4.11
Hardware: All
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: jboss-set
QA Contact: Matej Novotny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-10 10:53 UTC by Carsten Lichy-Bittendorf
Modified: 2020-04-15 14:50 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-10 15:24:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
reproducer using arquillian (18.32 KB, application/zip)
2016-11-10 10:53 UTC, Carsten Lichy-Bittendorf
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-7026 0 Major Pull Request Sent [GSS](7.0.z) @Startup @Singleton fails to invoke EJB via Remote interface in PostConstruct 2016-12-20 20:10:28 UTC
Red Hat Knowledge Base (Solution) 2760261 0 None None None 2016-11-10 11:06:10 UTC

Description Carsten Lichy-Bittendorf 2016-11-10 10:53:02 UTC
Created attachment 1219309 [details]
reproducer using arquillian

Description of problem:

@Startup
@Singleton
public class TrivialSingleton {
	
	@EJB
	MostSimpleEjbRemote calculator;

fails in EAP 6.4.11 while it worked until EAP 6.4.10

Version-Release number of selected component (if applicable):


How reproducible:

See attached reproducer

Actual results:

Caused by: javax.ejb.EJBException: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available ...

Expected results:

Should work as it worked before

Additional info:

Comment 2 Brad Maxwell 2016-11-10 15:24:53 UTC

*** This bug has been marked as a duplicate of bug 1389428 ***


Note You need to log in before you can comment on or make changes to this bug.