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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management removing all messages on shutdown

by clebert.suconic＠jboss.com

"timfox" wrote : "clebert.suconic(a)jboss.com" wrote : Problem is, | | | | If the user is really undeploying a Queue, the messages should go away, | | | | No, deploying just means removing from JNDI, it does not mean deleting messages! | Ok.. what you do when the user really undeploy the queue then? You just leave the messages on the journal? (Well... yes is not really an option here!) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170826#4170826 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170826

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management removing all messages on shutdown

by timfox

"clebert.suconic(a)jboss.com" wrote : Problem is, | | If the user is really undeploying a Queue, the messages should go away, | No, deploying just means removing from JNDI, it does not mean deleting messages! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170825#4170825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170825

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message redistribution in JBM 2.0 - request for feedback

by clebert.suconic＠jboss.com

"clebert.suconic(a)jboss.com" wrote : IMO the user should have an option. | | In some cases where you don't have more than few messages/second in a queue, the Singleton queue would make more sense for the user, but in cases where you would flood the servers the clustered queue is necessary. | What I meant to say is... as we discussed in the past.. for some cases a single Queue on the Cluster (That's why I said Singleton... the naming here should be correct) would make more sense than the Partial Queue, for cases where you don't need performance. (There is a JIRA for that .. I know). If we had that option.. I would vote to just keep the Partial Queue the way it is on 1.4, and implement the Single queue on the cluster. That's my vote.. but I'm not necessarily an interface with the user... so I value more the vote of folks who do the interface. (Like JeffDelong who is a trainer or Jay who is on support) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170824#4170824 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170824

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: JavaDocs for CR2

by bstansberry＠jboss.com

If you have maven installed, from the varia dir: mvn javadoc:javadoc The docs will be generated into varia/target/site/apidocs These might be available via some other means, but I just did that and it worked. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170823#4170823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170823

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management removing all messages on shutdown

by clebert.suconic＠jboss.com

My suggestion was a simple change on the shutdown hook: | public void shutDown() | { | log.info("Shutting down"); | ListIterator<KernelDeployment> iterator = deployments.listIterator(deployments.size()); | while (iterator.hasPrevious()) | { | KernelDeployment deployment = (KernelDeployment) iterator.previous(); | someHowInvokeStop(deployment); | } | } | And besides that, we should also change the method stop on JMSServerDeployer, as that is calling undeploy. I just don't want to take the risk of messages hanging on the journal when you don't have a queue any more. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170821#4170821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170821

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message redistribution in JBM 2.0 - request for feedback

by jeffdelong

I teach classes on the JBoss ESB / SOA Platform. ESB uses JBM clustered queues to achieve high availability and scalability. I describe the feature exactly as Tim has described it; and students seem to accept this as reasonable / preferable behavior. I would not want to see this change in the future. Customers just need to be better educated. Jeff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170820#4170820 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170820

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Management removing all messages on shutdown

by clebert.suconic＠jboss.com

Problem is, If the user is really undeploying a Queue, the messages should go away, while if you just shutdown the server that doesn't mean undeploying. (just stop) (Especially with the journal schema, where reclaiming would break.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170819#4170819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170819

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - JavaDocs for CR2

by anuman36

Not sure if this a little bit of the ServiceBindingManager topic but the building of the nightly build does not seem to generate javadocs for the api. Where can I find the javadocs or generate it from the CR2 nightly build. I see the target in the build-common.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170816#4170816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170816

17 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Message redistribution in JBM 2.0 - request for feedback

by jhowell＠redhat.com

Yeah Singleton has a loaded meaning and we should probably not use it jbm terms because it's confused with the jboss terms. If we didn't have partial queue on each machine, what would be the alternative for load balancing messages in a queue. Would we(I'm just throwing out some thoughts)... 1. Only allow one(it an it's buddy) node on the cluster to hold the actual queue(I think this is what Clebert was talking about). Then when a consumer hits a node in the cluster, it's directed to the one that has the actual queue on it. This would allow a consumer to go to anynode in the cluster and ask for a queue, where by it would be redirected to the machine that has the real queue, but the actual queue would be on one node. 2. Drop load balancing support all together for queues and make consumers go to the machine that the queue is on(either that or it's backup node). So the clients would have to have some knowledge of what queues are on what boxes in the cluster. 3. Replicate the entire queue to one or more buddies. Performance would go down, but uses could choose to have the queue completely replicated on each node. We spoke about making the number of buddies in the cluster configurable, so you could choose, just one for failover or multiple. In this same paradigm users could choose which nodes in the cluster will have the queue. I do think that the idea of pulling messages around the ring of nodes was a little confusing to users(especially when they start using selectors), but I do think that the ability to be able to load balance consumers on different boxes, doing local access(without having to hop to a different cluster member) is a definite need. So I'd start off with what I would believe the requirements to be from a customer stand point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170814#4170814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170814

17 years, 7 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Dynamic AOP API

by kabir.khan＠jboss.com

"flavia.rainone(a)jboss.com" wrote : | I mean, for simple operations we should try to keep it simple, making it possible to execute the whole thing in a couple of lines? | In this case, I think we could maintain the dbo, using it with more complex bindings. Agreed View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170799#4170799 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170799

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