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

[Design of POJO Server] - Re: extra jars needed when deploying a Seam app into JBAS5 b

by alesj

"charles.crouch(a)jboss.com" wrote : | Any ideas why/how this is occurring and what can be done about it? | Since you need to make Seam be VFS aware. And since you're deploying Seam core with your app, you cannot simply put a single jboss-seam-as5.jar into configuration lib, because the VFS impl would then miss the Scanner class. Meaning, Seam As5 specific classes would be in parent CL of Seam core CL, and hence not being able to see them At the moment we did it that way, but the discussion about it will take place at JBW. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125215#4125215 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125215

16 years, 11 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler 2

by jesper.pedersen

You properly need to include the JAVA_OPTS directly in run.bat. No need to update the PROFILER setting. Otherwise you should be ok in your setup - let me know if this works. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125207#4125207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125207

16 years, 11 months

1
0
0 / 0

[Design of POJO Server] - extra jars needed when deploying a Seam app into JBAS5 beta4

by charles.crouch＠jboss.com

Link to a discussion in the Seam forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125083#4125083 Any ideas why/how this is occurring and what can be done about it? Thanks Charles View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125177#4125177 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125177

16 years, 11 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Handling of 'deployments taking ~1 minute' scenario

by bstansberry＠jboss.com

It's hard for me to say for sure without knowing for sure what your issue is. I'll I can do is *assume* the issue was due to slow or non-existent replies to intra-cluster calls made by the jboss:service=DefaultPartition service. If that was the problem, then yes, using many smaller clusters could help isolate the problem to a few machines rather than having it effect all of them. But be careful about the assumption above. In most use cases there are not a lot of calls over the jboss:service=DefaultPartition after the nodes have started. If you are seeing continued cluster-wide issues after startup, there's a good chance this is not the issue. Please be sure to raise a support case on the customer support portal, where we have better tools available to diagnose your problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125174#4125174 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125174

16 years, 11 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet Container 1.2 changes

by julien＠jboss.com

I haven't mentioned it yet but I did remove the ProducerCacheInterceptor due to the addition of the CacheControl feature in 286. Now the same job is executed when the initial CacheControl impl is built and can be overwritten by the portlet at runtime using the API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125157#4125157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125157

16 years, 11 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Portlet Container 1.2 changes

by julien＠jboss.com

In order to implement the "next possible portlet mode" feature I did: - remove on PortletInvocation the properties "supportedModes" and "supportedWindowStates" - remove the ModesInterceptor and WindowStatesInterceptor - updates -beans.xml to remove those interceptors I have added on the FragmentResponse a Set nextModes which indicates the next possible modes to the portal. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125156#4125156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125156

16 years, 11 months

1
0
0 / 0

[Design of POJO Server] - Re: EJB/War deployer ordering problem

by wolfc

Seam only does a simple JNDI lookup. Which is perfectly allowed. A JNDI lookup can happen anywhere at any time without MC knowing any explicit dependency. One way to solve this is to hook JNP to MC, so that if something is not found open deployments are resolved first until either the JNDI name appears or MC is done with deploying. In the later case it would result in a NameNotFoundException. (It can even remember (persistently) which bean made it pop-up so future deployments will be faster.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125151#4125151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125151

16 years, 11 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Handling of 'deployments taking ~1 minute' scenario

by aparolini88

Hi, I am the "customer" that incoutered this issue with log4j and NFS. In our TEST Jboss cluster, we solved this by installing all our JBOSS AS into a local file system insteed of NFS. Since then, it never happed again. But just this morning, we had the same issue in our PRODUCTION environement. Meaning that all EJB calls inter-jboss where dreadfully slow. We solved it by restarting one of our Jboss that was somehow "stuck" ( but not by log4j that time!). The problem is this: when just one Jboss server is stuck, the whole Jgroup cluster is stuck. This issue is terrible for us, because we have a big heterogenous cluster with 20 applications (nodes) on it. So when this issue araises, all the application are not working. My question is this: if we switch to several homogenous cluster ( each application has it how small cluster (partition) of 2 to 4 nodes), will this leverage the effect of this issue ? Thanks in advance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125145#4125145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125145

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: New ClassLoader initial checkin

by gcompienne

Ok thanks, this answers my question. I didn't realize that your comment was only about the implementation itself (of the classloaders) and didn't include classes like ClassLoaderMetadata. I agree that if the basic rules (hierarchical model,...) are followed then there should not be any issues. Thanks for the clarification. Gilles. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125144#4125144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125144

16 years, 11 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ManagedObject stuff for AOP

by alesj

"kabir.khan(a)jboss.com" wrote : | 1) Am I ok using -beans.xml files for this? Or should I be using -aop.xml? If so, how do the -aop.xml files get recognised by the deployer that deploys -beans.xml files? I think that means scrapping the AspectDeployer? | | 2) I will probably need to do something similar for aspects configured via annotations. So we might need the AspectDeployer anyway. I should be able to easily create the BeanMetaDataFactory from the annotations, but what would the entry point of getting these beans into the MC be? | http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124836 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125138#4125138 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4125138

16 years, 11 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 January 2008