November 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBossCache] - Re: Default classloader for deserialization

by max.andersen＠jboss.com

It should be the TCCL that is in effect for the application that needs to read/write to the cache. Wether that is actually possible because of the asynchronous ways of JBC usage...that is the question. (I guess this is why bstansberry talked about classloader per region) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989694#3989694 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989694

17 years, 11 months

1
0
0 / 0

[Design of JBossCache] - Re: Default classloader for deserialization

by manik.surtani＠jboss.com

Well, to boil it down (and from what I understand) is that the default CL used is by JGroups, in the RpcDispatcher, when deserializing MethodCall objects streamed over the wire. And you are talking about overriding this with the TCCL in effect when JBossCache is instantiated? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989693#3989693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989693

17 years, 11 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-880 discussion ...

by manik.surtani＠jboss.com

And there actually has been a thread on the user forum about this too, although I still think usage only makes sense for pretty specific cases. About your implementation - how does this work with existing eviction policies? Also, why the use of an 'expiration' element, vs. a more explicit attribute on Node - Node.setTTL() or something? And what are the semantics of this - millis since last accessed, millis since created, or expiry at a specific time? Perhaps this is best in the form of a pluggable policy too? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989689#3989689 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989689

17 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-eventing clustering problem

by heiko.braun＠jboss.com

Thanks for the detailed explanation. Now i clearly see the problem. The eventing specs allow for SubscriptionManager interposition. This means you can have multiple event sources being handled by just one subscription manager. In composition with WS-Addressing a subscription response contains the subscription manager EPR (endpoint reference). Which basically is the URL plus reference parameters. Applying this idea to your cluster topology means that you would have a single SubscriptionManager instance running on a particular node, addressed through WS-Addressing. Still this lacks some features that would need to be implemented: - SubscriptionManager runs HA-Singleton - There would only be one EventDispatcher, available through HA-JNDI - Event sources need to know the subscription manager EPR details. This could be propagated through HA-JNDI. Does this make sense to you? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989686#3989686 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989686

17 years, 11 months

1
0
0 / 0

[Design of JBoss Web Services] - ws-eventing clustering problem

by maeste

As Heiko asked me some times ago I tried to describe in deep when ws-eventing SubscriptionManager need to be clustered in our opinion. I wrote a post on our blog describing the problem and our proposed solution including a Sequence diagram to help me in the description. I reported here the text of the post, but I kindly suggest to read the post on the blog, because the Sequence Diagram is very useful IMHO. Let me know if you prefer me to transfer it to a wiki page. The post is this one: http://www.javalinux.it/blogs/index.php?title=ws_eventing_clustering_prob... Of course we would have fun to work on this issue. * Subscription on one of the clustered environment's machine DESCRIPTION: when a client subscribes to our ws-eventing service the load balancer sends his requests to a real server that receives the subscription and store it locally (in current jbossws eventing implementation this is achieved using a Map owned by SubscriptionManagerMbean). An event source generates a notification and delegates its notification to jbossws; but in a cluster environment this event source could use a different real server knowing nothing about the subscriber. The notification would be lost. See messages from 1 to 5 in the above diagram. Of course a very similar situation may happen when renewing a subscription: a renew message cold be send to a server different from the one that received the first subscription, resulting in subscription renew failure. The client will receive an "Unable to renew" exception, and on the server side the subscription will expire for timeout! All notifications are lost until client re-subscribe to the right real server. See messages from 6 to 13 in the above diagram. PROPOSED SOLUTION: These two problems could be solved clustering the SubscriptionMap. The easiest solution would probably be arranged using HAJNDI to store subscriptions. Of course the use of a local Map instead of HAJNDI have to be configured at deploy time. * Shutdown of one of the cluster's machine DESCRIPTION: SubscriptionManagerMbean sends notifications to remove every subscriptions when it is stopped or the real server it runs on shutdowns. But in a cluster environment other servers continue to work and potentially to send notifications. Those notifications will be lost. See messages from 14 to 26 in the above diagram. PROPOSED SOLUTION: SubscriptionManagerMbeans have to be clustered and have to exchange their status before they can decide to send this kind of notifications. The solution could be implemented using jGroups (of course), but it needs further investigations and discussions, mainly to understand if SubscriptionManager is the only part of jbossws needing clustered solutions View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989678#3989678 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989678

17 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Configure JBPM

by jinsonjacob＠gmail.com

How can i configure JBPM for standalone Application ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989674#3989674 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989674

17 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Re: DeploymentInfo and DeploymentContext information

by vickyk

It looks that a DeploymentUnit(DU) contains multiple DeploymentContext(DC) and each DC is linked to only one DU . Considering the deployment as | A.sar(DC1) | -->B.sar(DC2) | ---------->C.ear(DC3) | ---------->D.ear(DC4) | --->E.ear(DC5) | ---------->G.war(DC6) | ----------->H.war(DC7) | ---->I.jar(EJB) (DC8) | And all the DC's for a Tree which is represented by DU , this is logical relationship . Is this how it goes ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989646#3989646 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989646

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Hibernate as Messaging persistence layer

by thejavafreak

Dear all, Is it true that in the future JBoss messaging will use hibernate for the persistency? If it is, I think it will be a great idea. Because when I had a hard time when migrating the datasource from hsqldb to postgres in JBoss5. I have to remark the 'create table on startup' back and forth to true and false parameter each time I install the Appserver. Hibernate got this feature update value in 'create table on startup'. So, can we know in what release this feature will be available? Cheers, Joshua View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989635#3989635 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989635

17 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Branch 1_0_XARecovery

by timfox

Sounds reasonable View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989633#3989633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989633

17 years, 11 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Problems with replicating entity queries via JBC

by max.andersen＠jboss.com

but scoped classloading is what we want to allow deployment of apps that uses different versions of classes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989611#3989611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989611

17 years, 11 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 November 2006