Looking at jboss-3.0.4, i can see 3 ways.
1) Easy one: Change the Scan period to be a huge value, so that scan happens only between long intervals.
2) Set the ScanEnabled to be false. to do this, get to the http://localhost:8080/jmx-console, click on the
and set the "ScanEnabled" attribute to false. This doesnt stop the hot deployment, so you have to stop the mbean using the stop method and start(). This stops hot deployment.
3) Change the AbstractDeploymentScanner.java code from
protected MuBoolean scanEnabled = new MuBoolean(true);
protected MuBoolean scanEnabled = new MuBoolean(false);
and recompile and use that.
Thanks. it works well.
Just curiosity... Why would you like to disable such as nice feature?
I am using JBoss 3.0.8. My hot deploy does not work correctly on most occassions. I can see the .ear getting deployed - but either the changes do not take effect or worse I get all kinds of errors.
The only way I have been able to make it work is by re-starting JBoss.
Anyone has experienced the same, ideas and suggestions.
Are you ftp-ing over to your deploy dir? Thats one of the cases where i have seen errors because Jboss sees the .ear file as soon as its created(or Windows creates the file as soon as it gets the first bye) and since the file is not fully created, jboss throws errors as it is not a valid jar/ear.
No - the deployment works correctly- I do not get deployment errors.
The errors are only when I execute.
hot deploy is awesome for dev. but if you
were running a critical application (say 24/7 type)
accepting machine-to-machine ecommerce, would
you trust that
1. JBoss will always hotdeploy your war/ear correctly?
(not dissing jboss here). The possiblities for errors
are endless (i could have a developer putting in some
bad piece of code somewhere that can break the hot deploy process)
2. what if one of the operation guy copy the wrong
jar/war/ear to the deploy dir by mistake?
3. most of us are pretty paranoid.
The argument for hotdeploy cuts both ways. If it is 24/7 production- I need hotdeploy- else I will have to bring the server down.
But my issue is simple- the hot deploy is not working. I deploy- the deploy is successful- that is JBoss did not report any errors.
As I stated earlier- either the changes don't take effect or it gives errors- when executing. The problems go away- when I stop and restart JBoss. Hotdepeloy should not require restart.
True. without hotdeploy, i'd have to restart JBoss.
However, in a 24/7 , wouldn't you be expected to
have multiple redundant app servers pooled together?
anyway in our case, we have a pool of 5 JBoss servers (non clustered though) which allow
us to take one out of the pool, shutdown,update,restart and push it back into the pool.
Like i said, we haven't had any issue with JBoss
hotdeploying during QA and DEV. I am just
> The argument for hotdeploy cuts both ways. If it is
> 24/7 production- I need hotdeploy- else I will have
> to bring the server down.
> But my issue is simple- the hot deploy is not
> working. I deploy- the deploy is successful- that is
> JBoss did not report any errors.
> As I stated earlier- either the changes don't take
> effect or it gives errors- when executing. The
> problems go away- when I stop and restart JBoss.
> Hotdepeloy should not require restart.
I think my problems may be beyond hotdeploy. My application is a 3-tier app. A Tomcat/JSP front and , JBoss/EJB Middle-end and a JBoss/EJB backend. The three layers are indpendent of each other but ofcourse talk to each other. Any of the layers can re-deploy/hotdeploy itself. This is when the problem occurs. I guess some old EJB references are held and by some layer- so at execution time it throws exceptions.
Seems like a complex issue. I don't know what the answer may be.
Ideas suggestions welcome.
Thanks a lot,