1 Reply Latest reply on Feb 2, 2006 3:44 AM by Dimitris Andreadis

    Is SingleScheduleProvider broken or end-of-lifed in 4.0.3?

    Mark McGregor Newbie

      I'm converting from jboss 3.2.x to 4.0.3SP1 for unix.

      We have a number of mbeans that we formerly deployed under a ScheduleManager using org.jboss.varia.scheduler.SingleScheduleProvider.

      Under 4.0.3 I get a


      org.jboss.deployment.DeploymentException: Unexpected error during load of: org.jboss.varia.scheduler.SingleScheduleProvider, msg=org/jboss/varia/scheduler/AbstractScheduleProvider; - nested throwable: (java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.varia.scheduler.SingleScheduleProvider, msg=org/jboss/varia/scheduler/AbstractScheduleProvider)
       at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:178)
       at org.jboss.system.ServiceController.install(ServiceController.java:215)
      ...
      ...
      Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: org.jboss.varia.scheduler.SingleScheduleProvider, msg=org/jboss/varia/scheduler/AbstractScheduleProvider
       at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:512)
       at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:377)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
       at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:1189)
       at org.jboss.mx.server.MBeanServerImpl.instantiate(MBeanServerImpl.java:271)
       at org.jboss.mx.server.MBeanServerImpl.createMBean(MBeanServerImpl.java:329)
       at org.jboss.system.ServiceCreator.install(ServiceCreator.java:124)
       at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:431)
       at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:153)
      
      


      Just to verify that this was not my code causing the problem I took the default deploy and uncommented the appropriate mbeans in schedule-manager-service.xml and got the same error. If the jboss provided example doesn't work then I'm going to assume that the problem is most likely not my code.

      So is this truly broken or is the code end-of-lifed?