problems in jboss3.2.2

[normal]

I found that examples in schedule-manager-service.xml can't be deployed correctly in version 3.2.2, while that works well in version 3.2.1.

in version3.2.2, I got the following errors:
2003-10-23 16:03:08,674 WARN [org.jboss.system.ServiceController] Problem starting service jboss:service=SingleScheduleProvider
java.lang.NullPointerException
at org.jboss.ha.jmx.HAServiceMBeanSupport.registerRPCHandler(HAServiceMBeanSupport.java:173)
at org.jboss.ha.jmx.HAServiceMBeanSupport.startService(HAServiceMBeanSupport.java:142)
at org.jboss.varia.scheduler.AbstractScheduleProvider.startService(AbstractScheduleProvider.java:236)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
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:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
at $Proxy14.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:394)
at org.jboss.system.ServiceController.start(ServiceController.java:411)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
at $Proxy6.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:302)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:458)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:212)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:191)

why?

[normal]

There is another problem.
In version 3.2.1 i can create a ejb named category/name, but this name result in an error in version 3.2.2: category/name is an invalid java identifier name.

why?

[juha]

You're not allowed to use / in your ejb-name. If you want to create subcontexts in JNDI you must use the <jndi-mapping> element in your beans jboss.xml descriptor.

-- Juha

[osganian]

Does anybody have a solution to this? I am getting the same exact error on 3.2.3.

[darranl]

Borrowing from a previous post :-

You're not allowed to use / in your ejb-name. If you want to create subcontexts in JNDI you must use the <jndi-mapping> element in your beans jboss.xml descriptor.

[osganian]

Thanks, but I'm not using '/' in my name. I get the same error (the stack trace part) if I use the example defined in the schedule-manager-service.xml file in the default/deploy directory. I uncommented out the xml in that configuration file and it gets the same stack trace.

Here is the snippet (using the example provided by JBoss) of the server.log:

2004-04-27 10:46:00,900 INFO [org.jboss.deployment.MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.3/server/default/deploy/schedule-manager-service.xml
2004-04-27 10:46:01,011 INFO [org.jboss.varia.scheduler.example.SchedulableMBeanExample] Started jboss:service=SchedulableMBeanExample
2004-04-27 10:46:01,031 INFO [org.jboss.varia.scheduler.ScheduleManager] Started jboss:service=ScheduleManager
2004-04-27 10:46:01,151 ERROR [org.jboss.varia.scheduler.XMLScheduleProvider] Starting failed
java.lang.NullPointerException
at org.jboss.ha.jmx.HAServiceMBeanSupport.registerRPCHandler(HAServiceMBeanSupport.java:173)
at org.jboss.ha.jmx.HAServiceMBeanSupport.startService(HAServiceMBeanSupport.java:142)
at org.jboss.varia.scheduler.AbstractScheduleProvider.startService(AbstractScheduleProvider.java:236)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
...

10:46:59,037 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:

Incompletely deployed packages:

MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss:service=XMLScheduleProvider
state: FAILED
I Depend On: jboss:service=ScheduleManager
jboss:service=SchedulableMBeanExample

Depends On Me: java.lang.NullPointerException]

Thanks for any help,
Mike

[osganian]

You need to set the HASingleton=false attribute in a non-clustered environment to get the example code to work.