JBoss Interview Questions and Answers
Ques 11. Can I run Seam outside of JBoss AS?
Ans. Yes, you can run Seam applications in plain Tomcat 5.5+ or in the Sun GlassFish application server. To run Seam application in Tomcat, you need a number of additional library files and a few configuration files to bootstrap the JBoss EJB3 inside Tomcat. Please refer to the deploy.tomcat ANT build target for the Seam booking example (in the examples/booking directory of the Seam distribution) for more on how to build a Tomcat WAR for Seam applications. Refer to this blog post on how to run Seam in Sunís Glassfish application server.
Ques 12. Can I run Seam in a J2EE environment?Ans. Yes, as of Seam 1.1, you can use Seam in any J2EE application server, with one caveat: you will not be able to use EJB 3.0 session beans. However, you can use either Hibernate or JPA for persistence, and you can use Seam JavaBean components instead of session beans.
Ques 13. Can I run Seam with JDK 1.4 and earlier?Ans. No, Seam only works on JDK 5.0 and above. It uses annotations and other JDK 5.0 features.
Ques 14. How to build clusters in JBoss?Ans. here is a nutshell summary from the example given in the .org quick start:
from your jboss bin directory:
$ ./run.sh -c all -g DocsPartition -u 22.214.171.124 -b 192.168.0.101 -Djboss.messaging.ServerPeerID=1
./run.sh = the executable
-c all = use server in jboss_home/server/all directory
-g DocsPartition = this is the partition name, use whatever but should be the same across nodes
-u 126.96.36.199 = this is the multicast address, ususally just pick anything in the 239.255.x.y range and you should be ok
-b 192.168.0.101 = this is the ip of the machine the node is on
-Djboss.messaging.ServerPeerID=1 = this is the peerid, it must be unique for each node,
so the start script that you would run on your second machine for the second node would look like:
$ ./run.sh -c all-node2 -g DocsPartition -u 188.8.131.52 -b 192.168.0.102 -Djboss.messaging.ServerPeerID=2
you can also use nohup to send the process to the background...
now that both nodes should be running, you have to enable and configure the sticky sessions on thw webserver and each server.
Most helpful rated by users: