-
1. Re: Farm deployment on JBoss 3.2
rcostanzo May 8, 2003 11:22 AM (in response to mrenner)Add a dependency on the transaction service in your deploy/farm-service.xml config, like:
<depends optional-attribute-name="TransactionManagerServiceName">jboss:service=TransactionManager
This should make your datasource available before the application is deployed. -
2. Re: Farm deployment on JBoss 3.2
rcostanzo May 8, 2003 2:40 PM (in response to mrenner)The above posting may not do the trick. Refer to the following past posting for a solution which may fix your issue:
http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg27030.html//www.mail-archive.com/jboss-user@lists.sourceforge.net/msg27030.html -
3. Re: Farm deployment on JBoss 3.2
mrenner May 9, 2003 2:14 AM (in response to mrenner)Hi.
Both changes didn't fix my issue :(
After I added the dependency to the transaction service, the startup order was the following:
Starting deployment: farm-service.xml
Deployed package: farm-service.xml
...
Starting deployment: transaction-service.xml
Starting deployment: jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/
Deployed package: jbossha-httpsession.sar/ClusteredHttpSessionEB.jar/
Starting deployment: My EAR in "farm"
Deployed package:: My EAR in "farm"
Deployed package: transaction-service.xml
So, although I added a dependency from "farm-service" to "transaction-service", it looks like the farm service starts the deployment of my EAR *while* the transaction service is starting up.
IMHO there is something broken with the configuration of JBoss 3.2. Without any changes, the farm-service is started in the middle of the startup sequence for the directory "deploy". Then, the farm service is deploying the files found in "farm", thus breaking the startup order which is defined in the DeploymentSorter. -
4. Re: Farm deployment on JBoss 3.2
toddmcf2002 May 9, 2003 8:58 AM (in response to mrenner)I have the same issues and wonder if things are broken. For now I'm not farming.
-
5. Re: Farm deployment on JBoss 3.2
mrenner May 11, 2003 1:55 AM (in response to mrenner)Hi.
I found a thread on the mailing list, which describes exactly the same problem with JBoss 3.0.4:
http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg24705.html//www.mail-archive.com/jboss-user@lists.sourceforge.net/msg24705.html
According to the last message in this thread, it should have been fixed in 3.0.5. If this is the case, then it looks like patches from 3.0.x don't make it into 3.2.x :-(( -
6. Re: Farm deployment on JBoss 3.2
gmatthews May 14, 2003 6:02 PM (in response to mrenner)I had the same/similar error message appearing in my attempts to get farming working.
I manually put the datasource .xml file in the *deploy* directory of each machine, and put the .ear file in the *farm* directory.
This seemed to make startup + re-deploy errors go away. I thought it a reasonable workaround since the datasource .xml file doesn't usually change between new releases of the .ear -
7. Re: Farm deployment on JBoss 3.2
slaboure May 20, 2003 4:30 AM (in response to mrenner)If you think this is a bug that whould be fixed, please post a bug report on http://sf.net/projects/jboss and assign it to slaboure.
Thanks