June 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bounding the number of threads created by the MDB contai

by ovidiu.feodorov＠jboss.com

OK, let me think about a way to apply this to the 1 branch. As I said, the issue comes from very practical considerations, and it would be good if it gets fixed. What branch should I use to experiment with? Do you still keep the "release map" up to date? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156849#4156849 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156849

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bounding the number of threads created by the MDB contai

by timfox

We already do something similar in JBM 2.0 (to preserve the relative ordering) See http://anonsvn.jboss.org/repos/messaging/trunk/src/main/org/jboss/messagi... The problems of deadlock still remain though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156848#4156848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156848

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by scott.stark＠jboss.org

"anil.saldhana(a)jboss.com" wrote : All you have to do is start AS5 and wait a minute or so.... So it is only in F9? Apparently. I have a default AS5 instance that has been running for ~6 hours under osx without any change in descriptor/port counts. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156846#4156846 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156846

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bounding the number of threads created by the MDB contai

by ovidiu.feodorov＠jboss.com

All you need is to maintain the order of the deliveries relative to a session. It doesn't really matter what thread runs a delivery, whether is the same thread or different thread, as long as the relative order is preserved. "Booking" a thread for each session, while it is a solution that works at a small scale, breaks down when the problem grows in size. As long as you agree with this, solutions can be found. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156845#4156845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156845

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by emuckenhuber

"anil.saldhana(a)jboss.com" wrote : All you have to do is start AS5 and wait a minute or so.... So it is only in F9? Hmm i also tried it on Fedora 8 with the same result View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156844#4156844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156844

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by emuckenhuber

"scott.stark(a)jboss.org" wrote : The server has been running for a couple of hours now with no increase in file descriptors or ports. I suspect its the "Too many open files" causing the issues. What are the ulimits your running under? | ulimit is unlimited anonymous wrote : | If you have an lsof output you can send it to me. | on the way View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156843#4156843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156843

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

Use GParted (free from sf.net) to quickly create a partition your disk and do an install of F9 over the network (if possible). This may get things faster for you. For now, we just bounce the AS frequently (a minute delay to recycle which is fine). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156842#4156842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156842

17 years, 10 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bounding the number of threads created by the MDB contai

by timfox

I guess I have misunderstood what you are suggesting then. If you pool the threads, then how do you guarantee that all deliveries (say) for a particular session are delivered in order. This is the piece of the puzzle I am missing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156841#4156841 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156841

17 years, 10 months

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner exception

by anil.saldhana＠jboss.com

All you have to do is start AS5 and wait a minute or so.... So it is only in F9? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156840#4156840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156840

17 years, 10 months

1
0
0 / 0

[Design of EJB 3.0] - JBPAPP-864/EJBTHREE-1109 - clustered home proxies

by galder.zamarreno＠jboss.com

Re: http://jira.jboss.com/jira/browse/JBPAPP-864 As promised, I've attached a ZIP file containing: - patch file with the fix and the corresponding test cases. - zip containing the html reports of the entire EJB3 test suite run with the fix. Regarding the reports, there's only two tests failing, one is org.jboss.ejb3.test.bank.unit.BankDeploymentDescriptorTestCase which I couldn't reproduce the failure when run individually and org.jboss.ejb3.test.invoker.unit.InvokerTestCase which is not even part of the continous build and I'm planning to phase out anyway (see http://jira.jboss.com/jira/browse/JBAS-5464). Other than these two tests, everythin looks good :) With regards to the fix, one thing to note: Both SLSB and SFSB containers would create a new bean factory whenever home.create() was called. We can't do this for clustered homes because the creation of a new factory is pretty expensive (create HATargets, create FamilyClusterInfo....etc) and after having a quick chat with Brian don't think would work. So, as you can see from the code, I've used different tricks to be able to retrieve the factory itself. They're probably hacks but they seem to work Ok and this fix is oriented at AS/EAP 4.x so it was never gonna be pretty. It is my intention to tackle this JIRA in trunk once I've got the EAP fix done as deadline for this comes earlier and for the trunk version, I'm happy to discuss design of this further. The aim with AS/EAP 4.x is to get it to work. On top of that, I've added some much needed TRACE logging here and there to be able to figure out what happens inside of EJB3 as I don't always have a debugger at hand :) A quick note about the patch itself. It contains some code that is changed when EAP 4.x is checked out. This is part of the magic that switches between EAP 4.3 and 4.2. The code changed by this magic is fairly obvious and hope it doesn't confuse you. Please let me know if you need a patch without this. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156839#4156839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156839

17 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums June 2008