6 Replies Latest reply on Apr 27, 2009 5:23 AM by Ross Nicholson

    Deployment error using Service beans

    Ross Nicholson Apprentice

      If I remove a service bean jar from an ears application.xml and redeploy, I get deployment errors for the missing jar file as if it should still exist.

      Here's the first ear I deploy:

      <?xml version="1.0" encoding="UTF-8"?>
      <application xmlns="http://java.sun.com/xml/ns/javaee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5"
      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
      http://java.sun.com/xml/ns/javaee/application_5.xsd">
       <display-name>SPE Test</display-name>
      
       <module>
       <web>
       <web-uri>spe-test.war</web-uri>
       <context-root>/spe-test</context-root>
       </web>
       </module>
      
       <module>
       <ejb>spe-test.jar</ejb>
       </module>
      
       <module>
       <ejb>spe-input.jar</ejb>
       </module>
      
       <library-directory>lib</library-directory>
      
      </application>
      


      Then if I remove "spe-input.jar" from the ear file and change this file to reflect this change and redeploy:

      <?xml version="1.0" encoding="UTF-8"?>
      <application xmlns="http://java.sun.com/xml/ns/javaee"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5"
      xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
      http://java.sun.com/xml/ns/javaee/application_5.xsd">
       <display-name>SPE Test</display-name>
      
       <module>
       <web>
       <web-uri>spe-test.war</web-uri>
       <context-root>/spe-test</context-root>
       </web>
       </module>
      
       <module>
       <ejb>spe-test.jar</ejb>
       </module>
      
       <library-directory>lib</library-directory>
      
      </application>
      


      I get this error:

      DEPLOYMENTS MISSING DEPENDENCIES:
       Deployment "spe-input:service=inputServiceBean" is missing the following dependencies:
       Dependency "<UNKNOWN spe-input:service=inputServiceBean>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **")
      
      DEPLOYMENTS IN ERROR:
       Deployment "<UNKNOWN spe-input:service=inputServiceBean>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **
      


      Surely the jar I removed from the ear should be undeployed as it no longer exists as part of the ear?

      The only way to stop the error is to either restart JBoss or add the jar back into the ear and deploy it again.

      I'd be gratefult of any insight into this.

      Thanks,

      Ross


        • 1. Re: Deployment error using Service beans
          jaikiran pai Master

          Which version of the AS do you use? Can you please post the relevant console logs (not the server.log) from the point where your application is being deployed (for the first time) till this error? And also please include any exception stacktraces that you see on the console.

          • 2. Re: Deployment error using Service beans
            Ross Nicholson Apprentice

            I'm using the latest beta release 5.1.0.Beta.

            Here are the console logs:

            First deploy including service bean jar:

            10:59:37,526 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
            10:59:37,591 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
            10:59:37,633 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
            
             SecureProfileService/remote - EJB3.x Default Remote Business Interface
             SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
            
            10:59:38,439 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
            10:59:38,526 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
            10:59:38,556 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build: SVNTag=JBoss_5_1_0_Beta1 date=200903131506)] Started in 1m:7s:429ms
            11:00:50,949 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
            11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
            11:00:51,636 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@15332560{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
            11:00:51,726 INFO [JBossASKernel] Created KernelDeployment for: spe-input.jar
            11:00:51,726 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
            11:00:51,726 INFO [JBossASKernel] with dependencies:
            11:00:51,726 INFO [JBossASKernel] and demands:
            11:00:51,726 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
            11:00:51,726 INFO [JBossASKernel] and supplies:
            11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
            11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
            11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
            11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
            11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
            11:00:51,726 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
            11:00:51,726 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
            11:00:51,726 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3) to KernelDeployment of: spe-input.jar
            11:00:51,814 INFO [JBossASKernel] installing bean: spe-input:service=inputServiceBean
            11:00:51,814 INFO [JBossASKernel] with dependencies:
            11:00:51,814 INFO [JBossASKernel] and demands:
            11:00:51,814 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
            11:00:51,814 INFO [JBossASKernel] jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
            11:00:51,814 INFO [JBossASKernel] and supplies:
            11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
            11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
            11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
            11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
            11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
            11:00:51,814 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
            11:00:51,814 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
            11:00:51,814 INFO [JBossASKernel] Installing bean(spe-input:service=inputServiceBean) into kernel
            11:00:51,817 INFO [STDOUT] InputBeanService - Creating
            11:00:51,818 INFO [EJBContainer] STARTED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
            11:00:51,845 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
            
             spe-test/InputServiceBean/remote - EJB3.x Default Remote Business Interface
             spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote - EJB3.x Remote Business Interface
             spe-test/InputServiceBean/local - EJB3.x Default Local Business Interface
             spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal - EJB3.x Local Business Interface
            
            11:00:51,880 INFO [STDOUT] InputBeanService - Starting
            11:00:52,438 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
            
            


            And the deploy after removing the service bean jar:

            11:00:52,438 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
            11:01:42,663 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
            11:01:42,682 INFO [STDOUT] InputBeanService - Stopping
            11:01:42,683 INFO [STDOUT] InputBeanService - Stopped
            11:01:42,710 INFO [EJBContainer] STOPPED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
            11:01:42,710 INFO [STDOUT] InputBeanService - Destroying
            11:01:42,711 INFO [STDOUT] InputBeanService - Stopped
            11:01:43,211 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
            11:01:43,293 WARN [HDScanner] Failed to process changes
            org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
            
            DEPLOYMENTS MISSING DEPENDENCIES:
             Deployment "spe-input:service=inputServiceBean" is missing the following dependencies:
             Dependency "<UNKNOWN spe-input:service=inputServiceBean>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **")
            
            DEPLOYMENTS IN ERROR:
             Deployment "<UNKNOWN spe-input:service=inputServiceBean>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **
            
             at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
             at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)
             at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:127)
             at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:337)
             at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:229)
             at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
             at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
             at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
             at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
             at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
             at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
             at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
             at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
             at java.lang.Thread.run(Unknown Source)
            
            


            • 3. Re: Deployment error using Service beans
              jaikiran pai Master

               

              11:00:51,814 INFO [JBossASKernel] installing bean: spe-input:service=inputServiceBean
              11:00:51,814 INFO [JBossASKernel] with dependencies:
              11:00:51,814 INFO [JBossASKernel] and demands:
              11:00:51,814 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
              11:00:51,814 INFO [JBossASKernel] jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3


              This one looks a bit strange. It shows as deploying a service with an dependency (demands) on jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3. I don't see any obvious reason this dependency should be added on the service, unless it is declared through a jboss.xml or through a @Depends in the code. Furthermore, looking at the logs, it appears like the service is being installed as a management interface too under spe-input:service=inputServiceBean. Do you have a @ObjectName in the code for this service? Can you please post the appropriate @Service bean code including the management interface and the import statements? Please also post the contents of jboss.xml (if any).


              • 4. Re: Deployment error using Service beans
                Ross Nicholson Apprentice

                My jboss-app.xml is as follows:

                <jboss-app>
                 <loader-repository>
                 spe-test:archive=spe-test.ear
                 </loader-repository>
                </jboss-app>
                


                Here are the annotations used in the service bean:

                import javax.ejb.Local;
                import javax.ejb.Remote;
                
                import org.jboss.ejb3.annotation.Management;
                import org.jboss.ejb3.annotation.Service;
                
                @Service (objectName = "spe-input:service=inputServiceBean")
                @Local(InputServiceBeanLocal.class)
                @Remote(InputServiceBeanRemote.class)
                @Management(InputServiceBeanManagement.class)
                public class InputServiceBean implements InputServiceBeanLocal, InputServiceBeanRemote, InputServiceBeanManagement
                


                InputServiceBeanLocal:
                public interface InputServiceBeanLocal
                {
                 void start() throws Exception;
                 void stop();
                
                }
                


                InputServiceBeanRemote:
                public interface InputServiceBeanRemote
                {
                 void start() throws Exception;
                 void stop();
                
                }
                


                InputServiceBeanManagement:
                public interface InputServiceBeanManagement
                {
                 void create() throws Exception;
                 void start() throws Exception;
                 void stop();
                 void destroy();
                 String update(int val);
                }
                
                


                So I removed the objectName attribute of the @Service annotation. But it did not make much difference.

                New service bean annotations:

                import javax.ejb.Local;
                import javax.ejb.Remote;
                
                import org.jboss.ejb3.annotation.Management;
                import org.jboss.ejb3.annotation.Service;
                
                @Service
                @Local(InputServiceBeanLocal.class)
                @Remote(InputServiceBeanRemote.class)
                @Management(InputServiceBeanManagement.class)
                public class InputServiceBean implements InputServiceBeanLocal, InputServiceBeanRemote, InputServiceBeanManagement
                



                My console log is now the following (first deploy):

                12:31:44,010 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
                12:31:44,058 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
                12:31:44,080 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
                
                 SecureProfileService/remote - EJB3.x Default Remote Business Interface
                 SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
                
                12:31:44,365 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
                12:31:44,537 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
                12:31:44,580 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.Beta1 (build: SVNTag=JBoss_5_1_0_Beta1 date=200903131506)] Started in 1m:2s:388ms
                13:00:08,726 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@3695434{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
                13:00:08,740 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@3695434{vfszip:/opt/jboss-5.1.0.Beta1-jdk6/server/default/deploy/spe-test.ear/spe-input.jar/}
                13:00:08,849 INFO [JBossASKernel] Created KernelDeployment for: spe-input.jar
                13:00:08,849 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
                13:00:08,850 INFO [JBossASKernel] with dependencies:
                13:00:08,850 INFO [JBossASKernel] and demands:
                13:00:08,850 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
                13:00:08,850 INFO [JBossASKernel] and supplies:
                13:00:08,850 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
                13:00:08,850 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
                13:00:08,850 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
                13:00:08,850 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
                13:00:08,850 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
                13:00:08,850 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
                13:00:08,850 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
                13:00:08,850 INFO [JBossASKernel] Added bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3) to KernelDeployment of: spe-input.jar
                13:00:08,977 INFO [JBossASKernel] installing bean: jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface
                13:00:08,977 INFO [JBossASKernel] with dependencies:
                13:00:08,977 INFO [JBossASKernel] and demands:
                13:00:08,977 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
                13:00:08,977 INFO [JBossASKernel] jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3
                13:00:08,978 INFO [JBossASKernel] and supplies:
                13:00:08,978 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanRemote
                13:00:08,978 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote
                13:00:08,978 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanLocal
                13:00:08,978 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal
                13:00:08,978 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/remote
                13:00:08,978 INFO [JBossASKernel] jndi:spe-test/InputServiceBean/local
                13:00:08,978 INFO [JBossASKernel] Class:com.paddypower.spe.input.bean.service.InputServiceBeanManagement
                13:00:08,978 INFO [JBossASKernel] Installing bean(jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface) into kernel
                13:00:08,991 INFO [STDOUT] InputBeanService - Creating
                13:00:08,994 INFO [EJBContainer] STARTED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
                13:00:09,064 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
                
                 spe-test/InputServiceBean/remote - EJB3.x Default Remote Business Interface
                 spe-test/InputServiceBean/remote-com.paddypower.spe.input.bean.service.InputServiceBeanRemote - EJB3.x Remote Business Interface
                 spe-test/InputServiceBean/local - EJB3.x Default Local Business Interface
                 spe-test/InputServiceBean/local-com.paddypower.spe.input.bean.service.InputServiceBeanLocal - EJB3.x Local Business Interface
                
                13:00:09,136 INFO [STDOUT] InputBeanService - Starting
                13:00:10,342 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
                
                


                And after removing the jar:

                13:00:10,342 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
                13:00:35,500 INFO [TomcatDeployment] undeploy, ctxPath=/spe-test
                13:00:35,551 INFO [STDOUT] InputBeanService - Stopping
                13:00:35,551 INFO [STDOUT] InputBeanService - Stopped
                13:00:35,584 INFO [EJBContainer] STOPPED EJB: com.paddypower.spe.input.bean.service.InputServiceBean ejbName: InputServiceBean
                13:00:35,585 INFO [STDOUT] InputBeanService - Destroying
                13:00:35,585 INFO [STDOUT] InputBeanService - Stopped
                13:00:36,116 INFO [TomcatDeployment] deploy, ctxPath=/spe-test
                13:00:36,201 WARN [HDScanner] Failed to process changes
                org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
                
                DEPLOYMENTS MISSING DEPENDENCIES:
                 Deployment "jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface" is missing the following dependencies:
                 Dependency "<UNKNOWN jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **")
                
                DEPLOYMENTS IN ERROR:
                 Deployment "<UNKNOWN jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3,type=ManagementInterface>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.j2ee:ear=spe-test.ear,jar=spe-input.jar,name=InputServiceBean,service=EJB3' **
                
                 at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
                 at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)
                 at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:127)
                 at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:337)
                 at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:229)
                 at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
                 at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
                 at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
                 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
                 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
                 at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
                 at java.lang.Thread.run(Unknown Source)
                
                






                • 6. Re: Deployment error using Service beans
                  Ross Nicholson Apprentice

                  Thanks for looking into this. Hopefully a fix will make it into the next release.