[Clustering/JBoss] - Re: change default partition name
by angelee
I can not find any documentation on JBoss AS 4.2. What am I doing wrong?
I changed all of the DefaultPartition to MYPartition in
deploy/cluster-service.xml.
e.g. FROM: {jboss.partition.name:DefaultPartition}
TO: {jboss.partition.name:MYPartition}
and in conf/standardjboss.xml
e.g. FROM: {jboss.partition.name:DefaultPartition}
TO: {jboss.partition.name:MYPartition}
I start the instance with this command:
# /opt/jboss-4.2.0.GA/bin/run.sh -c all -b10.40.0.35
and I get this error:
13:58:21,525 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.ha:service=HASingletonDeployer
State: CONFIGURED
I Depend On:
jboss:service=DefaultPartition
jboss.system:service=MainDeployer
ObjectName: jboss:service=FarmMember,partition=DefaultPartition
State: CONFIGURED
I Depend On:
jboss:service=DefaultPartition
jboss.web:service=WebServer
jboss.system:service=MainDeployer
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss:service=DefaultPartition
State: NOTYETINSTALLED
Depends On Me:
jboss.ha:service=HASingletonDeployer
jboss:service=FarmMember,partition=DefaultPartition
13:58:21,736 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-10.40.0.35-8080
13:58:21,797 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-10.40.0.35-8009
13:58:21,833 INFO [Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 57s:637ms
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053736#4053736
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053736
19Â years
[JBoss jBPM] - Re: How to tell if token is waiting?
by lachelt
Thanks for clarifying. No, I do not want to manipulate the token from the other thread. I figured that was a no-no. From my other thread I just want to know what node it is on. We want to provide users with some insight into what state the workflow is in.
In this case I think it is acceptable for the user to only have visibility into the previous rest state of a process. Any "long running" step in the workflow should be done asynchronously... the node should post some external request, and wait until that request has been satisfied.
If the workflow is marching along through some simple nodes that don't take much time (e.g. a decision node, or query to the DB) then the user would have to be aware that by the time they looked at the output of their request the workflow would already be beyond that point anyway. Probably at the next wait state.
At least that's my thought. Please let me know if I've said anything that doesn't sound right.
-Jon
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053727#4053727
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4053727
19Â years