Hi,
I am new with JBoss and EJB3. I have written a Stateless Session Bean and want to deploy on JBoss Application Server.
I want to configure the Instance Pool Size of JBoss with the following configuration:
Minimum Size: 10
Maximum Size: 50
The instance pool should be populated with the minimum number of instance at the startup of the server.
Is it possible to configure the Session Bean with the same?
Any reply will be appreciated as this is a bottleneck for me.
Thanks in advance...
Greetings,
Puneet
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139293#4139293
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139293
"alex.loubyansky(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : We know it found the schema (assuming that file exists in the classpath
| | and is reachable from the bean parsing deployer's classloader):
| |
| | | TRACE [org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver] (main) found schema InputSou
| | | rce, nsURI=urn:jboss:security-config:5.0, baseURI=null, schemaLocation=resource:security-config_5_0.
| | | xsd
| | |
|
| Actually, it didn't. This message would be logged even if it wasn't found. I am fixing it. And looking into why it is not found...
Are you going to fix the logging as well then? :-)
Kind of pointless even having it when it is meaningless.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139288#4139288
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139288
"alesj" wrote :
|
How would this relate with KernelDeploymentDeployer, meaning that we need to 'convince' it not to split up the deployment into separate non-related beans.
Or how do you plan to group all beans from a deployment marked with 'asynch' and install them in the same background thread?
Why would you need to?
You simply have an Executor backed by a thread pool + queue on the controller.
You submit the task to the executor then it will do something like:
anonymous wrote :
|
|
| A
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139283#4139283
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139283
"adrian(a)jboss.org" wrote : We know it found the schema (assuming that file exists in the classpath
| and is reachable from the bean parsing deployer's classloader):
|
| | TRACE [org.jboss.xb.binding.sunday.unmarshalling.DefaultSchemaResolver] (main) found schema InputSou
| | rce, nsURI=urn:jboss:security-config:5.0, baseURI=null, schemaLocation=resource:security-config_5_0.
| | xsd
| |
Actually, it didn't. This message would be logged even if it wasn't found. I am fixing it. And looking into why it is not found...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139282#4139282
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139282
"adrian(a)jboss.org" wrote : A simple mechansim that I can think of would to have a new ControllerMode
| http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/trunk/jboss-dependency...
| which you could add to your deployment.
|
|
| | <deployment mode="asynchronous">
| | <!-- beans here -->
| | </deployment>
| |
|
| which would work like the "automatic" mode, except it submits the work
| to a background thread pool.
|
| In this scenario, it would largely be "self-optimizing" since
| it would automatically advance related dependencies that are eligible once
| these beans reach the relevant stages.
|
How would this relate with KernelDeploymentDeployer, meaning that we need to 'convince' it not to split up the deployment into separate non-related beans.
Or how do you plan to group all beans from a deployment marked with 'asynch' and install them in the same background thread?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4139276#4139276
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4139276