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

[Design of POJO Server] - Re: JBAS-6104; slow Seam deployments

by alesj

"shane.bryzak(a)jboss.com" wrote : there hasn't been much of an improvement | The fix is probably fixing the problem at re-deploy. Or is that what you tested? As long as there's gonna be a lot of URL usage, VFS is gonna be slow. Since VFS URL doesn't know that there's already an un-packed version of that resource somewhere. Need to see what can be done ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184642#4184642 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184642

15 years, 12 months

1
0
0 / 0

[Design of JBoss Profiler] - Strange Jboss profiler 1.0 issue.

by DoubleDenim

I've just followed instructions on setting up jboss profiler and I get this strange error when trying to run. I actually looks a bit scary. java -XrunjbossInspector:/tmp this is the new DLL Running process on Windows 3648 Cannot open file /tmp\log_spyserver_3648.txt. Please check you directory name View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184612#4184612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184612

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by bstansberry＠jboss.com

Just an update. First, I deployed a bean with configuration like what you reported Andy, and when StatefulTreeCache was accessing the bean metadata to determine how to set up JBoss Cache's passivation, it got a maxSize=100000. So, that's all working fine. I deployed the bean along with a little service that creates a configurable # of threads that loop a configurable number of times instantiating new beans. Doesn't use the beans after looking up the proxy and invoking a single getter. Fired it off telling it to use 4 threads to create 200K beans. Am now watching the JMX console view of the bean container to see what happens. 1) The CurrentSize attribute steadily rose past 10K; no apparent limit; eventually got up to over 24K 2) After 5 mins, consistent with the default @CacheConfig.idleTimeoutSeconds=300 in ejb3-interceptors-aop.xml, passivation kicked in and the CurrentSize started dropping a bit while PassivatedCount steadily rose. It would appear the single background thread is able to passivate beans faster than the 4 threads create them. Judging from some periodic logging I added, it's taking about 6 secs to create 500 beans. The beans aren't particularly heavyweight, the client is in-vm, and there's only one node in the cluster, so no replication going on. So not particularly fast. But, the passivation part seems to be working as I'd expect. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184606#4184606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184606

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by bstansberry＠jboss.com

I want to see why it looks like he's ending up w/ a maxSize of 10,000 rather than 100,000. I've created a trivial SFSB deployment that will match what Andy's got; was planning to look a bit at what's happening to the deployment in a debugger. If the metadata StatefulTreeCache gets says 100,000 for sure it's my problem; if it says 10,000 we can flip a coin for the honors :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184575#4184575 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184575

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by ALRubinger

"bstansberry(a)jboss.com" wrote : Great, thanks. I've been diverted into a bunch of areas yesterday and this morning, but will be able to focus on this this afternoon. Which parts are you going to be looking at, Brian? If we find something with the SimpleStatefulCache outside of Clustering then I don't want to pull you away. :) S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184574#4184574 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184574

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by bstansberry＠jboss.com

Great, thanks. I've been diverted into a bunch of areas yesterday and this morning, but will be able to focus on this this afternoon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184570#4184570 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184570

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by andy.miller＠jboss.com

"andy.miller(a)jboss.com" wrote : "andy.miller(a)jboss.com" wrote : "ALRubinger" wrote : "andy.miller(a)jboss.com" wrote : I can probably reduce the code down to just the servlet and stateful session bean, and strip out the database access, and just put a sleep in the method implementation. | | | | | | In the end we're going to need a more isolated case that may involve invocations on an SFSB alone, or preferably something to test Cache passivation directly. Then we may apply the same test to any of our cache implementations. | | | | | | S, | | | ALR | | | | | | | | | | I will work on cutting out just the code for the Stateful Session Bean, so it can be turned into an isolated test case tomorrow. | | I have been struggling to create a more isolated test case that's easy to run. I have a test case that is creating lots of Stateful Session Beans, but I can't get them to be cached (other than one bean at a time). What causes the bean to be cached, and then eventually passivated? Okay, never mind. I had a little bug in the stateful session bean, and JBDS was not updating the ear dynamically (as it should have). I now have an isolated test case that caches the stateful session beans. I will attach the code, and I profile of it soon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184569#4184569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184569

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Passivating EJB 3 Stateful Session Beans stops the World

by andy.miller＠jboss.com

"andy.miller(a)jboss.com" wrote : "ALRubinger" wrote : "andy.miller(a)jboss.com" wrote : I can probably reduce the code down to just the servlet and stateful session bean, and strip out the database access, and just put a sleep in the method implementation. | | | | In the end we're going to need a more isolated case that may involve invocations on an SFSB alone, or preferably something to test Cache passivation directly. Then we may apply the same test to any of our cache implementations. | | | | S, | | ALR | | | | | | I will work on cutting out just the code for the Stateful Session Bean, so it can be turned into an isolated test case tomorrow. I have been struggling to create a more isolated test case that's easy to run. I have a test case that is creating lots of Stateful Session Beans, but I can't get them to be cached (other than one bean at a time). What causes the bean to be cached, and then eventually passivated? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184563#4184563 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184563

15 years, 12 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Pluggable replication protocols

by bstansberry＠jboss.com

Suggest you post on the Design of JBoss Cache mailing list where the main JBC developers are more likely to see your question: http://www.jboss.com/index.html?module=bb&op=viewforum&f=207 I don't think the 2PC protocol is particularly replaceable. There have been some changes in JBC 3 that might make it more replaceable than I think, but I doubt that it's really replaceable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184556#4184556 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184556

15 years, 12 months

1
0
0 / 0

[Design of EJB 3.0] - Re: Reintroducing Asynchronous Support

by david.lloyd＠jboss.com

It occurs to me that the javadoc is a better link: http://docs.jboss.org/xnio/latest/api/org/jboss/xnio/IoFuture.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4184543#4184543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4184543

15 years, 12 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 October 2008