Why JBoss always look for DefaultPartition for bound even I

[beaversx]

I set up a JBoss4.0.5 (ejb3-clustered installation) cluster with 3 nodes, and I use the following:
"run -Djboss.partition.name=newPartition -c a11"

I received the following log info:
11:36:26,544 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:ear=CMgmt.ear,jar=CMgmt.jar,name=CManagerImpl,service=EJB3
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultPartition not bound
I Depend On:
persistence.units:ear=CMgmt.ear,jar=CMgmt.jar,unitName=CMgmt

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:ear=CMgmt.ear,jar=CMgmt.jar,name=CManagerImpl,service=EJB3
State: FAILED
Reason: javax.naming.NameNotFoundException: DefaultPartition not bound
I Depend On:
persistence.units:ear=CMgmt.ear,jar=CMgmt.jar,unitName=CMgmt

When I use "run -c all" all problem gone. How can I setup the partition name correctly?

Thanks a lot.

[jaikiran]

I have never worked on clustering before so i might not be giving you a solution here. But i noticed that you are using:

run -Djboss.partition.name=newPartition -c a11

Shouldn't it be

run -Djboss.partition.name=newPartition -c all

Or is this just a typo?

[beaversx]

Yeah. It's typo. Thanks.