This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
I am currently involved with a two-node vertical cluster deployment of the JBoss SOA platform, version 4.3. I am trying to use JBoss Native to have my two nodes both running as Services in my Windows 2003 Server environment. I can get both services to install fine, however when the time comes to start them, only the first will start. The second does not start at all, and does not leave a log file.
Does anyone here have experience running a similar configuration using JBoss Native?
You will need to either bind that app servers to different IP addresses or change the ports so that they do not conflict. And you will need two service.bat files.
By the way, the full explanations of how to set up multiple app servers running as services using JBoss native is given in JBoss in Action, section 15.6.2.
Thank you for the welcome, Peter!
I've looked at those instructions, and I've also followed some instructions from a JBoss Support Rep. However, I am only able to get one service running at any one time. I can get both of my nodes to boot successfully if I do it via command-line, but using the installed service will only allow one to start. I am binding each node to its own IP address on the machine, so port conflicts aren't the issue.
I think I've narrowed down the culprit to a lock file which is created by the service.bat script when starting up the service. The batch file creates a lock file, then starts up the service. The lock file is removed after the service is stopped. Since I am unsure of what the purpose this lock file is serving, I am hesitant to just modify the service.bat to create a second lock file for my second node.
I will see about getting my hands on a copy of JBoss in Action for review. Thank you for your time!
Yes, you do have to use multiple lock file names, one for each service. The lock file is there to prevent the service from being started twice. If you look at the examples for the book you will see that we use a different lock file for each service.
subject: Using JBoss Native with a vertical cluster