"Live" changes in xml and "live" deploys?

[razta]

Hi. we just migrated to Wildfly from jboss6. Set up an managed domain, all working fine and dandy with 8 servers running a nice cluster.

We selected Domain as the chance to change stuff "on the fly" and hot deploy in the GUI sounded like an AWESOME thing to do.

But but but...

We cant edit anything while the servers are running.

Tried to edit a typeo in a datasource (one letter wrong on the username). Dident work as the datasource was enabled, tried to disable the datasrouce, still enabled and _ALL_ our live production servers just halted. Had to do a kill -9 on the application just to restart everything.

Tried to hotdeply an EAR file while servers was running. Dident work, couple of pages of a stacktrace and not deploying the app. Did a shutdown on one of the servergroups. deployed it there and did that over all the servers. Dident work. Had to do a kill -9 on the jboss application just to restart everything.

Why the HELL do i want a damn domain? If i would have set up this myself with my own clustering and single-servers i could have just disabled one in our loadbalancer. Do my edits and put it back. I cant do this now or am i missing something???

Anyone been able to get _ANY_ of the function son the domain part to actualy work as intended or is everythin "comming in next version" ?

[ctomc]

How did you try to edit configuration? in XML?

That wont work as new changes are only picked up once server is restarted.

CLI or admin console are the way to go when it comes to this.

What do you mean by hot deployment? In domain mode deployments are handled bit differently and traditional standalone hot deployment doesn't work by default

[razta]

>How did you try to edit configuration? in XML?

Tried changing XML at first, dont work until restart as you said.

But we also used the GUI to edit a datasource, witch dident work at all. As it was "in use" as i said in my post. Editing datasource required datasource to be disabled. Tried to disable the datasource = stopped all our app servers. All in all, had to restart all servers, shut them down. Edit XML. Start all servers. This is not really optimal, atleast not for us that have a 100% uptime requirement.

>What do you mean by hot deployment?

I meant deploy a new EAR while servers are running.

We have both a script to do CLI deployments but this time we tried to do it in the GUI with the fail above.

I dont know. I might have configured something faulty but i really can t see what that should be.