Petals ESB CLI

If a component installer is loaded, Petals CLI can't deploy it in a second step

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0.0
  • Fix Version/s: 2.1.0
  • Component/s: Command 'deploy'
  • Security Level: Public
  • Description:
    Hide
    1. Using the JVisualVM, load a component installer
    2. Using Petals CLI and the command deploy, we get the following error that is normal:
      ERROR: java.lang.Exception: org.ow2.petals.kernel.api.server.PetalsException: Other installation package already exists loaded in the component framework: petals-bc-soap
      	at org.ow2.petals.jbi.management.installation.InstallationServiceImpl.loadNewInstaller(InstallationServiceImpl.java:331)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:37)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:244)
      	at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1074)
      	at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:955)
      	at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203)
      	at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
      	at com.sun.jmx.remote.security.MBeanServerAccessController.invoke(MBeanServerAccessController.java:447)
      	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
      	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
      	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
      	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
      	at sun.rmi.transport.Transport$1.run(Transport.java:159)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
      	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
      	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
      	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      	at java.lang.Thread.run(Thread.java:662)
      Caused by: org.ow2.petals.kernel.api.server.PetalsException: Other installation package already exists loaded in the component framework: petals-bc-soap
      	at org.ow2.petals.jbi.management.task.installation.install.component.ComponentCheckPackageTask.checkPackage(ComponentCheckPackageTask.java:82)
      	at org.ow2.petals.jbi.management.task.AbstractCheckPackageTask.execute(AbstractCheckPackageTask.java:57)
      	at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)
      	at org.ow2.petals.jbi.management.installation.InstallationServiceImpl.loadNewInstaller(InstallationServiceImpl.java:328)
      	... 40 more

    Instead of the error, Petals CLI should continue the lifecycle until the state 'STARTED'

    Show
    1. Using the JVisualVM, load a component installer
    2. Using Petals CLI and the command deploy, we get the following error that is normal:
      ERROR: java.lang.Exception: org.ow2.petals.kernel.api.server.PetalsException: Other installation package already exists loaded in the component framework: petals-bc-soap
      	at org.ow2.petals.jbi.management.installation.InstallationServiceImpl.loadNewInstaller(InstallationServiceImpl.java:331)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:37)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:244)
      	at javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1074)
      	at javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:955)
      	at mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:221)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
      	at mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203)
      	at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
      	at com.sun.jmx.remote.security.MBeanServerAccessController.invoke(MBeanServerAccessController.java:447)
      	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1427)
      	at javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:72)
      	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1265)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1367)
      	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:788)
      	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      	at java.lang.reflect.Method.invoke(Method.java:597)
      	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
      	at sun.rmi.transport.Transport$1.run(Transport.java:159)
      	at java.security.AccessController.doPrivileged(Native Method)
      	at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
      	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
      	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
      	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      	at java.lang.Thread.run(Thread.java:662)
      Caused by: org.ow2.petals.kernel.api.server.PetalsException: Other installation package already exists loaded in the component framework: petals-bc-soap
      	at org.ow2.petals.jbi.management.task.installation.install.component.ComponentCheckPackageTask.checkPackage(ComponentCheckPackageTask.java:82)
      	at org.ow2.petals.jbi.management.task.AbstractCheckPackageTask.execute(AbstractCheckPackageTask.java:57)
      	at org.ow2.petals.jbi.management.TaskProcessor.process(TaskProcessor.java:76)
      	at org.ow2.petals.jbi.management.installation.InstallationServiceImpl.loadNewInstaller(InstallationServiceImpl.java:328)
      	... 40 more
    Instead of the error, Petals CLI should continue the lifecycle until the state 'STARTED'
  • Environment:
    -

Issue Links

Activity

Hide
Christophe DENEUX added a comment - Wed, 19 Sep 2012 - 18:41:45 +0200

Fixed in trunk,
User documentation updated

Show
Christophe DENEUX added a comment - Wed, 19 Sep 2012 - 18:41:45 +0200 Fixed in trunk, User documentation updated
Hide
Christophe DENEUX added a comment - Wed, 19 Sep 2012 - 16:50:28 +0200 - edited

To continue the lifecycle, the existing installer will be unloaded (depends on PETALSESBCONT-207) and a new one will be loaded.

Show
Christophe DENEUX added a comment - Wed, 19 Sep 2012 - 16:50:28 +0200 - edited To continue the lifecycle, the existing installer will be unloaded (depends on PETALSESBCONT-207) and a new one will be loaded.

People

Dates

  • Created:
    Wed, 12 Sep 2012 - 09:20:57 +0200
    Updated:
    Thu, 20 Sep 2012 - 16:30:46 +0200
    Resolved:
    Wed, 19 Sep 2012 - 18:41:45 +0200