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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging code review

by timfox

What about 5) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193932#4193932 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193932

17 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Why do Topic/Queue descriptors need extra metadata in or

by scott.stark＠jboss.org

There is a DestinationMOBuilder that builds the QueueService and TopicService destination classes ManageObjects from the QueueServiceMO and TopicServiceMO skeleton classes so that all destinations have the correct ManagedObject created without having to be annotated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193926#4193926 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193926

17 years, 4 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: Designing of jain-slee deployers for Jboss5.

by alexandrem

"alesj" wrote : There is no such mechanism in new deployers. | Since they work on a totally different system of what we used to have. | | Before if was (mostly) single deployer that did it all, | not it's a chain of unrelated deployers that are metadata driven. | So, even if some deployer is 'missing' that doesn't mean deployment wasn't deployed. | It just might be that that particualr deployer didn't provide it's input/output, | but that's hard/costly to fix - it would mean you have to re-deploy all deployments. | | But I agree, it make sense to do this for those deployments which we know weren't 'touched' by any deployer. | Perhaps a MC/Deployers 2.2 feature. ;-) Hope so! It's a must-have feature, IMO. :) "alesj" wrote : | In your case I see two options. | | 1) put SLEE into deployers | - conceptually ugly/wrong and not hot-re-deployable | Hmm... wouldn't like to have this and it's not possible without separating some components, as Mobicents depends on certain components that are not loaded at this stage. "alesj" wrote : | 2) use jboss-dependency.xml | - http://www.jboss.org/community/docs/DOC-13178 | | e.g. some pseudo xml code | <dependency xmlns="urn:jboss:dependency:1.0"> | | <item whenRequired="Describe">SLEEDeployer</item> | | </dependency> | | Where your SLEEDeployer gets SLEE injected. | | The only issue here is in which phase your SLEEDeployer kicks in? | If it's before PreDescribe, this won't work, since we're already past that. | This looked like a good option... but we start at PARSE phase, and that seems like an issue, cause adding the jboss-dependency.xml didn't solved the problem. Something I might consider would be running everything at the Real deployer, but that was a problem also due to the fact that we relied on the old deployers behavior, which would deliver, in different stages, childs first than parents, ie, if a.jar had {a1.jar, a2.jar} inside, CREATE/START would process it like: {a1.jar, a2.jar, a.jar} but now in order to achieve that behavior I need to call the old ACCEPTS/INIT on Parse and CREATE/START on Real. One other thing I've noticed and would like some help on it, is the fact that the jars are not exploded anymore into a tmp folder, the reference to them now comes as, and using the above example, .../server/default/deploy/a.jar/a1.jar and .../server/default/deploy/a.jar/a2.jar instead of the old way .../server/default/tmp/deploy/tmpXXXXXa.jar-contents/a1.jar. We used JarFile/JarEntry to handle it but now it fails due to those references not being a valid path for JarFile/JarEntry. I've managed a workaround for it, having a wrapper for the DeploymentUnit which will then enable me to return an InputStream to read the files... but not sure this is a good practice. Thanks & sorry for the (very) long post, Alexandre Mendonca JBoss R&D View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193913#4193913 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193913

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Paging code review

by clebert.suconic＠jboss.com

anonymous wrote : 1. Use OrdereredExecutorFactory for thread management. This should make the global pager redundant. I have this done on my local copy already.. I'm just waiting some tests to finish before I commit this tomorrow. anonymous wrote : 3. Much of the functionality currently in PagingManagerImpl is better placed in PagingStoreImpl, e.g. addSize, ondePage. This would also simplify the code since less lookups would be needed and several methods could be removed or made private. done anonymous wrote : 4. PagingStoreImpl - The locking is very complex. Can this be simplified by using Condition objects with the lock? Or perhaps we can disallow concurrent writes to the same page - which would simplify the locking. IS there really much performance to be gained by concurrent writes to the same page? Can this be verified with a test? The readWriteLock is used to avoid synchronized access on the verification on isPaging(). I wanted to not create any contention when paging is not activated. I have changed the code not allow multiple writes, but the lock schema is pretty much the same. anonymous wrote : | 6. PagingStoreImpl::page() | | Calculation of block size and lock acquisition: | | done anonymous wrote : | 7. PagingStoreImpl::page | | pagedUsedSize is being incremented twice? | | Not really.. openNewPage is setting it to 0, then it needs to be added again. anonymous wrote : | 8. TransactionImpl: | | An address can switch from paging to not paging mid way during a transaction before it is committed, resulting in the transactions messages being routed out of order | | 9. TransactionImpl: | | Currently paged messages are paged on commit(). If there are a lot of paged messages this could hold up the remoting thread for a significant amount of time, | | One of the design principles of the server is each operation should be quick to complete to avoid starving other operations.l | | We should consider instead, writing transactional actions straight to a file in the paging case, then on commit, since we know they are on file we can process them on a different thread and the commit can return ok immediately. This would also allow us to deal with huge transactions, much bigger than can fit in memory at once | | I want to do that as part HugeTransaction task. anonymous wrote : 10. Currently routing code is duplicated in ServerSessionImpl::send, TransactionImpl and in depage logic. This should be put in one place. This goes beyond of paging... but I will do that tomorrow. I'm still missing 2, but that should be easy. (Unless we decide to do something more complex such as hole-detection the way I have done on the Journal). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193911#4193911 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193911

17 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Declaration and deployment of threads and thread pools i

by david.lloyd＠jboss.com

...and I've created one. It makes sure that the queue submit unblocks after the worker thread dies. The executor used in the test is basically a regular ThreadPoolExecutor with the same queue wrapper, except I wrap the wrapped queue again to add addtional blocking so that the queue unblocks right when the race would occur - when the worker thread from the first task exits leaving zero threads in the pool. http://anonsvn.jboss.org/repos/sandbox/david.lloyd/jboss-threads/trunk/ma... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193909#4193909 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193909

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - ServiceTestBase

by clebert.suconic＠jboss.com

I have created for some time already a class on the testsuite called ServiceTestBase encapsulating createSerivce, directory creation and other things alike there. I just thought it would be better to have such encapsulation... than start servers all over the place in different ways when most tests are doing the same. So... when you create a new test that starts a server you should maybe use that class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193907#4193907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193907

17 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Declaration and deployment of threads and thread pools i

by david.lloyd＠jboss.com

In regards to the empty pool vs. blocking policy race condition... I think my solution solves the deadlock. Since the blocking occurs on the offer() rather than reject(), ThreadPoolExecutor has code in place to handle this problem (they need to handle it anyway - even if offer() works in the normal nonblocking fashion, the condition may still occur where the task is added to the queue but no threads remain to handle it). Namely, after successfully adding an element to the queue, it checks to verify that there is at least one thread around to handle the task, and if not, it starts one. I'm in the process now of figuring out a test case that artificially creates this scenario... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193891#4193891 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193891

17 years, 4 months

1
0
0 / 0

[Javassist development Forum] - help me please

by bantumi

Hello everybody. I'm working with Javassist and have trouble with the directory when i try to create a class (use makeClass()). I'd like to make a class in a determine Folder(such as C:\temp\). How can i do? Thanks everybody. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193888#4193888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193888

17 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2.0 Strict ordering via ordering groups

by timfox

"ataylor" wrote : anonymous wrote : What's the advantage in allowing multiple consumers? If you're ordering, then by definition, you will need to serialise consumption | | I was just taking this from the comments on the Jira, 'In order to guarantee strict ordering, even on rollback or in the presence of multiple consumers or with xa transactions, the queue needs to ensure that no more than one message with the value of ordering group is being delivered at any one time.' | I still don't see the advantage of multiple consumers. anonymous wrote : | So you send 10 messages, 5 for group A, with seq 1 to 5, and 5 for group B again with seq 1 to 5. A consumer consumes message group A seq 1 but does not acknowledge, the next message in group A with seq 2 can't be delivered but message group B seq 1 can, This gives you strict ordering within the defined group. | Yes, but the current message grouping also provides that same ordering guarantee, does it not? anonymous wrote : | The producer can specify on send the sequence number of a message to specify its delivery order. I'm not sure what that means. Again, does not message groups preserve delivery order. I'm just trying to understand here how message grouping does not accomplish the goal. The goal here is to provide strict ordering of delivery of messages, even on rollback and with multiple consumers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193875#4193875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193875

17 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: KernelDeploymentDeployer and annotations in MDR

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : | The issue appears to be that for the plain deployment, | we don't necessarily have the classloader from which we can | create the annotations. e.g. | | | <deployment> | | <classloader><inject name="BeanConstructedLaterOrInThisFile"></classloader> | | <annotation>@from.that.Classloader</annotation> | | </deployment> | | | It could create a static MetaDataLoader if the class loader was not a bean or not a bean that was available, otherwise how could a MetaDataLoader that was a bean be integrated into the deployment MetaData view? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4193867#4193867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4193867

17 years, 4 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 December 2008