Deployment problem with migration to 5.1.0 GA

[mcote321]

Hello all, new user here.

We are having problems porting our Seam app from JBoss 5.0.1 to 5.1.0, notably a deployment problem. The
HDScanner seems to want to keep redeploying after the server has successfully started. The result is that after
our app has been deployed, something notices a change and JBoss starts loading our war again...this loop seems
to go on endlessly.

To reproduce:

1) Stop JBoss (just to be on the safe side...)
2) Clean all traces of our war (from default server/deploy)
3) Deploy with Maven from Eclipse
4) Start JBoss (no errors during startup)
5) We get the following two interesting lines from the log:

2009-05-25 17:48:43,686 INFO [org.jboss.bootstrap.microcontainer.ServerImpl] (main) JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 45s:546ms
2009-05-25 17:48:51,466 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) undeploy, ctxPath=/sweat-dispatch-0.0.1

6) The whole thing restarts from step 4 ... etc


We are using:
- JDK 1.6 build 13
- JBoss 5.1.0 GA
- Maven 2.0.7
- Seam 2.1.1 GA
- Eclipse 3.4.2
- All are running on vista


Any help would be appreciated!

[jaikiran]

I remember there was a change in this hot deployment area in 5.1.0.GA. Is your application deployed in exploded format? Also, do any of the files (ex: xml files) get touched (timestamp change) or updated after the war is deployed? Also, is there a war file you can point us to which reproduces this?

[jaikiran]

- Eclipse 3.4.2

Does that mean you are using an IDE to deploy applications in JBoss?

[mcote321]

1. Yes we are using eclipse to deploy, rather a shortcut in eclipse generated by the maven plugin.

2. Our app is exploded when deployed.


Re: is anything getting touched after deployment?

We compared the timestamps of our war files before and after deployment, and not one file is different. We also deleted everything under "default server/tmp" in case something already compiled may be misbehaving...to no avail.

Note: We tried deploying the war file without exploding it, and it worked perfectly.

Thanks for looking into this for us.

[jaikiran]

Can you try reproducing this without the IDE in picture? I am not sure how the IDE handles the deployment/undeployment.

[mcote321]

It is actually Maven which is doing the deploying, we ran the following shell command on maven to exclude eclipse:

mvn compile war:exploded -P local -Dmaven.test.skip=true

...and we got the same result.

jaikiran, you suggested looking at our war: I can put it on our ftp server, can you please send me an email for info: mcote ats stingraydigital dots com

Thanks

[mcote321]

Found the problem, not sure what to do about it....

For many xml files we edit, eclipse( or JBoss Tools?) creates an equivalent *.jsfdia or *.spdia file. These were picked up by maven and deployed, and somehow they appear to handcuff JBoss during initialization, but somehow only when the war is exploded.

Any suggestions to elegantly correct this issue? ..aside from manually deleting them all the time. (We are new to JBoss and maven).


Thanks for your help

[jaikiran]

"mcote321" wrote:

jaikiran, you suggested looking at our war: I can put it on our ftp server, can you please send me an email for info: mcote ats stingraydigital dots com

Sure, let's see what the issue is with your war. I have dropped an mail. We'll continue the discussion in this thread so that others are aware of the real issue.

For many xml files we edit, eclipse( or JBoss Tools?) creates an equivalent *.jsfdia or *.spdia file. These were picked up by maven and deployed, and somehow they appear to handcuff JBoss during initialization, but somehow only when the war is exploded.

When do you edit the xml files? While the server has already deployed the application? And you edit the xml directly in the deployed application? I am trying to figure out at what point those .jsfdia files get added to the war.

[mcote321]

A bit more info:

Thanks for the offer of looking at our war, I'm not sure it will be helpful anymore.

We edit the XML files in eclipse, and everytime we do, I'm assuming the visual editor of eclipse generates the *.jsfdia or *.spdia files. So far they are generated when editing faces-config.xml and pages.xml, and the files are created in the WEB-INF dir.

When maven deploys our app in a war file (not exploded), these files are included in the generated war, but somehow overlooked by JBoss. On the other hand, if we maven deploys our app as an exploded war, JBoss seems to go into some kind of deployment loop; correctly loading our war over and over ad nauseam.

[jimjamz]

Was this ever resolved. I'm running into the same issue.

[jaikiran]

Was this ever resolved. I'm running into the same issue.

The fix will be part of the soon to be release AS 5.2 Beta version. However there are workarounds in the meantime.

1) (simple) workaround : Remove any *.jsfdia or *.spdia file(s) from the WEB-INF of the war file (note: those files might be "hidden")

OR

2) (a bit complex) workaround is discussed here http://www.jboss.org/index.html?module=bb&op=viewtopic&t=159645

[deanhiller]

We ran into the same issue...work around was to remove our *.txt files as that also caused the infinite redeploy. We however have not been using exploded wars..the problem happens in a normal war file for us. It is very annoying...not sure what bug was introduced in 5.1.