Try to move out your application from farm folder and then deploy after restarting.
There seems some issue with deployed application.
Thanks... we removed the ear completely...and get the same error.
We then modified the run.bat file to comment out the cluster settings with REM.
There were 2 lines that needed commenting out.
JBoss started up just fine when NOT in cluster mode.
We put the run.bat back to its original cluster setting, and startup fails with the message again.
So... it is something to do with clustering in the run.bat file.....
The first line was:
if [%1] -- [-c] set SERVER=%2/farm
The second line was:
set ARGS=%ARGS% -g IdmPartition -Djboss.messaging.ServerPeerID=0
Instead of specifying these options in run.bat, try by calling them manually as below :
run.bat -c farm -g IdmPartition -Djboss.messaging.ServerPeerID=0
Then see if it works or not.
We were able to resolve this issue by:
We deleted all the tmp, temp, and work files on the 01 server.
We deleted all the files in the DATA folder...on the 01 server.
We restarted JBoss on this 01 server.... it started, but still had some deployment issues.
We began noticing problems with the 02 server.
We restarted JBoss on the 02 server... it started.
We deleted all the tmp/temp, and work files on the 01 server.
We deleted all the files in the DATA folder... on the 01 server.
We restarted JBoss on the 01 server... it started with no deployment issues.
This appears to have been some type of clustering issue with the 2 Jboss servers.
Only after deleting the DATA folder were we able to recover.
Normally this thing happens, Jboss store caches and other tmp data in tmp, work and data folder. So its good to delete these after doing new installation and then restart servers .