Hot Deployment or Not?

[samuelj]

Hi to all.

My question is about of "what do you think about"...

I'm working on a project that includes several installation of JBoss instances on a large environment.

My problem is about the hot deployment service, I am not sure that enabling this service in a production environment is a good solution, above all in a large environment.

Simply because you can't have control of what should actually be released or not. I don't want an ear or a -ds.xml is accidentally released by an operator. So I prefer to deploy my applications with a full control stopping the service and restarting it.

What do you think about? Did you manage a large jboss environment with hot deployment service?

It's just my paranoia?

Thanks a lot!

SamuelJ

[samuelj]

Come on... no one has an opinion!? 

SJ

[samuelj]

Ok, I moved the thread from "Hot Deployment" to "JBoss As" discussion

[wdfink]

Hi Samuel,

sorry, normaly I look into hotdeployment

I would prefere no hotdeployment and no deploy-scanner in production. With JBoss4.x there are some issues with class unloading and application memory-leaks.

I think AS5 will be better but I never use it in production because of what you call 'accidentally released'.

With AS7 I think there is a good approach, the domain-management can be secured and the files are not scanned, you must deploy via console or CLI.

[samuelj]

Hi Wolf.

Thank yuo for you reply!

Sorry, but I don't know JBoss AS7. Are you telling me that "hot deployment" from AS7 was removed?

I'm curious to know why...

(Could you please link me some documentation? I didn't find nothing about ... )

Is there someone else that has an opinion about hot deployment in a production environment?

Come on guys, don't be shy!

SJ

[wdfink]

See AS7 admin guide here https://docs.jboss.org/author/display/AS7/Admin+Guide#AdminGuide-Coremanagementconcepts

With a so called 'standalone' installation you will have a single JBoss instance like in previous AS versions, but no cluster-farming service!

You can drop a file and it will be deployed.

With a 'domain' installation the domain-controller is the manager of all deployments, you can't drop a file to deploy it. You have to use the management interface.

In both cases the unloading of applications should be better isolated and do not leave garbage within the heap.

But nevertheless I prefere the managed 'domain' version in a productive environment to avoid deployments by accident.