Distributed scheduler over a cluster

[rjego]

Hello,

I'm trying to deploy a distributed scheduler over a cluster. I've got an IllegalArgumentException (full message -> RuntimeMBeanException: java.lang.IllegalArgumentException: interface org.jboss.ha.framework.server.ClusterPartitionMBean is not visible from class loader)

For deployment reasons, all files are packaged in a single ear, with an isolated ClassLoader.

My deployment file is like :

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE server>

<server>
 <mbean code="mypackage.MyService"
 name="jboss:service=MyService">
 <!--@@depends>jboss:service=myPartition</depends@@-->
 </mbean>

 <mbean code="org.jboss.varia.scheduler.ScheduleManager"
 name="jboss:service=ScheduleManager">
 <attribute name="StartAtStartup">true</attribute>
 </mbean>

 <mbean code="org.jboss.varia.scheduler.SingleScheduleProvider"
 name="jboss:service=HASingleScheduleProvider">
 <depends>jboss:service=myPartition</depends>
 <depends>jboss:service=ScheduleManager</depends>
 <depends>jboss:service=MyService</depends>
 <attribute name="HASingleton">true</attribute>
 <attribute name="PartitionName">myPartition</attribute>
 <attribute name="ScheduleManagerName">jboss:service=ScheduleManager</attribute>
 <attribute name="TargetName">jboss:service=MyService</attribute>
 <attribute name="TargetMethod">execute</attribute>
 <attribute name="DateFormat">dd/MM/yy HH:mm</attribute>
 <attribute name="StartDate">NOW</attribute>
 <attribute name="Period">10000</attribute>
 <attribute name="Repetitions">-1</attribute>
 </mbean>
</server>

Everything works well if I set HASingleton attribute to false. But the the scheduler is not distributed...

Thanks for help

Reynald

[ben.wang]

Is there a reason why it must be under an isolated classloader? The scoped classloader can be the problem because ClusterPartitionMBean is deserialized by the system one.

-Ben

[rjego]

I have to deploy several versions of my ear. But as I don't want to share classes between these versions, I use an isolated ClassLoader.

I really hope it is not definitly incompatible with a distributed scheduler over a cluster !