[JBoss-user] Deployment problems going from 3.0.6 -> 3.2.1

[Torsten T. <jb...@te...>]

Hi

We are trying to move our apps from 3.06 to 3.2.1, and have bumbed in to two
problems.

We have some common jar files containing ejb and normal classes, and a lot
of ears containg only deployment descriptors. This ways we can share the
code between our applications (wich are all identical), by giving them
different jndi names, datasource etc. Now each of these ear's contain a sar
which constists of only a jboss-service.xml. This sar file is a scheduler
and the scduler class named in the jboss-service.xml is located in one of
the common jars. This have worked fine in 3.0.6, but now the scheduler won't
deploy:

org.jboss.deployment.DeploymentException: Exception setting attribute
javax.management.Attribute: name=SchedulableClass
value=zzz.xxx.yyy.Scheduler on mbean jboss:service=MyScheduler; - nested
throwable: (java.security.InvalidParameterException: Given class
zzz.xxx.yyy.Scheduler is not instance of Schedulable)

I suspect it is class cast issue, since the class is indeed an instance of
schedulable and it has worked fine in 3.0.6. Any ideads?

The second thing we see, is that each ear we deploy will result in a
InstanceAlreadyExistsException. This also happens for normal self-contained
ears, not only the ears descripbed above.

DEBUG [org.jboss.management.j2ee.J2EEApplication] Could not create JSR-77
J2EEApplication:
jboss.management.local:J2EEServer=Local,j2eeType=J2EEApplication,name=myapp.
ear
javax.management.InstanceAlreadyExistsException:
jboss.management.local:J2EEServer=Local,j2eeType=J2EEApplication,name=myapp.
ear already registered.

Although we get the above exception, the apps seem to be running just fine,
but we would offcource rather be without it. Have anyone seen this
behaviour?

Thanks in advance..

Torsten