January 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover possible dead lock

by timfox

So... when the producer detects the failover it (eventually) calls all the message callback handlers interruptReceiveThread() method, which calls interrupt() on the receive thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008077#4008077 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008077

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failover possible dead lock

by timfox

I don't think this is a deadlock - deadlock implies a race for two exclusive locks: thread 1 gets lock on resource A. thread 2 gets lock on resource B thread 1 tries to get lock on resource B and blocks thread 2 tries to get lock on resource A and blocks However, it's still an issue. Can't you interrupt the receive thread, to cause it to return? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008076#4008076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008076

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Failover possible dead lock

by clebert.suconic＠jboss.com

I found a possible dead lock on Failover / valves. This is the scenario: One Connection Two Threads .. Thread1 is called Consumer .. Thread2 is called Producer (Each thread will have its own session, of course) The Consumer thread will do: | | while (true) | { | Message message = consumer.receive(); System.out.println("Message = " + message); } While the Producer will do | while(true) | { | producer.send(session.createTextMessage("Message from producer " + id + " counter=" + (counter))); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008072#4008072 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008072

17 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Process definition element label attribute

by kukeltje

Come on Tom.... Now I do not get you anymore... you opposed the addition of the variable type to the jdpl file so strongly and now in addition to a name, a mappedname and a description, a new label is added? Then please include the variable type as well, and now I come to think of it, why not include the coordinates as well (like xpdl) The name is to be unique (like an id) is, on transitions used, for reference (like an idref) why not ditch the name/to then and realy use an ID and idref? the xsd standard can make sure these constraints are automatically met (a refid should point to an existing id, id's should be unique etc..etc..etc..ebBP uses this) Sorry if I sound a little frustrated (two STFF posts in 10 minutes) but I do mean what I say View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008048#4008048 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008048

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Issues with passivation of nested SFSBs

by bstansberry＠jboss.com

"bill.burke(a)jboss.com" wrote : Brian....so, if we attach the lifecycle of the child nested bean to that of its parent, will there be no problems? I believe the initial problem that led to this thread (orphaned ProxiedStatefulBeanContext left in cache) was a bug in StatefulTreeCache that can be easily fixed (StatefulTreeCache.remove() wasn't calling Pool.remove() when it should, preventing cleanup of the nested beans.) The issue of when to replicate still remains. If we follow Carlo's example where a ref to the nested bean is handed to another in-VM client, if that client causes replication, only the proxy is replicated. If instead, the cache finds the ultimate parent bean and replicates that, then there is the potential problem of the parent getting replicated multiple times as it invokes methods on its children. OK - I see the solution to that. Put a ThreadLocalStack in StatefulReplicationInterceptor; push and pop as the invocation proceeds; on the return side only replicate when the stack is empty. Similar to what the web session repl code does with cross-context requests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008032#4008032 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008032

17 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Web console changes - IMPORTANT

by kukeltje

sorry, that was not what I meant. I agree with you, but would like to be sure there is no other solution to this... I'm searching on google now to see if it is realy the RI or maybe something else. Stay tuned View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008025#4008025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008025

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Issues with passivation of nested SFSBs

by bill.burke＠jboss.com

Brian....so, if we attach the lifecycle of the child nested bean to that of its parent, will there be no problems? Another thing we could do is if the parent is removed, we can replace the Proxied with the real thing. It seems to me though that if you don't tie the lifecycle of the child to the parent, then if this usebase becomes prevalent, there could could quite possibly be orphaned beans. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008020#4008020 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008020

17 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Web console changes - IMPORTANT

by david.lloyd＠jboss.com

"kukeltje" wrote : I use doctype in all my seam pages and have no problems (FF1.5, 2.0, IE6). My seam apps use myfaces, so maybe it is a JSF-RI issue of not ripping out the doctypes. So Toms' observation is correct (since he also used myfaces) | | If I do not have doctypes in my pages, my eclipse plugin (exadel) cannot validate the pages, so I definately want the docstypes in. Well if the difference is between being broken for everyone using the RI, and not having eclipse be able to validate the XML, I'd rather break eclipse. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008013#4008013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008013

17 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Issues with passivation of nested SFSBs

by bill.burke＠jboss.com

I swear that the nested @Local SFSB shared the same lifecycle as its parent, but I cannot find it in the spec. I distinctly remember talking about it in the expert group. IMO, because of managed entities and extended PCs, we should implement the behavior this way, otherwise, it becomes impossible to reallign the object references. Ineed to reread and rethink the problem based on Brian's clustering problems... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008012#4008012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008012

17 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Web console changes - IMPORTANT

by kukeltje

I use doctype in all my seam pages and have no problems (FF1.5, 2.0, IE6). My seam apps use myfaces, so maybe it is a JSF-RI issue of not ripping out the doctypes. So Toms' observation is correct (since he also used myfaces) If I do not have doctypes in my pages, my eclipse plugin (exadel) cannot validate the pages, so I definately want the docstypes in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008006#4008006 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4008006

17 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums January 2007