Does you start a clean 7.1.1 or do you change configurations.
Do you have checked that the server start correct without the deploment?
Maybe you set the logging level of the root-logger to debug or trace to have more information.
Yes. The server starts correctly without the deployment. Also, when I try to deploy my ear (which fails), I can still access admin console. This means that everything else in the server seems to be ok and it's some sort of problem related to my deployment.
I have also set my root-logger to debug but there are no catastrophic errors.
I am using JDK 7. Thanks.
Could you attach the server.log and your application which can not be deployed?
I have attached my boot logs ( INFO and DEBUG levels). Unfortunately, I cannot attach my application because sensitive information are everywhere in the config files. As I said earlier, this is an app which has been running on JBoss 6 in production for over 1 year. If you require it, I could attach specific parts of the app. I hope you understand.
Btw, when the deployment hangs, after a while, I see the following in the console
13:34:12,363 WARN [com.arjuna.ats.arjuna] (Transaction Reaper) ARJUNA012117: TransactionReaper::check timeout for TX 0:ffffc0a8016f:-25588975:50127b67:8 in state RUN
13:34:12,369 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012095: Abort of action id 0:ffffc0a8016f:-25588975:50127b67:8 invoked while multiple threads active within it.
13:34:12,373 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012108: CheckedAction::check - atomic action 0:ffffc0a8016f:-25588975:50127b67:8 aborting with 1 threads active!
13:34:12,377 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffffc0a8016f:-25588975:50127b67:8
maybe this could be helpful.....
I also forgot to mention that this is a seam app. When the app was running on JBoss 6, I was using seam 2.2.2. For the migration to JBoss 7.1.1 I updated the seam jars to 2.3.0 beta2.
Thanks for your help.
Try to set the deployment-timeout:
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" deployment-timeout="600"/>
In your log the deploy end after about 60sec, I suppse the timeout is in seconds.
I actually set it to 300 seconds. That did not make a difference. Then I just increased to 600. Still no difference.