Uploaded image for project: 'Application Server 3  4  5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-2615

error using schedule-manager-service.xml at the boot in mode 'all'

XMLWordPrintable

      when I configure schedule-manager-service.xml and I boot jboss application server I have an error about dependence and so it don't deploy the SingleScheduleProvider mbean. But if I deploy schedule-manager-service.xml when jboss is started I haven't this problem. SingleScheduleProvider mbean need to activate the DefaultPartition for clustering. Indeed org.jboss.varia.scheduler.SingleSchedulerProvider extends indirectly org.jboss.ha.jmx.HAServiceMBeanSupport that throws an Exception if it don't find almost a cluster in the system. The problem is resolved add a <depends> tag in the schedule-manager-service.xml so:

      <mbean code="org.jboss.varia.scheduler.SingleScheduleProvider"
      name="jboss:service=SingleScheduleProvider">
      <depends>jboss:service=ScheduleManager</depends>
      <depends>jboss:service=SchedulableMBeanExample</depends>

      <!--------- new update -------->
      <depends>jboss:service=${jboss.partition.name:DefaultPartition}</depends>
      <!--------- end update --------->

      <attribute name="ScheduleManagerName">jboss:service=ScheduleManager</attribute>
      <attribute name="TargetName">jboss:service=SchedulableMBeanExample</attribute>
      <attribute name="TargetMethod">hit( NOTIFICATION, DATE, REPETITIONS, SCHEDULER_NAME, java.lang.String )</attribute>
      <attribute name="DateFormat">hh:mm:ss</attribute>
      <attribute name="StartDate">19:47:12</attribute>
      <attribute name="Period">1000</attribute>
      <attribute name="Repetitions">1</attribute>
      </mbean>

              dandread1@redhat.com Dimitrios Andreadis
              luca.stancapiano@vige.it Luca Stancapiano (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: