<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<font size="-1"><tt>While integrating EJB3 service into current AS
trunk, I noticed that if a Component's service (or any service in
general) has unresolved dependencies, although the service stays in
DOWN state (as expected), no error is reported and the deployment does
*not* fail. As a side effect of this, a runtime invocation on the
service (a InitialContext.lookup() leading to the
ServiceReferenceObjectFactory.getObjectInstance() in this case) ended
up hanging indefinitely <a class="moz-txt-link-freetext" href="http://pastebin.com/jK0i1aCi">http://pastebin.com/jK0i1aCi</a><br>
<br>
To debug this, I had to use jconsole and then get a list of all the
services, their dependencies and the state and then figure out what's
missing:<br>
<br>
Service
"jboss.deployment.unit.ejb3-example.jar.component.SimpleStatelessSessionBean"
(class org.jboss.as.ee.component.service.ComponentService) mode ACTIVE
state DOWN (dependencies:
jboss.naming.context.java.module.ejb3-example.jar,
jboss.naming.context.java.app.ejb3-example.jar,
jboss.naming.context.java.comp.ejb3-example.jar.SimpleStatelessSessionBean,
jboss.naming.context.java.global."ejb3-example/SimpleStatelessSessionBean!org.jboss.as.demos.ejb3.archive.SimpleStatelessSessionLocal")
(has missing dependency)<br>
<br>
Shouldn't a unresolved dependency on a service result in deployment
failure?<br>
<br>
-Jaikiran<br>
<br>
<br>
</tt></font>
</body>
</html>