[JBoss jBPM] - Re: Token.setNode(Node) method
by AlClientView
Thanks for replying...
Well, I warned the customer saying it might be possible but there would not be any "roll back"... Which means that things already done (actions, logging...etc...) are done and won't be undone by any "roll back" function beside setting back the Token to a previous node.
For example if in the node 4 a variable called Name has been set to "Bernie", and the Token is set back from node 8 to node 4, the variable Name would still be set to "Bernie". It would be the same as if there was a transition... The difference is that the transition does not exist on the graph.
The customer is ok with that...
Beside the "roll back" aspect... Do you see any other possible issues then ?
Thanks,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984357#3984357
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984357
19Â years, 6Â months
[Clustering/JBoss] - clustering in SUse entreprise server 9.0
by cocteau
I have 2 nodes(application server) JBOSS 4.0.4 GA version and one load balancer(apache 2.0.58/mod jk1.2.15) I try to make both work on a sticky session fashion It means when I make a the load balancer a request node A resolves having node B disabled.
I enable node B and then both nodes synchronize sessions(I see this through jboss console how versioning goes along) I disable node A
and node B keeps resolving requests with the same session.
When I enable node A and still B enable expecting it resolves requests nad it seems to be synchronized however if I disable node B it no longer resolves my request and the message I get is:cannot add session with id=session(session id) workername(name of worker of node A) because it is invalid.
We tried with JDK 1.5 and 1.4 our application is set as distributable and the jboss-web.xml is
<replication-config>
<replication-trigger>SET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
and we also tried with
<replication-config>
<replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
we also tried cache replication syncronous and asyncronous
we also tried isolation level repeteable_read and read_uncommited(dirty read)
we also tried change of setting in jgroup from udp to tcp
We are using Suse enterprise server 9.0
funny we tried in windows and it went through
any suggestion?
I've been trying to solve this problem through these last 3 weeks
I would really appreciate your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984352#3984352
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984352
19Â years, 6Â months
[Installation, Configuration & Deployment] - clustering
by cocteau
I have 2 nodes(application server) JBOSS 4.0.4 GA version and one load balancer(apache 2.0.58/mod jk1.2.15) I try to make both work on a sticky session fashion It means when I make a the load balancer a request node A resolves having node B disabled.
I enable node B and then both nodes synchronize sessions(I see this through jboss console how versioning goes along) I disable node A
and node B keeps resolving requests with the same session.
When I enable node A and still B enable expecting it resolves requests nad it seems to be synchronized however if I disable node B it no longer resolves my request and the message I get is:cannot add session with id=session(session id) workername(name of worker of node A) because it is invalid.
We tried with JDK 1.5 and 1.4 our application is set as distributable and the jboss-web.xml is
<replication-config>
<replication-trigger>SET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
and we also tried with
<replication-config>
<replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>
we also tried cache replication syncronous and asyncronous
we also tried isolation level repeteable_read and read_uncommited(dirty read)
we also tried change of setting in jgroup from udp to tcp
funny we tried in windows and it went through
any suggestion?
I've been trying to solve this problem through these last 3 weeks
I would really appreciate your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984350#3984350
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984350
19Â years, 6Â months
[JBoss Seam] - Re: Sun Java studio Creator 2 and JBoss Seam
by arondaniel
Hello,
Although I'm not attempting to use SEAM (just JSF) this page seems the closest match to what I'm experiencing.
I'm using jboss4.0.4.GA, default JSF, and attempting to deploy a war with Sun rave UI in it, from Java Studio Creator 2.
Just like you mentioned, the sun ui components don't render at all, but I don't get any exceptions either.
o I'm including sun's jars in the ear containing the war (except sun jsf jars)
o I copied Sun's jstl.jar and default.jar to deploy/jbossweb-tomcat55.sar.
o I added in the creator.taglib.xml as you explained, and context-param in web.xml
Still the same thing, no errors, nothing rendered.
Do you have any suggestion?
Thanks,
-Aron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984348#3984348
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984348
19Â years, 6Â months
[JBossCache] - Cannot evict node if the node is put into cache with FQN gen
by jeffreyai
Hi there,
We are using Jboss Cache 1.4.0.GA and are running into an eviction problem. It seems any node put into cache with Long-type FQN cannot be evicted.
The code is like below.
| Fqn BASE_FQN = new Fqn("xx/product");
| final Fqn fqn = new Fqn(BASE_FQN, Long.valueOf(productUid));
| cache.put(fqn, product);
|
We tried to trace into the TreeCache.java.
It seems the code always trying to remove a child node by giving a String key.
Here are the code section I quoted from the "_remove" method in TreeCache.java.
| // remove subtree from parent
| parent_node.removeChild(n.getName());
|
If we change the code to use String, then eviction works fine.
| final Fqn fqn = new Fqn(BASE_FQN, String.valueOf(productUid));
|
Do I missed something or is this a bug.
BTW, Our eviction strategy is defined as below:
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass">
| org.jboss.cache.eviction.LRUPolicy
| </attribute>
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <!-- This is the interval (in seconds) to process the node events and also to perform
| sweeping for the size limit and age-out nodes. -->
| <attribute name="wakeUpIntervalSeconds">10</attribute>
|
| <!-- Cache wide default -->
| <region name="/_default_">
| <!-- This is the maximum number of nodes allowed in this region. Any integer less than or equal to 0
| will throw an exception when the policy provider is being configured for use. -->
| <attribute name="maxNodes">50000</attribute>
|
| <!-- Time to idle (in seconds) before the node is swept away. 0 denotes no limit. -->
| <attribute name="timeToLiveSeconds">600</attribute>
|
| <!-- Time an object should exist in TreeCache (in seconds) regardless of idle time before the
| node is swept away. 0 denotes no limit. -->
| <attribute name="maxAgeSeconds">3600</attribute>
| </region>
| </config>
| </attribute>
|
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984347#3984347
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3984347
19Â years, 6Â months