[
https://issues.jboss.org/browse/WFLY-1568?page=com.atlassian.jira.plugin....
]
David Lloyd resolved WFLY-1568.
-------------------------------
Fix Version/s: (was: 9.0.0.CR1)
Resolution: Rejected
Actually it is theoretically possible for the CPU to schedule all actions for a REMOVE
before the install runs. But in the real world, yes, this code construct will probably
never work. A service can presently only be replaced by employing a service listener,
unfortunately. A simpler service replacement API is something we can look into for MSC 2
though.
Cannot reliably reinstall service with same name
------------------------------------------------
Key: WFLY-1568
URL:
https://issues.jboss.org/browse/WFLY-1568
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: MSC
Reporter: Thomas Diesler
Assignee: David Lloyd
There seems to be an undefined "cleanup period" needed, before a service with
the same name can be installed successfully. If you do the below in the same thread it
will always fail (I believe).
{code}
controller.setMode(Mode.REMOVE)
serviceTarget.addService(controller.getName(), service).install()
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira