September 2006 - jboss-dev-forums

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-549 - Lease set to -1 causes exception

by clebert.suconic＠jboss.com

anonymous wrote : To make things a little simplier, do you think it would be useful to add another method such as: | | void setLeaseEnabled(boolean) It would make sense IMO. However if you throw an exception on setLeasePeriod(<0) isn't that a signature change? We would have to change some testcases using setLeasePeriod(-1) hoping to disable lease. If you *must* change the API we will need to plan ahead. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973576#3973576 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973576

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Removed feature requests for JBossMQ

by adrian＠jboss.org

I've closed a lot of feature requests for JBossMQ which are unlikely to ever get done. I've attached he following message to the issues. | Closing features that are (or will be) implemented in JBoss Messaging. | http://jira.jboss.com/jira/browse/JBMESSAGING | | If anybody wants to provide a patch that implements these, | the issue can be reopened. | | Duplicates of these issues will be closed | unless they provide an implementation/patch. | | Patches should first be discussed in the | development forum: | http://www.jboss.com/index.html?module=bb&op=viewforum&f=153 | if there isn't already a forum link attached to this issue. | The remaining open issues in the "JMS Service" are either application integation issues or real (but not very important) issues in JBossMQ (like making the testsuite more robust). I did leave two feature requests which should be trivial to implement: Exposing number of messages currently being processed, i.e. delivered to clients but not yet acknowledged: http://jira.jboss.com/jira/browse/JBAS-3386 Browsing scheduled messages: http://jira.jboss.com/jira/browse/JBAS-3228 I plan to get these two done for 4.0.5.GA assuming nothing important comes up. Once those are done, I won't be accepting new feature requests for JBossMQ unless they come with an intention to implement it, like this one: http://jira.jboss.com/jira/browse/JBAS-2156 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973572#3973572 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973572

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-545 - Leaks on XA transactions

by clebert.suconic＠jboss.com

For III this is being done at the end of Commit/Rollback (not a finally block). Also, deleteTransaction is double checking for the state of the transaction. If you try to delete a transaction which is not in COMMITED or ROLLEDBACK state it will throw an exception. I wanted to have this double check since I knew this constraint. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973566#3973566 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973566

19 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Action Processing Pipelines, updated Trailblazer etc...

by tfennelly

"daniel.brum(a)jboss.com" wrote : Guys, using XStream on both sides was just a convenience, nothing more. The TB is about showing how to use the Beta of the ESB features, nothing to do with writing banks and their systems, etc. | | I would not bother with re-writing those aspects of the TB now. lol,.. too funny Dan! That's exactly what I said... "...we're not demoing writing banking systems ...". I changed it after anyway - XStream still on both sides but the classes are in different packages so peoples Eclipse etc doesn't complain about dup classes etc Once I get the Transformation stuff in there (very close), I'll engineer the Trailblazer such that the XML generated on the Loanbroker side will require a transformation before sending to the Bank. That should add nicely to the Trailblazer! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973565#3973565 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973565

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Usable deployers

by adrian＠jboss.org

"weston.price(a)jboss.com" wrote : Parsing and construction of the MeteData of the *-ds.xml file for Datasource deployment (first pass) is in HEAD. What remains is the conversion of the MetaData into something that can be used by the new deployment framework (if I understand how the new stuff works). | | I was going to finish this in conjunction with the port of the RARDeployer: | | http://jira.jboss.org/jira/browse/JBAS-3415 | | I've already ported (well more hacked :-) the old versions of the RARDeployer and ConnectionFactory deployer in MC-VDF-WORK so that they are part of the new deployment framework. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973513#3973513 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973513

19 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: Updating docs

by adrian＠jboss.org

If a metadata file is being parsed then it is potentially something that could be passed in as a predetermined managed object. i.e. You override the factory settings using the profile service or a management tool. To identify what is overridable (it is parsed from metadata files), it populates the transient managed objects which the profile service/front end can override by promoting the modified object to the predetermined section. They are different from the plain attachments which are just temporary artifacts of the deployment that deployers use to communicate with each other. P.S. Not sure that managed object is a good name for this since it conflicts with the real managed object created from this object + annotations on the class. Metadata is probably better but that also conflicts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973512#3973512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973512

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-545 - Leaks on XA transactions

by timfox

"clebert.suconic(a)jboss.com" wrote : | | So, summarizing the changes I'm making to fix this: | | I - I'm creating a method deleteTransaction on TransactionRepository. | | II - I also changed Transaction to accept a reference to TransactionRepository, as TransactionRepository is not static. | | Sounds good anonymous wrote : | III - On commit/rollback transactionRepository.delete is being called | Fine. Make sure this is done at the end of the processing and not in a finally block - we don't want to remove the tx if it fails (the tx mgr can retry) anonymous wrote : | | IV - Changed JDBCPersistenceManagerTest to perform a test on this | | V - Added a property method getNumberOfRegisteredTransactions() on TransactionRepository what is meant to be used only by tests. (I could use reflection on a private field for this, but I thought it was much cleaner to just add the property field. I could change this if someone doesn't like the exposed property) | | | Fine. Also we need to make sure we return ok if a commit request comes in for a 2pc transaction and it isn't in the map. There is a second part of this tasks which involves looking in the database if a request comes in for a transaction and it isn't in the map - but it's probably best to wait for Madhu to integrate his XA recovery work since you will need to re-use some of that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973509#3973509 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973509

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by timfox

Sounds good. One of the key requirements here is that the code should work the same irrespective of whether we're using the socket, transport, http transport or whatever. I.e. we want to avoid stuff like: | | if (transport == http) | { | //do it this way | } | else | { | //do it this way | } | | If you can find a way of doing that, that's great. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973488#3973488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973488

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Incorporating Remoting http transport into Messaging

by ron_sigal

Here's what I've got so far. As a first approximation, replacing the current Messaging push callbacks with Remoting's polling simulation of push callbacks is pretty easy. On the client side, CallbackManager is transformed from a ServerInvocationHandler to an InvokerCallbackHandler. When the Remoting poller pulls callbacks from the server, it passes them to CallbackManager, which proceeds as before. On the server side, instead of passing around the remoting callback Client, which was being used to make explicit invocations that were processed by CallbackManager, the ServerInvokerCallbackHandler from which the callback Client was obtained is passed around. Instead of calling Client.invoker(), ServerConsumerEndpoint.Deliverer calls ServerInvokerCallbackHandler.handleCallback(), which, since it is configured for pull callbacks, just stores the callback with its load of messages. Eventually the client side poller will retrieve them and pass them to CallbackManager. To some extent, these changes work. E.g., simple tests like HttpExample and QueueExample work. However, some of the more complex tests, for example, MessageConsumerTest.redel8(), fail. It looks like CallbackManager is trying to deliver the messages to a Consumer that has already closed. I'll need to look at this some more. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973481#3973481 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973481

19 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Virtual hosts and multiple portal server instances

by yxyang

i have no idea how to submit. The navigation portlet is a standalone portlet package. how to submit as patch? yang View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3973475#3973475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3973475

19 years, 6 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 September 2006