We'd need to think about the mbean interface as well; i.e .if we still want to expose a property via JMX attributes on the deployer then aggregating properties into beans doesn't help much.
For the clustering properties I don't see any point in still exposing JMX setters for them; they shouldn't be changed after the deployer is started.
Several of the clustering properties I'm tempted to pull out of the deployer anyway; they just set global defaults that can be overridden in jboss-web.xml. I could just make the defaults hard coded for a few rarely used ones (e.g. snapshotMode/Interval). I'd have done that already but I found out a major customer is actually using snapshotMode a lot.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089824#4089824
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089824
Either don't call Connector.stop() twice (needs new API to know if started), or reduce the logging level on the message it emits if stop() is called if already stopped.
>From looking at the how the various TC protocols work, I don't see how calling Connector.stop() will prevent keepalive requests on existing sockets either. Both pause() and stop() deal with accepting sockets off the server socket and handing them off to be handled; AFAICT they don't impact what happens with existing connections.
pause() -- pause the thread the accepts sockets off the server socket. Not good for shutdown as it basically means connection requests will pile up on the socket rather than promptly failing over.
stop() -- pause() plus close the server socket.
This for sure needs Remy's input.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089800#4089800
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089800
I'm a beginner with JBoss Profiler and I've been trying to do some cost analysis on my architectural layers.
Imagine the following architecture:
| Client -> Web Services (JBoss WS) -> JBoss ESB -> EJB -> Hibernate
I'd like to know how much time I'm spending on each layer.
I've noticed that JBoss creates two threads, one for WS layer and the other for ESB and EJB.
To get start time on WS layer I took org.apache.catalina.connector.CoyoteAdapter.service(org.apache.coyote.Request,org.apache.coyote.Response) times.
To get start time on ESB I took java.util.concurrent.ThreadPoolExecutor$Worker.runTask(java.lang.Runnable)
1) Is this right!?
Maybe, I've misunderstood the concepts, but:
2) What is the difference between Process View and Thread View?
3) What is the meaning of "Root methods" in Process View mode?
4) What is the meaning of "% Threads" in Process View mode?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089792#4089792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089792