Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware - Red Hat Summit Accelerate Your JBoss Enterprise Middleware - Red Hat Summit
Accelerate Your JBoss Enterprise Middleware –Web ServicesWebWebServicesServices● A couple of additional comments on the configuration parameters● If you exceed the queue size, requests will start to be executed on thecalling thread.● The calling thread will be the HTTP thread, and hence the web servicewill cease to be asynchronous, but synchronous, losing all the benefitsof having annotated the web service with @OneWay to begin with.● The initial threads parameter causes that number of threads to bestarted at the time the AutomaticWorkerQueueImpl is started, so settingto something reasonable is a good idea, considering threads won't bestarted until the web service is invoked, and if that is under load, youcould have some severe startup performance issues, while threads arebeing started.● If you don't set the initial threads, but set a lowWaterMark, thelowWaterMark will be used as the value of pre-starting threads in thepool.
Accelerate Your JBoss Enterprise Middleware –RemotingRemotingRemoting● EAP 6 contains an entirely new remoting layer, written from scratch.● This new remoting layer is built on a JBoss project called XNIO,which as you can probably surmise, is based on the JDK's NIOcapabilities.● It's a completely non-blocking I/O design.● Configuration is done through the subsystems that actually useremoting.● The EJB 3 container is the primary user of the remoting layer inEAP 6.● So, we will talk configuration of this as we talk about the EJB3.x container.
- Page 2 and 3: Accelerate Your JBoss EnterpriseMid
- Page 4 and 5: Accelerate Your JBoss Enterprise Mi
- Page 6 and 7: Accelerate Your JBoss Enterprise Mi
- Page 8 and 9: Accelerate Your JBoss Enterprise Mi
- Page 10 and 11: Accelerate Your JBoss Enterprise Mi
- Page 12 and 13: Accelerate Your JBoss Enterprise Mi
- Page 16 and 17: Accelerate Your JBoss Enterprise Mi
- Page 18 and 19: Accelerate Your JBoss Enterprise Mi
- Page 20 and 21: Accelerate Your JBoss Enterprise Mi
- Page 22 and 23: Accelerate Your JBoss Enterprise Mi
- Page 24 and 25: Accelerate Your JBoss Enterprise Mi
- Page 26 and 27: Accelerate Your JBoss Enterprise Mi
- Page 28 and 29: Accelerate Your JBoss Enterprise Mi
- Page 30 and 31: Accelerate Your JBoss Enterprise Mi
- Page 32 and 33: Accelerate Your JBoss Enterprise Mi
- Page 34 and 35: Accelerate Your JBoss Enterprise Mi
- Page 36 and 37: Accelerate Your JBoss Enterprise Mi
- Page 38 and 39: Accelerate Your JBoss Enterprise Mi
- Page 40 and 41: Accelerate Your JBoss Enterprise Mi
- Page 42 and 43: Accelerate Your JBoss Enterprise Mi
- Page 44 and 45: Accelerate Your JBoss Enterprise Mi
- Page 46 and 47: Accelerate Your JBoss Enterprise Mi
- Page 48 and 49: ManagementManagementAccelerate Your
- Page 50 and 51: Accelerate Your JBoss Enterprise Mi
- Page 52 and 53: Accelerate Your JBoss Enterprise Mi
- Page 54 and 55: Accelerate Your JBoss Enterprise Mi
- Page 56 and 57: Accelerate Your JBoss Enterprise Mi
- Page 58 and 59: Accelerate Your JBoss Enterprise Mi
- Page 60 and 61: Accelerate Your JBoss Enterprise Mi
- Page 62 and 63: Accelerate Your JBoss Enterprise Mi
<strong>Accelerate</strong> <strong>Your</strong> <strong>JBoss</strong> <strong>Enterprise</strong> <strong>Middleware</strong> –RemotingRemotingRemoting● EAP 6 contains an entirely new remoting layer, written from scratch.● This new remoting layer is built on a <strong>JBoss</strong> project called XNIO,which as you can probably surmise, is based on the JDK's NIOcapabilities.● It's a completely non-blocking I/O design.● Configuration is done through the subsystems that actually useremoting.● The EJB 3 container is the primary user of the remoting layer inEAP 6.● So, we will talk configuration of this as we talk about the EJB3.x container.
Change language