April 2007 - jboss-development - Jboss List Archives

jboss-remoting-testsuite-1.4 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Failed

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

jboss-4.0-testsuite-win-sun-1.4 Build Failed

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

Re: Default jbosscache usage in JBoss AS 4.2/EJB3

by Brian Stansberry

Forwarding to Carlo and Bill DeCoste. The hibernate.cache_region.prefix would need to be derived from the deployment scope, probably the same algorithm used to create JMX ObjectNames for the deployment's beans. Want to keep the name fairly short, as it gets transmitted with every replication/invalidation message. Emmanuel Bernard wrote: > Don't know who exactly, but definitely, Carlo should be aware of that. > > On 17 avr. 07, at 09:57, Max Rydahl Andersen wrote: > >> Hi guys, >> >> From various discussions I understand that JBoss AS 4.2 currently >> deploys a single JBC instance for use as a shared cache across EJB3 >> deployments >> and that individual EJB3 deployments will by default share the same >> cache resulting in them sharing the same cache regions. >> >> That is bad! >> >> Two independent applications should not share the same cache regions - >> they should *always* be seperated by setting >> hibernate.cache_region.prefix so >> they only get access to the data that is actually relevant for them. >> >> There will also be classloading issues with such a scheme. >> >> From my understanding the place to fix this is in the ejb3 deployer to >> use whatever unique name these deployments have so the same >> cache_region.prefix >> will be set correctly across different nodes etc. >> >> If the above assumption about 4.2 is correct, who is the right person >> to fix that ? >> >> ---- >> Max Rydahl Andersen >> callto://max.rydahl.andersen >> >> Hibernate >> max(a)hibernate.org >> http://hibernate.org >> >> JBoss a division of Red Hat >> max.andersen(a)jboss.com > -- Brian Stansberry Lead, AS Clustering JBoss, a division of Red Hat brian.stansberry(a)redhat.com

18 years, 11 months

1
0
0 / 0

Re: Default jbosscache usage in JBoss AS 4.2/EJB3

by Carlo de Wolf

Hmm, we did a discussion on this a while back. But then it was more about cache start/stop semantics. Does anybody recall the subject line, so I can find it? Carlo On Tue, 2007-04-17 at 10:32 -0400, Emmanuel Bernard wrote: > Don't know who exactly, but definitely, Carlo should be aware of that. > > On 17 avr. 07, at 09:57, Max Rydahl Andersen wrote: > > > Hi guys, > > > > From various discussions I understand that JBoss AS 4.2 currently > > deploys a single JBC instance for use as a shared cache across EJB3 > > deployments > > and that individual EJB3 deployments will by default share the same > > cache resulting in them sharing the same cache regions. > > > > That is bad! > > > > Two independent applications should not share the same cache > > regions - they should *always* be seperated by setting > > hibernate.cache_region.prefix so > > they only get access to the data that is actually relevant for them. > > > > There will also be classloading issues with such a scheme. > > > > From my understanding the place to fix this is in the ejb3 deployer > > to use whatever unique name these deployments have so the same > > cache_region.prefix > > will be set correctly across different nodes etc. > > > > If the above assumption about 4.2 is correct, who is the right > > person to fix that ? > > > > -- > > -- > > Max Rydahl Andersen > > callto://max.rydahl.andersen > > > > Hibernate > > max(a)hibernate.org > > http://hibernate.org > > > > JBoss a division of Red Hat > > max.andersen(a)jboss.com >

18 years, 11 months

1
0
0 / 0

Re: [jboss-dev] JBoss Messaging - to scope or not to scope

by Tim Fox

Ram Venkataraman wrote: > I talked to Ovididu about a month or so ago when Messaging went GA and > spoke about integration JBM into 4.x and I clearly remember asking > about remoting. He did not raise any red flags, in fact we spoke of it > being compatible. I don't have any explanations why he would say that - we have been dependent on remoting 2.2 for some time now. I have harping on about this to various people for some months - well before CR1. Dimitris created a JIRA task some time ago to gather various projects dependencies so we could align them: http://jira.jboss.org/jira/browse/JBAS-3886 In that, you can see I make it clear we use remoting 2.2. I have also made this very clear in other emails between various other involved people. > > I will raise this in the next platform meeting. We are ready to go to > beta next week. We definitely cannot change anything at this time. I am > adding Patrick to this thread to see if this something that we can > change during the beta period without much impact. > > Do we know what impact an upgrade to Remoting 2.2 have on the other > parts of the appserver ? > > Ram > >

18 years, 11 months

2
1
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 11 months

1
0
0 / 0

Default jbosscache usage in JBoss AS 4.2/EJB3

by Max Rydahl Andersen

Hi guys, From various discussions I understand that JBoss AS 4.2 currently deploys a single JBC instance for use as a shared cache across EJB3 deployments and that individual EJB3 deployments will by default share the same cache resulting in them sharing the same cache regions. That is bad! Two independent applications should not share the same cache regions - they should *always* be seperated by setting hibernate.cache_region.prefix so they only get access to the data that is actually relevant for them. There will also be classloading issues with such a scheme. From my understanding the place to fix this is in the ejb3 deployer to use whatever unique name these deployments have so the same cache_region.prefix will be set correctly across different nodes etc. If the above assumption about 4.2 is correct, who is the right person to fix that ? -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate max(a)hibernate.org http://hibernate.org JBoss a division of Red Hat max.andersen(a)jboss.com

18 years, 11 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-development April 2007