uCosminexus Application Server, Messages
![[Contents]](FIGURE/CONTENT.GIF)
![[Back]](FIGURE/FRONT.GIF)
KDJE43218-E
Illegal synchronous loopback call during Singleton initialization would have resulted in deadlock. (EJB name = aa....aa)
- aa....aa: EJB name
- Description
- Initialization of the Singleton Session Bean failed because during the initialization, there was an invalid loopback invocation that might cause a deadlock.
- During the initialization of a Singleton Session Bean, initialization was re-executed for the same Singleton Session Bean.
- Action
- Check whether the initialization processing is being executed for the same Singleton Session Bean from the @PostConstruct annotation method.
- If a different Singleton Session Bean is being invoked from the @PostConstruct annotation method, the dependency based on the @DependsOn annotation becomes invalid and this message is displayed. The invalid example is as follows:
- Example
@DependsOn("SingletonA")
@Singleton
@Startup
public class SingletonB implements BIntf {
}
@Singleton
public class SingletonA implements AIntf {
@EJB
BIntf b;
@PostConstruct
void init() {
b.doB();
}
}
All Rights Reserved. Copyright (C) 2012, 2013, Hitachi, Ltd.