There were a cpl of threads last week on this issue.
I ran into it today, and could not find the solution posted.
Although, Victor's notes on the db problem helped.
When you first install JBoss in Linux as root, your umask is probably 022.
This means that JBoss won't have write access to any of the directories
it needs, causing several errors on startup.
Unfortunately, the Database errors are kind of bland and non-descriptive.
To solve the db problem, and thereby allowing JBoss auto deploy to start
correctly I made the following changes as root:
chmod -R 777 {your JBoss path}/deploy
chmod -R 777 {your JBoss path}/tmp
chmod -R 777 {your JBoss path}/log
chmod -R 777 {your JBoss path}/db
I'm still getting a cpl of errors, but at least the auto deploy for interest.jar
is working.
Does anyone have a less brute force solution?
Hope this helps,
Dave
Visit iWon today for a chance to win $25 Million!
Click here - http://www.iwon.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user