[JNDI/Naming/Network] - Why JBoss always look for DefaultPartition for bound even I
by 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.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012575#4012575
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012575
19Â years, 2Â months
[EJB/JBoss] - Re: Need
by juhaï¼ jboss.org
"eharoldw" wrote : In order to do this with an interceptor, would I not have to make a separate thread?
yes.
most state is held in the invocation object with couple of notable exceptions (security, tx on the thread), so basically you could disconnect your incoming thread from the actual worker thread by passing the invocation on -- you can return the calling thread based on your timeout and appropriate timeout indicators and let the worker thread die eventually if it didn't finish within the given time limit.
this however is going well beyond the EJB component contract and the expected behavior which is why a custom container (via interceptors) is probably what you should do (clean break from EJB component model) -- you may even be best doing this with purely POJO and/or AOP containers rather than EJB, depending on how much you rely on the other existing services the EJB spec provides (tx, sec, concurrency, pooling, etc).
hope it helps
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012573#4012573
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012573
19Â years, 2Â months