[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by John Ament (JIRA)
[ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.... ]
John Ament edited comment on WFLY-5919 at 1/4/16 7:50 PM:
----------------------------------------------------------
[~smarlow] yes, its not an issue of strings (we actually use constants here). I apologize, as I also created an issue in HHH for this with more info. The fact that switching from schema to catalog fixes it makes me think its not configuration related.
The HHH issue is https://hibernate.atlassian.net/browse/HHH-10408 which was closed - rejected. While I can update my mappings to use catalog over schema, it doesn't seem consistent with prior versions of hibernate (in fact, my output shows this was working fine in 5.0.1). In addition, this may be an issue for your customers upgrading to EAP7.
was (Author: meetoblivion):
[~smarlow] yes, its not an issue of strings (we actually use constants here). I apologize, as I also created an issue in HHH for this with more info. The fact that switching from schema to catalog fixes it
The HHH issue is https://hibernate.atlassian.net/browse/HHH-10408 which was closed - rejected. While I can update my mappings to use catalog over schema, it doesn't seem consistent with prior versions of hibernate (in fact, my output shows this was working fine in 5.0.1). In addition, this may be an issue for your customers upgrading to EAP7.
> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
> Key: WFLY-5919
> URL: https://issues.jboss.org/browse/WFLY-5919
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.CR5
> Reporter: John Ament
> Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5919) Wildfly 10 CR5 Regression - Schema not added to query
by John Ament (JIRA)
[ https://issues.jboss.org/browse/WFLY-5919?page=com.atlassian.jira.plugin.... ]
John Ament commented on WFLY-5919:
----------------------------------
[~smarlow] yes, its not an issue of strings (we actually use constants here). I apologize, as I also created an issue in HHH for this with more info. The fact that switching from schema to catalog fixes it
The HHH issue is https://hibernate.atlassian.net/browse/HHH-10408 which was closed - rejected. While I can update my mappings to use catalog over schema, it doesn't seem consistent with prior versions of hibernate (in fact, my output shows this was working fine in 5.0.1). In addition, this may be an issue for your customers upgrading to EAP7.
> Wildfly 10 CR5 Regression - Schema not added to query
> -----------------------------------------------------
>
> Key: WFLY-5919
> URL: https://issues.jboss.org/browse/WFLY-5919
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 10.0.0.CR5
> Reporter: John Ament
> Assignee: Scott Marlow
>
> My app, working fine in Wildfly 9.0.2 now fails in 10.0.0.CR5 (it was fine in earlier CR's)
> {code}
> 2016-01-03 08:30:43,626 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) SQL Error: 1046, SQLState: 3D000
> 2016-01-03 08:30:43,626 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 87) No database selected
> 2016-01-03 08:30:43,627 INFO [org.hibernate.event.internal.DefaultLoadEventListener] (ServerService Thread Pool -- 87) HHH000327: Error performing load command : org.hibernate.exception.GenericJDBCException: could not extract ResultSet
> {code}
> I turned on query debug, and the query being generated is now skipping the schema name defined in my entity's schema (I'm using MySQL)
> The config looks like this
> {code}
> @Table(name = "types", schema = "config")
> {code}
> I have an orm.xml file, I tried removing the default schema stanza without luck.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5928) Intermittent NPE registering a slave HC in mixed-domain test suite
by Brian Stansberry (JIRA)
Brian Stansberry created WFLY-5928:
--------------------------------------
Summary: Intermittent NPE registering a slave HC in mixed-domain test suite
Key: WFLY-5928
URL: https://issues.jboss.org/browse/WFLY-5928
Project: WildFly
Issue Type: Bug
Components: Domain Management, Test Suite
Affects Versions: 10.0.0.CR4
Reporter: Brian Stansberry
Assignee: Brian Stansberry
I've occasionally seen test failures in the mixed domain tests when a testsuite cannot start because the slave HC can't register due to an NPE on the master:
For example:
http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=82653&tab=buil...
Critical log details:
{code}[0m16:16:15,252 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1
[0m[0m16:16:15,363 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
[0m[Host Controller] [0m16:16:15,871 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1[0m
[Host Controller] [0m[0m16:16:16,015 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1[0m
[Host Controller] [0m[0m16:16:16,068 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting[0m
[Host Controller] [0m[0m16:16:16,625 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.10.GA-redhat-1[0m
[Host Controller] [0m[0m16:16:16,629 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.10.GA-redhat-1[0m
[Host Controller] [0m[0m16:16:16,657 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version (unknown)[0m
[Host Controller] [0m[0m16:16:16,705 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on [::1]:19999[0m
INFO [org.jboss.as.test.integration.domain.management.util.DomainLifecycleUtil] ServerIdentity{name=server-one, host=slave, server-group=other-server-group} status is starting
[Host Controller] [0m[31m16:16:17,913 ERROR [org.jboss.as.controller.management-operation] (Host Controller Service Threads - 50) WFLYCTL0013: Operation ("read-master-domain-model") failed - address: ([]): java.lang.NullPointerException[0m
[Host Controller] [31m at org.jboss.as.controller.registry.OperationTransformerRegistry$1.getResourceTransformer(OperationTransformerRegistry.java:83)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.resolveTransformer(ResourceTransformationContextImpl.java:235)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:285)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription$3.invokeNext(TransformingDescription.java:161)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.description.AttributeTransformationRule.transformResource(AttributeTransformationRule.java:103)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.description.TransformingDescription.transformResource(TransformingDescription.java:167)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChild(ResourceTransformationContextImpl.java:289)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformationContextImpl.processChildren(ResourceTransformationContextImpl.java:254)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.ResourceTransformer$1.transformResource(ResourceTransformer.java:53)[0m
[Host Controller] [31m at org.jboss.as.controller.transform.TransformersImpl.transformRootResource(TransformersImpl.java:115)[0m
[Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadMasterDomainModelUtil.readMasterDomainResourcesForInitialConnect(ReadMasterDomainModelUtil.java:88)[0m
[Host Controller] [31m at org.jboss.as.domain.controller.operations.ReadDomainModelHandler.execute(ReadDomainModelHandler.java:51)[0m
[Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:890)[0m
[Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:659)[0m
[Host Controller] [31m at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)[0m
[Host Controller] [31m at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1343)[0m
[Host Controller] [31m at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:395)[0m
[Host Controller] [31m at org.jboss.as.controller.AbstractControllerService.internalExecute(AbstractControllerService.java:408)[0m
[Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService.access$900(DomainModelControllerService.java:175)[0m
[Host Controller] [31m at org.jboss.as.host.controller.DomainModelControllerService$InternalExecutor.execute(DomainModelControllerService.java:1229)[0m
[Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.processRegistration(HostControllerRegistrationHandler.java:424)[0m
[Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$RegistrationContext.access$400(HostControllerRegistrationHandler.java:334)[0m
[Host Controller] [31m at org.jboss.as.host.controller.mgmt.HostControllerRegistrationHandler$InitiateRegistrationHandler$1.execute(HostControllerRegistrationHandler.java:230)[0m
[Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$ManagementRequestContextImpl$1.doExecute(AbstractMessageHandler.java:363)[0m
[Host Controller] [31m at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:465)[0m
[Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[0m
[Host Controller] [31m at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[0m
[Host Controller] [31m at java.lang.Thread.run(Thread.java:745)[0m
[Host Controller] [31m at org.jboss.threads.JBossThread.run(JBossThread.java:320)[0m
[Host Controller] [31m[0m
[Host Controller] [0m[33m16:16:17,935 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010900: Could not connect to remote domain controller at remote://[::1]:9999 -- 1-$-WFLYCTL0158: Operation handler failed: java.lang.NullPointerException[0m
[Host Controller] [33m[0m[33m16:16:17,936 WARN [org.jboss.as.host.controller] (Controller Boot Thread) JBAS016581: No domain controller discovery options remain.[0m
[Host Controller] [33m[0m[31m16:16:17,939 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS016519: Tried all domain controller discovery option(s) but unable to connect[0m
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5926) org.wildfly.bom tag for version 10.0.0.CR5
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5926?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar resolved WFLY-5926.
-------------------------------
Fix Version/s: 10.0.0.CR5
Resolution: Done
> org.wildfly.bom tag for version 10.0.0.CR5
> ------------------------------------------
>
> Key: WFLY-5926
> URL: https://issues.jboss.org/browse/WFLY-5926
> Project: WildFly
> Issue Type: Task
> Affects Versions: 10.0.0.CR5
> Reporter: Leandro Kersting de Freitas
> Assignee: Tomaz Cerar
> Labels: bom, maven
> Fix For: 10.0.0.CR5
>
>
> Hi
> I am waiting for the artifact release 10.0.0.CR5 of org.wildfly.bom "wildfly-javaee7" and "wildfly-javaee7-with-tools", but it seems that has not been created yet.
> {code:xml}
> <dependency>
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-javaee7</artifactId>
> <version>10.0.0.CR5</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-javaee7-with-tools</artifactId>
> <version>10.0.0.CR5</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> {code}
> org.wildfly.bom is deprecated for 10.0.0.CR5 or after?
> https://github.com/wildfly/boms/issues/17
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5918) ServletContext.getResourceAsStream fails on windows
by Alban Chadenas (JIRA)
[ https://issues.jboss.org/browse/WFLY-5918?page=com.atlassian.jira.plugin.... ]
Alban Chadenas commented on WFLY-5918:
--------------------------------------
Hi Stuart,
I can confirm that applying your patch in the latest CR5 release fixes this issue. I am using 'junction' (symbolic links) in Windows which seems to have been causing this issue.
> ServletContext.getResourceAsStream fails on windows
> ---------------------------------------------------
>
> Key: WFLY-5918
> URL: https://issues.jboss.org/browse/WFLY-5918
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR5
> Environment: Wildfly 10.0.0 CR5
> Windows 7
> JDK 1.8_66 64Bit
> Reporter: Alban Chadenas
> Assignee: Stuart Douglas
>
> Struts 1 ActionServlet fails to initialize with latest Wildfly 10.0.0 CR5 though it was working fine on the previous CR4 release. The failure occurs when Servlet tries to read the /WEB-INF/web.xml inside my web application.
> Looking at the struts source code, getServletContext().getResourceAsStream("/WEB-INF/web.xml") returns null during the Servlet initialization.
> *problem only occurs when server is started from path that is not case equal to real path on file system.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFLY-5926) org.wildfly.bom tag for version 10.0.0.CR5
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-5926?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-5926:
---------------------------------
Assignee: Tomaz Cerar (was: Jason Greene)
> org.wildfly.bom tag for version 10.0.0.CR5
> ------------------------------------------
>
> Key: WFLY-5926
> URL: https://issues.jboss.org/browse/WFLY-5926
> Project: WildFly
> Issue Type: Task
> Affects Versions: 10.0.0.CR5
> Reporter: Leandro Kersting de Freitas
> Assignee: Tomaz Cerar
> Labels: bom, maven
>
> Hi
> I am waiting for the artifact release 10.0.0.CR5 of org.wildfly.bom "wildfly-javaee7" and "wildfly-javaee7-with-tools", but it seems that has not been created yet.
> {code:xml}
> <dependency>
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-javaee7</artifactId>
> <version>10.0.0.CR5</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> <dependency>
> <groupId>org.wildfly.bom</groupId>
> <artifactId>wildfly-javaee7-with-tools</artifactId>
> <version>10.0.0.CR5</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> {code}
> org.wildfly.bom is deprecated for 10.0.0.CR5 or after?
> https://github.com/wildfly/boms/issues/17
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1257) support query filter implementation in MBeanServerConnection
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1257?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFCORE-1257:
-------------------------------------
Issue Type: Bug (was: Feature Request)
> support query filter implementation in MBeanServerConnection
> ------------------------------------------------------------
>
> Key: WFCORE-1257
> URL: https://issues.jboss.org/browse/WFCORE-1257
> Project: WildFly Core
> Issue Type: Bug
> Components: JMX
> Affects Versions: 2.0.5.Final
> Reporter: Chao Wang
> Assignee: Brian Stansberry
>
> There is no implementation for query filter in MBeanServerConnection, marked as TODO
> {code:title=ModelControllerMBeanHelper.java|borderStyle=solid}
> Set<ObjectName> queryNames(final ObjectName name, final QueryExp query) {
> return new RootResourceIterator<Set<ObjectName>>(accessControlUtil, getRootResourceAndRegistration().getResource(),
> new ObjectNameMatchResourceAction<Set<ObjectName>>(name) {
> Set<ObjectName> set = new HashSet<ObjectName>();
> @Override
> public boolean onResource(ObjectName resourceName) {
> if (name == null || name.apply(resourceName)) {
> //TODO check query
> set.add(resourceName);
> }
> return true;
> }
> @Override
> public Set<ObjectName> getResult() {
> if (set.size() == 1 && set.contains(ModelControllerMBeanHelper.createRootObjectName(domain))) {
> return Collections.emptySet();
> }
> return set;
> }
> }).iterate();
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1265) support query filter implementation in MBeanServerConnection
by Brian Stansberry (JIRA)
Brian Stansberry created WFCORE-1265:
----------------------------------------
Summary: support query filter implementation in MBeanServerConnection
Key: WFCORE-1265
URL: https://issues.jboss.org/browse/WFCORE-1265
Project: WildFly Core
Issue Type: Bug
Components: JMX
Affects Versions: 2.0.5.Final
Reporter: Chao Wang
Assignee: Brian Stansberry
There is no implementation for query filter in MBeanServerConnection, marked as TODO
{code:title=ModelControllerMBeanHelper.java|borderStyle=solid}
Set<ObjectName> queryNames(final ObjectName name, final QueryExp query) {
return new RootResourceIterator<Set<ObjectName>>(accessControlUtil, getRootResourceAndRegistration().getResource(),
new ObjectNameMatchResourceAction<Set<ObjectName>>(name) {
Set<ObjectName> set = new HashSet<ObjectName>();
@Override
public boolean onResource(ObjectName resourceName) {
if (name == null || name.apply(resourceName)) {
//TODO check query
set.add(resourceName);
}
return true;
}
@Override
public Set<ObjectName> getResult() {
if (set.size() == 1 && set.contains(ModelControllerMBeanHelper.createRootObjectName(domain))) {
return Collections.emptySet();
}
return set;
}
}).iterate();
}
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (WFCORE-1259) Embedded HC started with host-slave.xml does not allow changes as master connection service is not available
by Ken Wills (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1259?page=com.atlassian.jira.plugi... ]
Ken Wills edited comment on WFCORE-1259 at 1/4/16 4:21 PM:
-----------------------------------------------------------
Fixed and tested by checking for running in admin-only=true for embedded and slave, and a disconnected slave using --cached-dc & admin-only=false.
was (Author: luck3y):
Fixed and tested by checking for running in admin-only, and a disconnected slave using --cached-dc.
> Embedded HC started with host-slave.xml does not allow changes as master connection service is not available
> ------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-1259
> URL: https://issues.jboss.org/browse/WFCORE-1259
> Project: WildFly Core
> Issue Type: Bug
> Reporter: Ken Wills
> Assignee: Ken Wills
>
> # update host-slave.xml - simplify the example
> -<host xmlns="urn:jboss:domain:4.0">
> +<host name="slave" xmlns="urn:jboss:domain:4.0">
> $ ./jboss-cli.sh -Djboss.domain.master.address=127.0.0.1
> [disconnected /] embed-host-controller --host-config=host-slave.xml --std-out=echo
> [domain@embedded /] /host=slave/server-config=server-one:write-attribute(name=socket-binding-port-offset, value=1)
> 2:22:06,003 ERROR [org.jboss.as.controller.management-operation] (AeshProcess: 2) WFLYCTL0013: Operation
> +("write-attribute") failed - address: ([
> ("host" => "slave"),
> ("server-config" => "server-one")
> ]): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.domain.controller.connection not found
> at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)
> at org.jboss.as.controller.OperationContextImpl$OperationContextServiceRegistry.getRequiredService(OperationCo
> +ntextImpl.java:2208)
> at org.jboss.as.domain.controller.operations.SyncModelOperationHandlerWrapper.execute(SyncModelOperationHandle
> +rWrapper.java:131)
> 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:1341)
> at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:392)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:204)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:659)
> at org.jboss.as.controller.ModelControllerImpl$3.execute(ModelControllerImpl.java:649)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerCli
> +ent.java:63)
> at org.jboss.as.cli.embedded.ThreadContextsModelControllerClient.execute(ThreadContextsModelControllerClient.j
> +ava:59)
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:84)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:753)
> at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:799)
> at org.jboss.as.cli.impl.CommandContextImpl$2.execute(CommandContextImpl.java:412)
> at org.jboss.aesh.console.AeshProcess.run(AeshProcess.java:53)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {
> "outcome" => "failed",
> "result" => {},
> "failure-description" => {"host-failure-descriptions" => {"slave" => "WFLYCTL0158: Operation handler failed: org.j
> +boss.msc.service.ServiceNotFoundException: Service service jboss.domain.controller.connection not found"}},
> "rolled-back" => true
> }
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months