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

[Design of EJB 3.0] - Re: [EJBTHREE-788] Align Default timeout of SFSB and HttpSes

by ALRubinger

I just spoke to Pete, who pointed me to: http://seamframework.org/Community/ApplicationInstabilityInMultiuserEnvir... This talks about SFSB removal, not passivation. The default is now: @org.jboss.ejb3.annotation.CacheConfig (maxSize=100000, idleTimeoutSeconds=300, removalTimeoutSeconds=0) ...where "0" means "don't remove the bean as part of a timeout". So either: 1) The issue is now fixed in EJB3 by nature of us not removing a SFSB 2) EJB3 is applying a removal timeout when it shouldn't. The removals are reaped by a Thread with a name prefix of "SFSB Removal Thread - ", by default as defined by SimpleStatefulCache. Pete and I have agreed to curb this pending further evidence that the issue is still present. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182474#4182474 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182474

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - Re: [EJBTHREE-788] Align Default timeout of SFSB and HttpSes

by ALRubinger

"ALRubinger" wrote : Possible to get Seam to hook into the SFSB lifecycle callbacks and on passivation/reactivation? I came across this in an email from Pete: "Pete Muir" wrote : We can't easily switch to using passivation/activation callbacks as at that point the session (at least for SFSBs) and conversation (though if we have the session, we could work around this) aren't available. So my question becomes: can you make it available? :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182464#4182464 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182464

16 years, 3 months

1
0
0 / 0

[Design of EJB 3.0] - [EJBTHREE-788] Align Default timeout of SFSB and HttpSession

by ALRubinger

https://jira.jboss.org/jira/browse/EJBTHREE-788 Seam is requesting a bump of the default SFSB timeout (==passivation, not removal) from 5 minutes to at least 30. I'm not comfortable with this for the following reasons: 1) Possible abrupt memory profile changes for our users upon upgrade that brings in this change 2) There's nothing binding the timeouts of SFSB and HttpSession, so this makes a problem less frequent but not properly resolve it But the real nagging point is that EJBTHREE-788 does not specify *why* this needs to be done; Brian notes in a discussion w/ Pete that likely managed objects stored in HttpSession get out of sync when references to these are unbound upon SFSB passivation? Possible to get Seam to hook into the SFSB lifecycle callbacks and on passivation/reactivation? S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182463#4182463 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182463

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JSR77 View

by scott.stark＠jboss.org

These are the attachment types: EJB = JBossMetaData attachment CAR = JBossClientMetaData attachment EAR = JBossAppMetaData attachment WAR = JBossWebMetaData attachment RAR = RARDeploymentMetaData attachment JCA = ManagedConnectionFactoryDeploymentGroup attachment JMS = ServiceMetaData attachment with a code value of either org.jboss.jms.server.destination.QueueService org.jboss.jms.server.destination.TopicService View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182421#4182421 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182421

16 years, 3 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Can we have Multiple Layout for a page?

by PMN

Changing the layout of a page dynamically is definitively a must have feature. I do not believe that this feature is supported by the current version, neither being addressed in the next. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182415#4182415 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182415

16 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: JSR77 View

by alesj

"adrian(a)jboss.org" wrote : | So you could for example have an EJBJSR77Deployer that looks at the | ejb metadata and then either creates the ServiceMetaData for the relevant | jsr77 mbean(s) or talks to the LocalJBossServerDomain directly. | How do I know what all is ejb metadata? Looking at the JBossMetaData attachment? | public org.jboss.metadata.ejb.jboss.JBossEnterpriseBeansMetaData getEnterpriseBeans() { /* compiled code */ } | | public org.jboss.metadata.ejb.jboss.WebservicesMetaData getWebservices() { /* compiled code */ } | | public org.jboss.metadata.ejb.jboss.ResourceManagersMetaData getResourceManagers() { /* compiled code */ } | Checking all of these, or just enterprise beans? But even better question is how to collect all the metadata for JCA / RAR. Just looking at the jca-deployers-jboss-beans.xml gives me shivers. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182402#4182402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182402

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Project JAXR mavenization suggestions

by richard.opalka＠jboss.com

I'll take care of that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182399#4182399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182399

16 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Project JAXR mavenization suggestions

by anil.saldhana＠jboss.com

The following need to be done to the mavenized JAXR project. 1) The parent of the project needs to be set to the JBoss parent. This way you get all the definitions of plugins inherited (source, jar, release) etc. An example is how the security project has done. http://anonsvn.jboss.org/repos/jbossas/projects/security/security-jboss-s... I suggest following the setup done by other projects such as JBoss Microcontainer. 2) Incorporate the maven release plugin which will do the pom modification to next version, tagging etc automatically for you. The current process of updating the poms to release version, tagging and then reverting the pom versions to next snapshot is tedious/error-prone and better left to the maven release plugin. 3) Fix the 3rd party issue. https://jira.jboss.org/jira/browse/JBAS-6098 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182397#4182397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182397

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Mavenised build and Eclipse

by kabir.khan＠jboss.com

The thirdparty folder has now been removed. This means Eclipse now picks up the thirdparty files from your local maven repository so you need to set up a M2_REPO classpath variable in Eclipse to point to that. If you update versions of dependencies in the root pom.xml you need to run mvn eclipse:eclipse to regenerate the Eclipse .classpath files to point to those new versions. This uses the dependency information in the pom.xml's to generate the classpath settings. I have commited the ones resulting from my local run. If you refresh from subversion and you do not yet have the versions referenced in the .classpath files in your local repository, you need to run mvn install from the root of your aop checkout which will populate your local maven repository. Another thing is that having your eclipse workspace in your aop checkout folder will no longer work, since the eclipse plugin uses different names for the projects than previously. There might be other ways around this, but the way I have got around this for this and other projects is to create the workspace in jboss-aop/eclipse and to have the subversion checkout in jboss-aop/subversion. Some of the folders/files need to be excluded from the build for compilation errors of things that cannot be found. These are: jboss-aop-aspects/src/test/org/jboss/test/asynch jboss-aop/src/main/org/jboss/aop/hook/JRockitClassPreProcessor.java The eclipse plugin does not exclude these. I have manually excluded these in the .classpath files. Paul, is there a way to have the eclipse plugin exclude these when generating the .classpath files? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182364#4182364 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182364

16 years, 3 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Reimplementing ClassPools for AS

by kabir.khan＠jboss.com

The work so far has been commited against https://jira.jboss.org/jira/browse/JBAOP-666 I've had to look at other things so far this week, so unfortunately I don't think this will be done before the GA cutoff point on Monday. I will try to make the existing code work for Adrian's original comments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182340#4182340 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4182340

16 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2008