proper redeployment under JBoss6?

[alfonz19]

Hi,

I've got here this problem. I'm used to deploy aplication by copying for example ear into deploy directory. And redeploying it via deleting that file and placing there a new one(without stopping AS). But after switching to JBoss6 I'm facing *very ofter* problem that after redeployment (as described) of new version the old version gets deployed again instead! Then I have to turn off the AS clear its caches, start it again and miraculously everything works fine and I did not touch mentioned ear at all!

Question:

what's the proper way of redeployment to avoid this problem? (nothing sucks more than debugging aplication and suddenly realize that I'm debugging current version of app ...)

[jaikiran]

martin mucha wrote:

But after switching to JBoss6 I'm facing *very ofter* problem that after redeployment (as described) of new version the old version gets deployed again instead!

Can you explain a bit more? What shows up as old data?

[alfonz19]

ok, no problem.

Actually I do not *know* what is happening, I just observe it as a black box. I happens like this:

I've got running AS with deployed application. I noticed a bug in it and corrected it in sources, rebuild app, deleted old ear from deploy directory of running jboss, moved new build into deploy directory. Apps get deployed, I check whether error is still present, and it is! I'm confused, but also lucky enough that I've run Jboss with arguments

-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n

so I just attach debugger and look closely why the correction did not work, AND debugger stops on blank lines, outside of methods, follow the code improperly --> there *must* be inconsistence between running app and source code.

shut down AS,

rm -rf work tmp data log

start AS again, application works as expected.

[wdfink]

Do you changed anything other than ear? Can it be possible that you provide an interface jar in the lib directory?

Does it work without deleting tmp directory?

[alfonz19]

no, just the ear was modified. Deleted and than other file was moved to that location. Happened many times so I'm absolutery sure that ... I did not intentionaly touch anything else. Of course I cannot grant that OS did not touch some file, but that's I think highly improbable. The OS is linux, if that can cause something (if I remember it correctly, on linux is possible delete file while this file will be available on for processes already having handle to it, which is kind a different from windows where such file won't be allowed for deletion -- but I find this to be also highly improbable as a reason for this behavior)

Ok, next time I saw this problem I'll check whether sole AS restart is sufficient to solve the problem. If it won't help then I check whether deletion of work data log

will save the day.

Btw. thanks for helping me.