[
https://issues.jboss.org/browse/JBAS-8204?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on JBAS-8204:
----------------------------------------
Saw this when using interactive demo with both a master and slave DC. Had deployed a war
to all servers in all groups, undeployed from main-server-group, then did "undeploy
and remove" from other-server-group. This was reported on the master:
[Host Controller] 10:59:39,615 ERROR [org.jboss.as.protocol.connection] (pool-1-thread-13)
Failed to read a message: java.io.IOException: Failed to handle management operation
[Host Controller] at
org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:63)
[Host Controller] at
org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:254)
[Host Controller] at
org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:213)
[Host Controller] at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_24]
[Host Controller] at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
[:1.6.0_24]
[Host Controller] at java.util.concurrent.FutureTask.run(FutureTask.java:138)
[:1.6.0_24]
[Host Controller] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
[:1.6.0_24]
[Host Controller] at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206)
[:1.6.0_24]
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
[Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
[Host Controller] at org.jboss.threads.JBossThread.run(JBossThread.java:122)
[Host Controller] Caused by: java.lang.IllegalArgumentException
[Host Controller] at org.jboss.dmr.ModelValue.asPropertyList(ModelValue.java:100)
[Host Controller] at org.jboss.dmr.ModelNode.asPropertyList(ModelNode.java:251)
[Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl.getOpsByGroup(DomainControllerImpl.java:627)
[Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl.execute(DomainControllerImpl.java:322)
[Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl.execute(DomainControllerImpl.java:110)
[Host Controller] at
org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:46)
[Host Controller] at
org.jboss.as.controller.remote.ModelControllerOperationHandlerImpl$ExecuteAsynchronousOperation.sendResponse(ModelControllerOperationHandlerImpl.java:209)
[Host Controller] at
org.jboss.as.protocol.mgmt.ManagementResponse$2.handle(ManagementResponse.java:119)
[Host Controller] at
org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59)
[Host Controller] ... 11 more
Deployment via a deployment plan
--------------------------------
Key: JBAS-8204
URL:
https://issues.jboss.org/browse/JBAS-8204
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: 7.0.0.Beta2
I want us to have some sort of deployment plan notion in our deployment API so users can
specify in a document how a rolling upgrade should occur, e.g. here's the new
deployment(s), first quiesce this set of servers, then upgrade, roll on to this set of
servers, etc.
Basically describe in a document the set of operations that are meant to be atomic.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira