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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management operation over JBM 2 Core API

by jmesnil

"timfox" wrote : | What about, the current add/delete queue/address methods on the transport? Are these necessary now we can do that through management? Yes, we still need them to create the destination and the (temp) queue which is used to receive the management messages View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173354#4173354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173354

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Thread usage in AIO layer

by clebert.suconic＠jboss.com

If the file.close takes a lot of time to finish (more than what it would take to write a whole new file), the server will wait until a new file is opened. But from what I have seen on my tests TimeCompletion < TimeWrite, i.e. by the time a new file is required you will already have a new file opened. what means this condition shouldn't happen under regular circumstances. That's why I think this is not an issue. It would only happen if the disk was really slow. (Maybe some other application sharing the disk with JBM, and that would cause delays anyway). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173353#4173353 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173353

15 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: ClientUserTransaction and TxPropogation inefficiencies

by jhalliday

> The ClientUserTransaction is only a proxy to a real transaction on the server so JTS is irrelevant for normal clients Unfortunately not. If a normal (i.e. without ORB) client is using UT to communicate to a server and that server is switched from the JTA to the JTS, the client will break. Of course that may be a bug rather than a design issue. Then there is the question of what the behaviour should be when the client is using RMI/IIOP rather than JRMP for transactional calls to the server. Should it need the JBossTS libraries, or should it continue to use UT? What if it wants to switch to JBossTS? Using either the JTA API or the CORBA API for transaction demarcation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173351#4173351 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173351

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management operation over JBM 2 Core API

by timfox

"jmesnil" wrote : | Once I'm done with that, the only remaining task wrt to management will be to be able to subscribe to a management topic to receive notifications. What about, the current add/delete queue/address methods on the transport? Are these necessary now we can do that through management? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173349#4173349 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173349

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Thread usage in AIO layer

by timfox

You didn't answer the question, "what happens in this case"? ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173348#4173348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173348

15 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: ClientUserTransaction and TxPropogation inefficiencies

by adrian＠jboss.org

"jhalliday" wrote : You missed the big one, which is: It won't work with the JTS. Since the JTS is going to be a supported option shortly, we should probably figure out what we want to do about that :-) What do you mean? UserTransaction is JTA not JTS. The ClientUserTransaction is only a proxy to a real transaction on the server so JTS is irrelevant for normal clients. If there is a transaction manager on the "client" then we use ServerVMClientUserTransaction which is just a wrapper for that JTA implementation. UT.begin() -> TM.begin() etc. Of course whether/how that "client" will propogate the TPC to the real server maybe an issue you need to resolve, but it is irrelevant whether the transaction was started using the UserTransaction api or some other use of the client's TM. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173347#4173347 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173347

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management operation over JBM 2 Core API

by jmesnil

i agree with your suggestion, it'll make the management code more flexible. I still need to write some unit tests before committing. Once I'm done with that, the only remaining task wrt to management will be to be able to subscribe to a management topic to receive notifications. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173345#4173345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173345

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Thread usage in AIO layer

by clebert.suconic＠jboss.com

anonymous wrote : What happens in that case? That could happen if you have a slow disk. But if you have a slow disk, you would have waits on writing and waiting transactions to complete anyways. I don't think it is an issue based on the measures I've taken on the waitForAnOpenFile. I can take some meausres if you like. There is on possible change: Start the native thread on the nextOpenFile only when the file was returned. We keep it opened but without a thread. That would save us one thread. That means. AIO files would have three states. Opened, Active(poller thread running) and Closed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173342#4173342 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173342

15 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: ClientUserTransaction and TxPropogation inefficiencies

by jhalliday

You missed the big one, which is: It won't work with the JTS. Since the JTS is going to be a supported option shortly, we should probably figure out what we want to do about that :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173339#4173339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173339

15 years, 7 months

1
0
0 / 0

[Design of JBoss Transaction Services] - ClientUserTransaction and TxPropogation inefficiencies

by adrian＠jboss.org

This isn't really related to the TM, more JBoss's remote UT. I've fixed this race condition in the initialisation which Galder found while load testing: https://jira.jboss.org/jira/browse/JBAS-5904 While looking at the code, I noticed a couple of other issues this thread can be used for discussions: Leaving remote initial contexts to be closed by the GC https://jira.jboss.org/jira/browse/JBAS-5904 Inefficient determination of the TPC factory due to "broken" caching and duplicate jndi lookups https://jira.jboss.org/jira/browse/JBAS-5908 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173338#4173338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173338

15 years, 7 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 August 2008