[jboss-jira] [JBoss JIRA] Created: (JBAS-8032) EJB dependency on another EJB from the same EJB-JAR

Alexey Loubyansky (JIRA) jira-events at lists.jboss.org
Mon May 17 15:15:06 EDT 2010


EJB dependency on another EJB from the same EJB-JAR
---------------------------------------------------

                 Key: JBAS-8032
                 URL: https://jira.jboss.org/browse/JBAS-8032
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: EJB2
    Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA
            Reporter: Alexey Loubyansky
            Assignee: Alexey Loubyansky
             Fix For: 6.0.0.M4


The following is failing to deploy

<jboss>
   <enterprise-beans>
      <session>
         <ejb-name>MySession</ejb-name>
         <depends>jboss.j2ee:jndiName=MySession2,service=EJB</depends>
      </session>
      <session>
         <ejb-name>MySession2</ejb-name>
         <depends>jboss.j2ee:jndiName=MySession3,service=EJB</depends>
      </session>
   </enterprise-beans>
</jboss>

with the exception

21:09:14,425 WARN  [org.jboss.deployment.MainDeployer] Failed to deploy: file:/XXXX/jbossas/trunk/testsuite/output/lib/ejbdepe
nds.ear: org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "jboss.j2ee:ear="ejbdepends.ear",module="ejbdepends1.jar",service=EjbModule" is missing the following dependencies:
    Dependency "jboss.j2ee:jndiName=MySession2,service=EJB" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.j2e
e:jndiName=MySession2,service=EJB' **")

DEPLOYMENTS IN ERROR:
  Deployment "jboss.j2ee:jndiName=MySession2,service=EJB" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.j2ee:jndiName=MyS
ession2,service=EJB' **

        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1395) [:2.2.0.Alpha4]
        at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1341) [:2.2.0.Alpha4]
        at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:968) [:2.2.0.Alpha4]
        at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:957) [:2.2.0.Alpha4]
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:373) [:6.0.0-SNAPSHOT]
        at org.jboss.deployment.MainDeployer.redeploy(MainDeployer.java:277) [:6.0.0-SNAPSHOT]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_13]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_13]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_13]
        at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_13]
        at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) [:6.0.0.Beta5]
        at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) [:6.0.0.Beta5]
        at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) [:6.0.0.Beta5]
        at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:271) [:6.0.0.Beta5]
        at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:670) [:6.0.0.Beta5]
        at org.jboss.system.server.jmx.MBeanServerWrapper.invoke(MBeanServerWrapper.java:138) [:6.0.0-SNAPSHOT (Build SVNTag:JBoss_6.0.0-SNAPSHOT date
: 20100517)]
        at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1426) [:1.6.0_13]
        at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72) [:1.6.0_13]
        at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1264) [:1.6.0_13]
        at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1359) [:1.6.0_13]
        at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788) [:1.6.0_13]
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_13]
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_13]
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_13]
        at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_13]
        at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) [:1.6.0_13]
        at sun.rmi.transport.Transport$1.run(Transport.java:159) [:1.6.0_13]
        at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_13]
        at sun.rmi.transport.Transport.serviceCall(Transport.java:155) [:1.6.0_13]
        at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) [:1.6.0_13]
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) [:1.6.0_13]
        at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) [:1.6.0_13]
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_13]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_13]
        at java.lang.Thread.run(Thread.java:619) [:1.6.0_13]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-jira mailing list