[JBoss JIRA] (WFLY-5601) Failure to add a datasource with a name that was previously used
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-5601?page=com.atlassian.jira.plugin.... ]
James Perkins closed WFLY-5601.
-------------------------------
Resolution: Rejected
Using the {{reload}} operation executes and returns immediately. This could result in the {{add}} operation executing before the reload is complete. That would result in some odd behavior in this case indicating a duplicate capability reference.
Just for completeness of the description. Here's what Brian said about the {{reload}} operation.
{quote}
you also get a response to the reload op earlier than you might intuitively expect
basically it has to tell you it succeeded before it starts shutting down all the services
otherwise you likely won't ever get a response because the service to send you a response has stopped
{quote}
With CLI there is a {{reload}} command that does block and handle the reconnect for the {{ModelControllerClient}}.
> Failure to add a datasource with a name that was previously used
> ----------------------------------------------------------------
>
> Key: WFLY-5601
> URL: https://issues.jboss.org/browse/WFLY-5601
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> Steps to re-create: create DS, remove it, reload and then add again (using the same name for the DS)
> This leads to:
> {noformat}
> java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.swarm-integration-test' is already registered in context 'global'.
> at org.jboss.as.controller.CapabilityRegistry.registerCapability(CapabilityRegistry.java:146)
> at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1422)
> at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1414)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:274)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:146)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-5601) Failure to add a datasource with a name that was previously used
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFLY-5601?page=com.atlassian.jira.plugin.... ]
James Perkins reassigned WFLY-5601:
-----------------------------------
Assignee: James Perkins (was: Brian Stansberry)
> Failure to add a datasource with a name that was previously used
> ----------------------------------------------------------------
>
> Key: WFLY-5601
> URL: https://issues.jboss.org/browse/WFLY-5601
> Project: WildFly
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: James Perkins
> Priority: Blocker
> Fix For: 10.0.0.Final
>
>
> Steps to re-create: create DS, remove it, reload and then add again (using the same name for the DS)
> This leads to:
> {noformat}
> java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.swarm-integration-test' is already registered in context 'global'.
> at org.jboss.as.controller.CapabilityRegistry.registerCapability(CapabilityRegistry.java:146)
> at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1422)
> at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1414)
> at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:274)
> at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:146)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
> at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
> at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
> at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-5601) Failure to add a datasource with a name that was previously used
by Heiko Braun (JIRA)
Heiko Braun created WFLY-5601:
---------------------------------
Summary: Failure to add a datasource with a name that was previously used
Key: WFLY-5601
URL: https://issues.jboss.org/browse/WFLY-5601
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Brian Stansberry
Priority: Blocker
Fix For: 10.0.0.Final
Steps to re-create: create DS, remove it, reload and then add again (using the same name for the DS)
This leads to:
{noformat}
java.lang.IllegalStateException: WFLYCTL0363: Capability 'org.wildfly.data-source.swarm-integration-test' is already registered in context 'global'.
at org.jboss.as.controller.CapabilityRegistry.registerCapability(CapabilityRegistry.java:146)
at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1422)
at org.jboss.as.controller.OperationContextImpl.registerCapability(OperationContextImpl.java:1414)
at org.jboss.as.controller.AbstractAddStepHandler.recordCapabilitiesAndRequirements(AbstractAddStepHandler.java:274)
at org.jboss.as.controller.AbstractAddStepHandler.execute(AbstractAddStepHandler.java:146)
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1336)
at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:217)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-5600) List of nodes taken from org.wildfly.clustering.group.Group is different across nodes
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-5600?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-5600.
------------------------------
Fix Version/s: 10.0.0.Alpha3
Resolution: Out of Date
This issue was addressed by: https://github.com/wildfly/wildfly/commit/bc19803a2fcd5b02caad187a0353ab5...
> List of nodes taken from org.wildfly.clustering.group.Group is different across nodes
> -------------------------------------------------------------------------------------
>
> Key: WFLY-5600
> URL: https://issues.jboss.org/browse/WFLY-5600
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EE, EJB
> Affects Versions: 9.0.1.Final
> Environment: Windows 7 64 bit, JDK 1.8_20 64bit
> Reporter: Piotr Nowicki
> Assignee: Paul Ferraro
> Labels: channel, cluster, jgroups
> Fix For: 10.0.0.Alpha3
>
>
> I have a cluster of 2 nodes with a WAR application deployed using web-console and exposing EJB remote business interface with following content:
> {code}@Stateless
> @Remote
> public class ServiceImplementation implements Service {
> @Resource( lookup = "java:jboss/clustering/group/ejb" )
> private Group channelGroup;
> @Override
> public void printNodeList() {
> for( Node node : channelGroup.getNodes()) {
> System.out.println( "node = " + node );
> }
> }
> }
> {code}
> I invoke this EJB from a standalone client multiple times (to make sure that method calls will reach both nodes.)
> The result is different on both nodes:
> * On master node the result is *correct* = two nodes' names are printed out ,
> * On second node the result is *incorrect* = *no nodes' names are printed out*.
> This was working fine in WFLY 8.2.0.Final.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month